diff --git a/x-pack/docs/en/security/authorization/mapping-roles.asciidoc b/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
index 590546e217c86..fba87db978626 100644
--- a/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
+++ b/x-pack/docs/en/security/authorization/mapping-roles.asciidoc
@@ -36,17 +36,14 @@ To use file based role-mappings, you must configure the mappings in a YAML file
 and copy it to each node in the cluster. Tools like Puppet or Chef can help with
 this.
 
-By default, role mappings are stored in `ES_PATH_CONF/x-pack/role_mapping.yml`,
+By default, role mappings are stored in `ES_PATH_CONF/role_mapping.yml`,
 where `ES_PATH_CONF` is `ES_HOME/config` (zip/tar installations) or
 `/etc/elasticsearch` (package installations). To specify a different location,
-you configure the `files.role_mapping` realm settings in `elasticsearch.yml`.
-This setting enables you to use a different set of mappings for each realm type:
-
-|=====
-| `xpack.security.authc.ldap.files.role_mapping` | | | The location of the role mappings for LDAP realms.
-| `xpack.security.authc.active_directory.files.role_mapping` | | | The location of the role mappings for Active Directory realms.
-| `xpack.security.authc.pki.files.role_mapping` | | | The location of the role mappings for PKI realms.
-|=====
+you configure the `files.role_mapping` setting in the 
+{ref}/security-settings.html#ref-ad-settings[Active Directory], 
+{ref}/security-settings.html#ref-ldap-settings[LDAP], and 
+{ref}/security-settings.html#ref-pki-settings[PKI] realm settings in 
+`elasticsearch.yml`.
 
 Within the role mapping file, the security roles are keys and groups and users
 are values. The mappings can have a many-to-many relationship. When you map roles