apply suggestions from review

Author: renetapopova

modules/ROOT/pages/database-administration/aliases/remote-database-alias-configuration.adoc

@@ -123,7 +123,7 @@ It must not be accessible to any user except for the administrator and `neo4j`,
 ====
 
 In a cluster, you must share the same keystore file among all servers.
-For example, these would be valid additions to the config when using the suggested keytool command:
+For example, these would be valid additions to the configuration when using the suggested keytool command:
 
 [parameters]
 ----
@@ -149,7 +149,7 @@ chmod 640 conf/neo4j.conf
 bin/neo4j start --expand-commands
 ----
 
-=== Manage remote database aliases
+=== Manage remote database aliases (_Carol_)
 
 To be able to manage remote database aliases, you must have either xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-database-management[database management]
 or xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-alias-management[alias management] privileges.
@@ -283,16 +283,16 @@ dbms.security.oidc.<provider>.claims.groups=groups
 dbms.security.oidc.<provider>.authorization.group_to_role_mapping= "engineers" = admin; \
                                                                    "collaborators" = reader
 ----
-=== Manage remote database aliases
+=== Manage remote database aliases (_Carol_)
 
 To be able to manage remote database aliases, you must have either xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-database-management[database management]
 or xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-alias-management[alias management] privileges.
 
-For example, the following command grants the permission to create an alias to the `administrator` role:
+For example, the following command grants the permission to create an alias to the `admin` role, which _Carol_ is a member of:
 
 [source, Cypher]
 ----
-GRANT CREATE ALIAS ON DBMS TO administrator
+GRANT CREATE ALIAS ON DBMS TO admin
 ----
 
 And here is how to grant the xref:authentication-authorization/database-administration.adoc#access-control-database-administration-access[`ACCESS` privileges] to use the remote database alias:
@@ -362,4 +362,4 @@ In the case of using `STORED NATIVE CREDENTIALS`, the same credentials are used
 This will result in the stored native user being logged in the audit trails on the remote DBMS for all queries using the remote database alias.
 When using `OIDC CREDENTIAL FORWARDING`, the actual end-user's credentials and permissions are used, resulting in per-user audit trails being logged on the remote DBMS.
 
-* When using a remote database alias with OIDC credential forwarding, the user needs to be logged in to the local DBMS with OIDC, otherwise there is no token to forward, and the access to the remote database will be denied with GQLSTATUS link:https://neo4j.com/docs/status-codes/current/errors/gql-errors/42NFF/[`42NFF`].
+* When using a remote database alias with OIDC credential forwarding, the user needs to be logged into the local *DBMS A* with OIDC, otherwise there is no token to forward, and the access to the remote database will be denied with GQLSTATUS link:https://neo4j.com/docs/status-codes/current/errors/gql-errors/42NFF/[`42NFF`].