diff --git a/windows/deployment/windows-autopilot/registration-auth.md b/windows/deployment/windows-autopilot/registration-auth.md
index 7ec31a7650..17a9875fb0 100644
--- a/windows/deployment/windows-autopilot/registration-auth.md
+++ b/windows/deployment/windows-autopilot/registration-auth.md
@@ -65,10 +65,11 @@ Each OEM has a unique link to provide to their respective customers, which the O
     NOTE: A user without global admin privileges who clicks the link will see a message similar to the following:
 
     ![Not global admin](images/csp7.png)
-3.	Customer clicks the “Yes” checkbox, followed by the “Accept” button, and they’re done.  Authorization happens instantaneously.
+3.	Customer selects the **Yes** checkbox, followed by the **Accept** button, and they’re done.  Authorization happens instantaneously.
 
-4.	The OEM can use the Validate Device Submission Data API to verify the consent has completed.  This API is discussed in the latest version of the API Whitepaper (p. 14ff).  As the Whitepaper says, it’s a best practice recommendation for OEM partners to run that API check to confirm they’ve received customer consent before attempting to register devices, to avoid errors in the registration process.
+4.	The OEM can use the Validate Device Submission Data API to verify the consent has completed.  This API is discussed in the latest version of the API Whitepaper, p. 14ff (https://devicepartner.microsoft.com/en-gb/assets/detail/windows-autopilot-integration-with-oem-api-design-whitepaper-docx). **Note**: this link is only accessible by Microsoft Device Partners. As discussed in this whitepaper, it’s a best practice recommendation for OEM partners to run the API check to confirm they’ve received customer consent before attempting to register devices, thus avoiding errors in the registration process.
 
 ## Summary
 
-As you can see from the steps above, Microsoft is no longer involved in the process:  the consent exchange happens directly between OEM and customer.  Also, it all happens instantaneously, as quickly as buttons are clicked.
+At this stage of the process, Microsoft is no longer involved; the consent exchange happens directly between the OEM and the customer.  And, it all happens instantaneously - as quickly as buttons are clicked.
+