fix documentation
diff --git a/src/site/apt/configuration.apt b/src/site/apt/configuration.apt
index a8f5168..e2c976d 100644
--- a/src/site/apt/configuration.apt
+++ b/src/site/apt/configuration.apt
@@ -239,5 +239,9 @@
* valid values for realistic usage are 'cached' and then further configuring the cached instance to use another underlying user manager like ldap or the jdo one which is used by default. Placing 'ldap' here will check with the ldap system for a fair amount of checks and would likely be a performance issue
+** RBAC Manager Implementation(s) to use
+
+ * rbac.manager.impl=cached (since 1.4-M4: Archiva support more than one value comma separated)
+
diff --git a/src/site/apt/rbac/introduction.apt b/src/site/apt/rbac/introduction.apt
index 5774f65..278616e 100644
--- a/src/site/apt/rbac/introduction.apt
+++ b/src/site/apt/rbac/introduction.apt
@@ -199,7 +199,7 @@
achieved by statically and dynamically regulating users' actions
through the establishment and definition of roles, role
hierarchies, relationships, and constraints. Thus, once an RBAC
- framework is established for an organization, the principal
+ framework is established for an organization, the username
administrative actions are the granting and revoking of users
into and out of roles. This is in contrast to the more
conventional and less intuitive process of attempting to
