Change docs.microsoft.com to learn.microsoft.com (#19994)

docs/building/linux.md

@@ -23,7 +23,7 @@ We use the [.NET Command-Line Interface][dotnet-cli] (`dotnet`) to build the man
 Installing the toolchain is as easy as running `Start-PSBootstrap` in PowerShell.
 Of course, this requires a self-hosted copy of PowerShell on Linux.
 
-Fortunately, this is as easy as [downloading and installing the package](https://docs.microsoft.com/powershell/scripting/install/installing-powershell-core-on-linux#binary-archives).
+Fortunately, this is as easy as [downloading and installing the package](https://learn.microsoft.com/en-us/powershell/scripting/install/install-other-linux#binary-archives).
 The `./tools/install-powershell.sh` script will also install the PowerShell package.
 
 In Bash:
@@ -53,7 +53,7 @@ The `Start-PSBootstrap` function does the following:
 
 If you want to use `dotnet` outside of `Start-PSBuild`, add `~/.dotnet` to your `PATH` environment variable.
 
-[dotnet-cli]: https://docs.microsoft.com/dotnet/core/tools/
+[dotnet-cli]: https://learn.microsoft.com/dotnet/core/tools/
 
 ## Build using our module
 

docs/building/windows-core.md

@@ -47,7 +47,7 @@ Install-Dotnet
 It removes the previously installed version of .NET CLI and installs the version that PowerShell Core depends on.
 If you have any problems installing `dotnet`, please see their [documentation][cli-docs].
 
-[dotnet-cli]: https://docs.microsoft.com/dotnet/core/tools/
+[dotnet-cli]: https://learn.microsoft.com/dotnet/core/tools/
 [cli-docs]: https://www.microsoft.com/net/core#windowscmd
 
 ## Build using our module

docs/cmdlet-example/command-line-simple-example.md

@@ -220,9 +220,9 @@ and macOS as well as Windows using the .NET Core 2.x SDK command-line tools.
 For more information on .NET Standard, check out the [documentation][net-std-docs]
 and the [.NET Standard YouTube channel][net-std-chan].
 
-[dotnet-cli]:    https://docs.microsoft.com/dotnet/core/tools/
+[dotnet-cli]:    https://learn.microsoft.com/dotnet/core/tools/
 [net-core-sdk]:  https://www.microsoft.com/net/download/core
-[net-std-docs]:  https://docs.microsoft.com/dotnet/standard/net-standard
+[net-std-docs]:  https://learn.microsoft.com/dotnet/standard/net-standard
 [net-std-chan]:  https://www.youtube.com/playlist?list=PLRAdsfhKI4OWx321A_pr-7HhRNk7wOLLY
 [pscore-os]:     https://github.com/powershell/powershell#get-powershell
 [readme]:        ../../README.md

docs/debugging/README.md

@@ -41,7 +41,7 @@ process named `powershell`, and will attach to it. If you need more fine-grained
 control, replace `processName` with `processId` and provide a PID. (Please be
 careful not to commit such a change.)
 
-[core-debug]: https://docs.microsoft.com/dotnet/core/tutorials/with-visual-studio-code#debug
+[core-debug]: https://learn.microsoft.com/dotnet/core/tutorials/with-visual-studio-code#debug
 [vscode]: https://code.visualstudio.com/
 [OmniSharp]: https://github.com/OmniSharp/omnisharp-vscode
 

docs/dev-process/coding-guidelines.md

@@ -88,7 +88,7 @@ We also run the [.NET code formatter tool](https://github.com/dotnet/codeformatt
 
 ### Documentation comments
 
-* Create documentation using [XML documentation comments](https://docs.microsoft.com/dotnet/csharp/language-reference/xmldoc/) so that Visual Studio and other IDEs can use IntelliSense to show quick information about types or members.
+* Create documentation using [XML documentation comments](https://learn.microsoft.com/dotnet/csharp/language-reference/xmldoc/) so that Visual Studio and other IDEs can use IntelliSense to show quick information about types or members.
 
 * Publicly visible types and their members must be documented.
   Internal and private members may use doc comments but it is not required.
@@ -189,16 +189,16 @@ See [CODEOWNERS](../../.github/CODEOWNERS) for more information about the area e
 * Consider using the `Interlocked` class instead of the `lock` statement to atomically change simple states. The `Interlocked` class provides better performance for updates that must be atomic.
 
 * Here are some useful links for your reference:
-  * [Framework Design Guidelines](https://docs.microsoft.com/dotnet/standard/design-guidelines/index) - Naming, Design and Usage guidelines including:
-    * [Arrays](https://docs.microsoft.com/dotnet/standard/design-guidelines/arrays)
-    * [Collections](https://docs.microsoft.com/dotnet/standard/design-guidelines/guidelines-for-collections)
-    * [Exceptions](https://docs.microsoft.com/dotnet/standard/design-guidelines/exceptions)
-  * [Best Practices for Developing World-Ready Applications](https://docs.microsoft.com/dotnet/core/extensions/best-practices-for-developing-world-ready-apps) - Unicode, Culture, Encoding and Localization.
-  * [Best Practices for Exceptions](https://docs.microsoft.com/dotnet/standard/exceptions/best-practices-for-exceptions)
-  * [Best Practices for Using Strings in .NET](https://docs.microsoft.com/dotnet/standard/base-types/best-practices-strings)
-  * [Best Practices for Regular Expressions in .NET](https://docs.microsoft.com/dotnet/standard/base-types/best-practices)
-  * [Serialization Guidelines](https://docs.microsoft.com/dotnet/standard/serialization/serialization-guidelines)
-  * [Managed Threading Best Practices](https://docs.microsoft.com/dotnet/standard/threading/managed-threading-best-practices)
+  * [Framework Design Guidelines](https://learn.microsoft.com/dotnet/standard/design-guidelines/index) - Naming, Design and Usage guidelines including:
+    * [Arrays](https://learn.microsoft.com/dotnet/standard/design-guidelines/arrays)
+    * [Collections](https://learn.microsoft.com/dotnet/standard/design-guidelines/guidelines-for-collections)
+    * [Exceptions](https://learn.microsoft.com/dotnet/standard/design-guidelines/exceptions)
+  * [Best Practices for Developing World-Ready Applications](https://learn.microsoft.com/dotnet/core/extensions/best-practices-for-developing-world-ready-apps) - Unicode, Culture, Encoding and Localization.
+  * [Best Practices for Exceptions](https://learn.microsoft.com/dotnet/standard/exceptions/best-practices-for-exceptions)
+  * [Best Practices for Using Strings in .NET](https://learn.microsoft.com/dotnet/standard/base-types/best-practices-strings)
+  * [Best Practices for Regular Expressions in .NET](https://learn.microsoft.com/dotnet/standard/base-types/best-practices)
+  * [Serialization Guidelines](https://learn.microsoft.com/dotnet/standard/serialization/serialization-guidelines)
+  * [Managed Threading Best Practices](https://learn.microsoft.com/dotnet/standard/threading/managed-threading-best-practices)
 
 ## Portable Code
 

docs/host-powershell/README.md

@@ -41,7 +41,7 @@ There is a special hosting scenario for native hosts,
 where Trusted Platform Assemblies (TPA) do not include PowerShell assemblies,
 such as the in-box `powershell.exe` in Nano Server and the Azure DSC host.
 
-For such hosting scenarios, the native host needs to bootstrap by calling [`PowerShellAssemblyLoadContextInitializer.SetPowerShellAssemblyLoadContext`](https://docs.microsoft.com/dotnet/api/system.management.automation.powershellassemblyloadcontextinitializer.setpowershellassemblyloadcontext).
+For such hosting scenarios, the native host needs to bootstrap by calling [`PowerShellAssemblyLoadContextInitializer.SetPowerShellAssemblyLoadContext`](https://learn.microsoft.com/dotnet/api/system.management.automation.powershellassemblyloadcontextinitializer.setpowershellassemblyloadcontext).
 When using this API, the native host can pass in the path to the directory that contains PowerShell assemblies.
 A handler will then be registered to the [`Resolving`](https://github.com/dotnet/corefx/blob/d6678e9653defe3cdfff26b2ff62135b6b22c77f/src/System.Runtime.Loader/ref/System.Runtime.Loader.cs#L38)
 event of the default load context to deal with the loading of assemblies from that directory.