Apply suggestions from code review

Co-authored-by: Mark Dixon <[email protected]>

Author: phil198

modules/ROOT/pages/authentication-authorization/manage-roles.adoc

@@ -353,7 +353,7 @@ You can view all available roles using the Cypher command `SHOW ROLES`, which re
 | STRING
 
 | immutable
-| Whether the role is immutable
+| `true` if the role is immutable, otherwise `false`.
 | BOOLEAN
 |===
 

modules/ROOT/pages/authentication-authorization/privileges-and-roles-immutable.adoc

@@ -6,16 +6,19 @@
 
 [NOTE]
 ====
-Immutable roles are newly introduced in Neo4j 5.24. Immutable privileges have been available since Neo4j 5.0.
+Immutable roles were introduced in Neo4j 5.24. Immutable privileges have been available since Neo4j 5.0.
 ====
 
 [[access-control-privileges-immutable-admin]]
 == How to administer immutable privileges and roles
 
-Unlike for regular privileges and roles, immutable privileges and roles cannot be administered by users with xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-privilege-management[PRIVILEGE MANAGEMENT] and xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-role-management[ROLE MANAGEMENT] privileges. Instead, they can only be administered when auth is disabled -- that is, when the configuration setting <<config_dbms.security.auth_enabled,`dbms.security.auth_enabled`>> is set to `false`.
+Unlike regular privileges and roles, immutable privileges and roles cannot be administered by users with xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-privilege-management[PRIVILEGE MANAGEMENT] and xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-role-management[ROLE MANAGEMENT] privileges. 
+Instead, they can only be administered when auth is disabled -- that is, when the configuration setting <<config_dbms.security.auth_enabled,`dbms.security.auth_enabled`>> is set to `false`.
 
 [CAUTION]
-It is intended that administering immutable privileges and roles is an extraordinarily rare scenario and one which should be undertaken with extreme caution (i.e. when the dbms has been isolated by some other means and unauthorized access can be reliably prevented). It is considered to be the kind of action which may be performed once during the commissioning phase of a database.
+Immutable privileges and roles should only be used in a scenario where changes are rare. 
+They are intentionally difficult to change and thus changes should be undertaken with caution (i.e. when the DBMS has been isolated by some other means and unauthorized access can be reliably prevented).
+It is considered to be the kind of action which may be performed once during the commissioning phase of a DBMS.
 
 When the configuration setting <<config_dbms.security.auth_enabled,`dbms.security.auth_enabled`>> is set to `false`, immutable privileges and roles can be administered in a similar way to regular privileges and roles, using the `IMMUTABLE` keyword.