fix tests

Author: sarahsanders-docker

content/manuals/security/for-admins/provisioning/scim.md

@@ -256,7 +256,7 @@ and select your SCIM application.
     - `userPrincipalName` -> `userName`
     - `mail` -> `emails.value`
     - Optional. Map `dockerRole`, `dockerOrg`, or `dockerTeam` using one of the
-    [mapping methods](#choose-a-role-mapping-method).
+    [mapping methods](#step-two-choose-a-role-mapping-method).
 1. Remove any unsupported attributes to prevent sync errors.
 1. Optional. Go to **Mappings** > **Provision Azure Active Directory Groups**:
     - If group provisioning causes errors, set **Enabled** to **No**.

content/manuals/security/troubleshoot/troubleshoot-provisioning.md

@@ -43,7 +43,7 @@ assignment does not reflect changes.
 
 **Disable JIT provisioning (recommended)**
 
-1. Sign in to the Docker [Admin Console](app.docker.com/admin).
+1. Sign in to the Docker [Admin Console](https://app.docker.com/admin).
 1. Go to your organization's **Settings** > **Security** > **SSO and SCIM**.
 1. Find the relevant SSO connection.
 1. Select the **actions menu** and choose **Edit**.
@@ -76,7 +76,7 @@ linked to manage them.
 SCIM only manages users that it provisions. To allow SCIM to manage an
 existing user:
 
-1. Remove the user manually from the Docker [Admin Console](app.docker.com/admin).
+1. Remove the user manually from the Docker [Admin Console](https://app.docker.com/admin).
 1. Trigger provisioning from your IdP.
 1. SCIM will re-create the user with correct attributes.