DOC: Replace transaction by role permissions

src/doc/permissions.rst

@@ -37,11 +37,11 @@ A Permission Rule consists of:
    below.
 
 There are two complementing types of permission rules that will be explained
-below: transaction permissions and entity permissions.
+below: role permissions and entity permissions.
 
-.. _transaction-permissions:
+.. _role-permissions:
 
-Transaction permissions
+Role permissions
 ***********************
 
 .. _entity-permissions:
@@ -106,9 +106,9 @@ used for administration users and in no other case. So, ...
 How to set permissions
 ----------------------
 
-There are multiple ways to set transaction and entity permissions. The most
+There are multiple ways to set role and entity permissions. The most
 common and best tested way currently is to set global default entity permissions
-in the ``global_entity_permissions.xml`` config file, and role-based transaction
+in the ``global_entity_permissions.xml`` config file, and role-based role
 permissions with the ``caosdb_admin.py`` `utility script
 <https://gitlab.com/caosdb/caosdb-pylib/-/blob/main/src/caosdb/utils/caosdb_admin.py>`__
 of CaosDB's Python library which is also used to `manage users and
@@ -126,7 +126,7 @@ find a more detailed description of the possible ways of setting permissions.
    permissions defined here (see :ref:`Permission
    calculation<Calculation>`). Note also that, as the name suggests, only
    :ref:`entity permissions<entity-permissions>` can be set this way. The
-   role-based :ref:`transaction-permissions<transaction-permissions>` have to be
+   role-based :ref:`role-permissions<role-permissions>` have to be
    set with one of the other ways explained below.
 -  **API:** Both REST and GRPC API allow to set the permissions. This hasn't been
    documented properly yet, but for the GRPC API, `the specification