Minor changes

server_admin/topics/authentication/flows.adoc

@@ -183,7 +183,7 @@ After entering the username, the way this flow works is the following:
 It is important to note that since the WebAuthn Passwordless execution is set to _Alternative_ instead of _Required_, this flow will never ask the user to register a WebAuthn credential. For a user
 to have a Webauthn credential, that user must have a required action added by an administrator. This is done first by making sure that the `Webauthn Register Passwordless`
 required action is enabled in the realm (see the <<_webauthn,WebAuthn>> documentation), and then by setting the required action by using the `Credential Reset` part of a
-user's <<_user-credentials,Credentials>> management menu.
+user's xref:ref-user-credentials_{context}[Credentials] management menu.
 
 Creating a more advanced flow such as this one can have some subtle side effects. For example, if you were to enable the ability to reset the password
 for the user, then this would be accessible from the password form. In the default "Reset Credentials" flow, the user has to enter his username. Since

server_admin/topics/authentication/webauthn.adoc

@@ -86,7 +86,7 @@ assuming that authentication flow configuration above with the conditional subfl
 
 ===== Managing Credentials
 
-WebAuthn credentials are managed in a similar manner as other credentials, such as OTP, from the <<_user-credentials, User credential management>>:
+WebAuthn credentials are managed in a similar manner as other credentials, such as OTP, from the xref:ref-user-credentials_{context}[User credential management]:
 
 * Users can be assigned a required action to create a WebAuthn credential from the `Reset Actions` list, and selecting `Webauthn Register`
 * The administrator can delete a WebAuthn credential by pressing `Delete`.

server_admin/topics/users/proc-searching-user.adoc

@@ -15,7 +15,7 @@ NOTE: This action searches only the local {project_name} database and not the fe
 +
 .. To search users from a federated backend, the user list must be synced into the {project_name} database. Adjust the search criteria to sync the backend users to the {project_name} database.
 +
-.. Alternatively, click the *User Federation* tab.
+.. Alternatively, click the *User Federation* in the left menu.
 ... To apply changes to a selected user, click *Sync changed users* on the page with your federation provider.
 ... To apply changes to all users in the database, click *Sync all users* on the page with your federation provider.
 

server_admin/topics/users/recaptcha.adoc

@@ -7,7 +7,7 @@ To enable this you need to first go to link:https://developers.google.com/recapt
 and create an API key so that you can get your reCAPTCHA site key and secret.
 (FYI, localhost works by default so you don't have to specify a domain).
 
-Next, there are a few steps you need to perform in the {project_name} Admin Console.
+Next, there are a few steps you need to perform in the {project_name} admin console.
 Click the `Authentication` left menu item and go to the `Flows` tab.  Select the `Registration` flow from the drop down
 list on this page.
 
@@ -33,5 +33,5 @@ values of both the `X-Frame-Options` and `Content-Security-Policy` headers.
 image:{project_images}/security-headers.png[]
 
 Once you do this, reCAPTCHA should show up on your registration page.  You may want to edit _register.ftl_ in your login
-theme to muck around with the placement and styling of the reCAPTCHA button.  See the link:{developerguide_link}[{developerguide_name}]
+theme to experiment with the placement and styling of the reCAPTCHA button.  See the link:{developerguide_link}[{developerguide_name}]
 for more information on extending and creating themes.