diff --git a/single-sign-on/configure/index.md b/single-sign-on/configure/index.md
index 78a230a95c..e757230381 100644
--- a/single-sign-on/configure/index.md
+++ b/single-sign-on/configure/index.md
@@ -143,7 +143,7 @@ After you’ve completed the SSO configuration process in Docker Hub, you can te
 Before you enforce SSO in Docker Hub, you must complete the following:
 Test SSO by logging in and out successfully, confirm that all members in your org have upgraded to Docker Desktop version 4.4.2, PATs are created for each member, CI/CD passwords are converted to PAT. Also, when using Docker partner products (for example, VS Code), you must use a PAT when you enforce SSO. For your service accounts add your additional domains in **Add Domains** or enable the accounts in your IdP.
 
-Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that's configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see [Configure registry.json](../docker-hub/image-access-management.md#enforce-authentication)
+Admins can force users to authenticate with Docker Desktop by provisioning a registry.json configuration file. The registry.json file will force users to authenticate as a user that's configured in the allowedOrgs list in the registry.json file. For info on how to configure a registry.json file see [Configure registry.json](../../docker-hub/image-access-management.md#enforce-authentication)
 
 1. On the Single Sign-On page in Docker Hub, select **Turn ON Enforcement** to enable your SSO.
 2. When SSO is enforced, your users are unable to modify their email address and password, convert a user account to an organization, or set up 2FA through Docker Hub. You must enable 2FA through your IdP.
diff --git a/single-sign-on/requirements/index.md b/single-sign-on/requirements/index.md
index 51741b9e8f..6b5c9553c5 100644
--- a/single-sign-on/requirements/index.md
+++ b/single-sign-on/requirements/index.md
@@ -8,7 +8,7 @@ title: Requirements
 
 * You must first notify your company about the new SSO login procedures
 * Verify that your org members have the latest Docker Desktop version 4.4.2, or later, installed on their machines
-* New org members must create a PAT to sign in to the CLI, however existing users can use their username and password during the grace period as specified below
+* New org members must create a Personal Access Token (PAT) to sign in to the CLI, however existing users can use their username and password during the grace period as specified below
 * Confirm that all CI/CD pipelines have replaced their passwords with PATs
 * For your service accounts, add your additional domains or enable it in your IdP
 * Test SSO using your domain email address and IdP password to successfully sign in and log out of Docker Hub