apply suggestions from review

Author: renetapopova

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

@@ -13,22 +13,23 @@ CREATE ROLE roleViewer IF NOT EXISTS;
 CREATE ROLE roleManager IF NOT EXISTS;
 CREATE ROLE userAdder IF NOT EXISTS;
 CREATE ROLE userNameModifier IF NOT EXISTS;
-CREATE ROLE homeDbModifier IF NOT EXISTS;
-CREATE ROLE allUserImpersonator IF NOT EXISTS;
 CREATE ROLE userModifier IF NOT EXISTS;
-CREATE ROLE passwordModifier IF NOT EXISTS;
-CREATE ROLE statusModifier IF NOT EXISTS;
 CREATE ROLE userDropper IF NOT EXISTS;
 CREATE ROLE userViewer IF NOT EXISTS;
 CREATE ROLE userManager IF NOT EXISTS;
 CREATE ROLE userImpersonator IF NOT EXISTS;
+CREATE ROLE allUserImpersonator IF NOT EXISTS;
+CREATE ROLE authModifier IF NOT EXISTS;
+CREATE ROLE passwordModifier IF NOT EXISTS;
+CREATE ROLE statusModifier IF NOT EXISTS;
+CREATE ROLE homeDbModifier IF NOT EXISTS;
 CREATE ROLE databaseAdder IF NOT EXISTS;
 CREATE ROLE compositeDatabaseAdder IF NOT EXISTS;
 CREATE ROLE databaseDropper IF NOT EXISTS;
 CREATE ROLE compositeDatabaseDropper IF NOT EXISTS;
 CREATE ROLE databaseModifier IF NOT EXISTS;
 CREATE ROLE accessModifier IF NOT EXISTS;
-CREATE ROLE languageModifier IF NOT EXISTS;
+CREATE ROLE languageModifier IF NOT EXISTS;Enables the specified roles to delete composite databases.
 CREATE ROLE compositeDatabaseModifier IF NOT EXISTS;
 CREATE ROLE compositeDatabaseManager IF NOT EXISTS;
 CREATE ROLE databaseManager IF NOT EXISTS;
@@ -49,8 +50,6 @@ CREATE ROLE deniedBoostedProcedureExecutor2 IF NOT EXISTS;
 CREATE ROLE deniedBoostedProcedureExecutor3 IF NOT EXISTS;
 CREATE ROLE deniedBoostedProcedureExecutor4 IF NOT EXISTS;
 CREATE ROLE adminProcedureExecutor IF NOT EXISTS;
-CREATE ROLE userAndRoleAdministrator IF NOT EXISTS;
-CREATE ROLE authModifier IF NOT EXISTS;
 CREATE ROLE functionExecutor IF NOT EXISTS;
 CREATE ROLE deniedFunctionExecutor IF NOT EXISTS;
 CREATE ROLE boostedFunctionExecutor IF NOT EXISTS;
@@ -91,7 +90,6 @@ The xref:authentication-authorization/built-in-roles.adoc#access-control-built-i
 This includes the following tasks and their relevant privileges:
 
 * Create, delete, and modify <<access-control-dbms-administration-database-management, databases>> and  <<access-control-dbms-administration-alias-management, aliases>>.
-* Manage <<access-control-dbms-administration-privilege-management, privileges>>.
 * Change configuration parameters.
 * xref:authentication-authorization/database-administration.adoc#access-control-database-administration-transaction[Manage transactions].
 * Manage <<access-control-dbms-administration-user-management, users>> and <<access-control-dbms-administration-role-management, roles>>.
@@ -1047,7 +1045,7 @@ GRANT [IMMUTABLE] CREATE COMPOSITE DATABASE
 | Enables the specified roles to create new composite databases.
 
 | [source, syntax, role=noheader]
-GRANT DROP COMPOSITE DATABASE
+GRANT [IMMUTABLE] DROP COMPOSITE DATABASE
   ON DBMS
   TO role[, ...]
 | Enables the specified roles to delete composite databases.

modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc

@@ -25,14 +25,12 @@ Privileges are defined on the target database, and not the local database alias.
 Remote database aliases::
 A remote database alias may target a database from another Neo4j DBMS.
 It can be used for:
-* Connecting to a database of a remote Neo4j DBMS
-* `USE` clauses
-* Setting a user's home database
-* Defining the access privileges to the remote database
-* label:new[Introduced in 2025.06] Setting a default Cypher version for queries to the remote database.
-
+* Connecting to a database of a remote Neo4j DBMS. +
 Remote database aliases require configuration to safely connect to the remote target, which is described in xref::database-administration/aliases/remote-database-alias-configuration.adoc[Connecting remote databases].
 It is not possible to impersonate a user on the remote database or to execute an administration command on the remote database via a remote database alias.
+* `USE` clauses.
+* Defining the access privileges to the remote database.
+* label:new[Introduced in 2025.06] Setting a default Cypher version for queries to the remote database.
 
 [NOTE]
 ====

modules/ROOT/pages/database-administration/index.adoc

@@ -9,7 +9,7 @@ The DBMS can manage a standalone server, or a group of servers in a cluster.
 A database is an administrative partition of a DBMS.
 In practical terms, it is a physical structure of files organized within a directory or folder, that has the same name of the database.
 
-This chapter describes how to manage standard databases, composite databases, and local and remote database aliases. +
+This chapter describes how to manage standard databases, composite databases, and local and remote database aliases.
 All databases and database aliases are managed using the Cypher administration commands.
 For more information on the Cypher administration commands syntax, see xref:database-administration/syntax.adoc[Database management command syntax].