[BULK UPDATE] DocuTune - Rebranding

Contributor-guide/github-browser-updates.md

@@ -14,14 +14,14 @@ There are two separate locations where we keep Windows Server technical content.
 
 - **I'm a Microsoft employee.** As a Microsoft employee, you have options, based on what you're trying to do:
 
-    - **Create a brand-new article.** To create a brand-new article, you must create and set up your GitHub account and tools, fork and clone the `windowsserverdocs-pr` repo, set up your remote branch, create the article, and finally create a new pull request for approval and publishing. For these instructions, see the [Create new Windows Server articles using GitHub and Visual Studio Code](create-new-using-github.md) article.
+  - **Create a brand-new article.** To create a brand-new article, you must create and set up your GitHub account and tools, fork and clone the `windowsserverdocs-pr` repo, set up your remote branch, create the article, and finally create a new pull request for approval and publishing. For these instructions, see the [Create new Windows Server articles using GitHub and Visual Studio Code](create-new-using-github.md) article.
 
-    - **Make large changes to an existing article.** To make substantial changes to an existing article, you can follow the instructions in the [Edit an existing Windows Server article using GitHub and Visual Studio Code](edit-existing-using-github.md) article.
+  - **Make large changes to an existing article.** To make substantial changes to an existing article, you can follow the instructions in the [Edit an existing Windows Server article using GitHub and Visual Studio Code](edit-existing-using-github.md) article.
 
-    - **Make minor changes to an existing article.** To make minor changes to an existing article, follow the instructions in this article.
+  - **Make minor changes to an existing article.** To make minor changes to an existing article, follow the instructions in this article.
 
   > [!IMPORTANT]
-  > All repositories published to Microsoft Docs have adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) or the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/code-of-conduct). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/). Or contact [[email protected]](mailto:[email protected]), or [[email protected]](mailto:[email protected]) with any questions or comments.
+  > All repositories published to Microsoft Learn have adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) or the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/code-of-conduct). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/). Or contact [[email protected]](mailto:[email protected]), or [[email protected]](mailto:[email protected]) with any questions or comments.
   >
   > Minor corrections or clarifications to documentation and code examples in public repositories are covered by our [Terms of use](/legal/termsofuse). New or significant changes generate a comment in the pull request, asking you to submit an online Contribution License Agreement (CLA) if you are not an employee of Microsoft. We need you to complete the online form before we can review or accept your pull request.
 

README.md

@@ -18,7 +18,7 @@ There are two separate locations where we keep Windows Server technical content.
 
 ## Public (`windowsserverdocs-pr`) and private (`windowsserverdocs`) repos
 
-These repos are actively managed and contain the source for Windows Server technical content published to [Microsoft Docs](https://learn.microsoft.com):
+These repos are actively managed and contain the source for Windows Server technical content published to [Microsoft Learn](https://learn.microsoft.com):
 
 - [Windows Server home page](https://learn.microsoft.com/windows-server/)
 - [Windows Server Essentials](https://learn.microsoft.com/windows-server-essentials)

WindowsServerDocs/identity/solution-guides/Dynamic-Access-Control--Scenario-Overview.md

@@ -58,5 +58,5 @@ The following scenarios and guidance are included as part of this content set:
 |**Planning**|- [Planning a Central Access Policy Deployment](./scenario--central-access-policy.md)<br>- [Plan for File Access Auditing](Plan-for-File-Access-Auditing.md)|
 |**Deployment**|- [Active Directory Deployment](../ad-ds/deploy/ad-ds-deployment.md)<br>- [File and Storage Services Deployment](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831487(v=ws.11))|
 |**Operations**|[Dynamic Access Control PowerShell Reference](/powershell/module/activedirectory/)|
-<!--|**Tools and settings**|[Data Classification Toolkit](/learn/modules/intro-to-data-classification-protection/)|-->
+<!--|**Tools and settings**|[Data Classification Toolkit](/training/modules/intro-to-data-classification-protection/)|-->
 |**Community resources**|[Directory Services Forum](/answers/topics/windows-active-directory.html)|