feedback from doc review

Author: micheleRP

modules/manage/partials/rbac-delete-role.adoc

@@ -6,6 +6,4 @@ To delete an existing role:
 
 . Click *Delete*.
 
-. {ui} displays a prompt asking you to confirm deletion of the role. The prompt differs based on whether there are principals assigned to the role or not. If there are principals assigned to the role, you must type the role name in the input field when prompted before you can continue.
-
 . Click *Delete*.

modules/manage/partials/rbac-dp.adoc

@@ -116,8 +116,8 @@ Permission resolution rules:
 
 A user is permitted to perform an operation if and only if:
 
-. No DENY permission exists matching the operation
-. An ALLOW permission exists matching the operation
+. No `DENY` permission exists matching the operation
+. An `ALLOW` permission exists matching the operation
 
 Examples:
 
@@ -127,22 +127,22 @@ Examples:
 
 | `ALLOW READ topic:logs`
 | Role has `DENY READ topic:logs`
-| ❌ DENIED
-| DENY always takes precedence
+| ❌ denied
+| `DENY` always takes precedence
 
 | `DENY WRITE topic:sensitive`
 | Role has `ALLOW WRITE topic:*`
-| ❌ DENIED
-| Specific DENY blocks wildcard ALLOW
+| ❌ denied
+| Specific `DENY` blocks wildcard `ALLOW`
 
 | No direct ACLs
 | Role has `ALLOW READ topic:data`
-| ✅ ALLOWED
+| ✅ allowed
 | Role permission applies
 
 | `ALLOW READ topic:public`
 | No role ACLs for this topic
-| ✅ ALLOWED
+| ✅ allowed
 | Direct permission applies
 |===
 
@@ -187,7 +187,7 @@ Permission management
 
 * Start with minimal permissions: Grant only the access required for the role's function
 * Use wildcards carefully: Prefixed patterns like `analytics-*` are useful but review regularly
-* Avoid DENY rules: Prefer specific ALLOW rules over complex DENY/ALLOW combinations
+* Avoid `DENY` rules: Prefer specific `ALLOW` rules over complex `DENY`/`ALLOW` combinations
 * Document role purpose: Maintain clear documentation about what each role is intended for
 
 Operational guidelines