Update docs.microsoft.com to learn.microsoft.com. (dotnet#14774)

* Update docs.microsoft.com to learn.microsoft.com.

* Correct links in FSharp.Core.

* Scrub en-us

DEVGUIDE.md

@@ -247,7 +247,7 @@ Where `<version>` corresponds to the latest Visual Studio version on your machin
 
 * Coding conventions vary from file to file
 
-* Format using [the F# style guide](https://docs.microsoft.com/en-us/dotnet/fsharp/style-guide/)
+* Format using [the F# style guide](https://learn.microsoft.com/dotnet/fsharp/style-guide/)
 
 * Avoid tick identifiers like `body'`. They are generally harder to read and can't be inspected in the debugger as things stand. Generally use R suffix instead, e.g. `bodyR`. The R can stand for "rewritten" or "result"
 
@@ -427,4 +427,4 @@ See the "Debugging The Compiler" section of this [article](https://medium.com/@w
 
 If you are behind a proxy server, NuGet client tool must be configured to use it:
 
-See the Nuget config file documention for use with a proxy server [https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file)
+See the Nuget config file documention for use with a proxy server [https://learn.microsoft.com/nuget/reference/nuget-config-file](https://learn.microsoft.com/nuget/reference/nuget-config-file)

README.md

@@ -86,7 +86,7 @@ build.cmd -noVisualStudio
 
 ### Докуметація для Ф# громади
 
-* [The F# Documentation](https://docs.microsoft.com/dotnet/fsharp/) is the primary documentation for F#. The source for the content is [here](https://github.com/dotnet/docs/tree/main/docs/fsharp).
+* [The F# Documentation](https://learn.microsoft.com/dotnet/fsharp/) is the primary documentation for F#. The source for the content is [here](https://github.com/dotnet/docs/tree/main/docs/fsharp).
 
 * [The F# Language Design Process](https://github.com/fsharp/fslang-design/) is the fundamental design process for the language, from [suggestions](https://github.com/fsharp/fslang-suggestions) to completed RFCs.  There are also [tooling RFCs](https://github.com/fsharp/fslang-design/tree/main/tooling) for some topics where cross-community co-operation and visibility is most useful.
 
@@ -242,7 +242,7 @@ Additionally, you can use the `#fsharp` tag on Twitter if you have general F# qu
 
 If you're curious about F# itself, check out these links:
 
-* [What is F#](https://docs.microsoft.com/dotnet/fsharp/what-is-fsharp)
-* [Get started with F#](https://docs.microsoft.com/dotnet/fsharp/get-started/)
+* [What is F#](https://learn.microsoft.com/dotnet/fsharp/what-is-fsharp)
+* [Get started with F#](https://learn.microsoft.com/dotnet/fsharp/get-started/)
 * [F# Software Foundation](https://fsharp.org)
 * [F# Testimonials](https://fsharp.org/testimonials)

TESTGUIDE.md

@@ -228,7 +228,7 @@ When you switch branches, certain temporary files, as well as the .NET version (
 git clean -xdf -e .vs
 ```
 
-If you get "file in use" errors during cleaning, make sure to close Visual Studio and any running `dotnet.exe` and `VBCSCompiler.exe`, esp those that show up at the bottom of [Process Explorer](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) without parent process.
+If you get "file in use" errors during cleaning, make sure to close Visual Studio and any running `dotnet.exe` and `VBCSCompiler.exe`, esp those that show up at the bottom of [Process Explorer](https://learn.microsoft.com/sysinternals/downloads/process-explorer) without parent process.
 
 #### Running tests on release/dev16.6 etc branches
 
@@ -250,7 +250,7 @@ The following are common errors that users have encountered while running tests
 
 ### Error that a file cannot be accessed
 
-The build often leaves dangling processes like `HostedCompilerServer.exe`, `VBCSCompiler.exe` or `MSBuild.exe`. In [Process Explorer](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) you can see these processes having no parent process anymore. You can also use this to kill such processes. A typical error looks like and contains the process IDs (here 23152, 25252 and 24704):
+The build often leaves dangling processes like `HostedCompilerServer.exe`, `VBCSCompiler.exe` or `MSBuild.exe`. In [Process Explorer](https://learn.microsoft.com/sysinternals/downloads/process-explorer) you can see these processes having no parent process anymore. You can also use this to kill such processes. A typical error looks like and contains the process IDs (here 23152, 25252 and 24704):
 
 > C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(4364,5): error MSB3026: Could not copy "D:\Projects\FSharp\artifacts\bin\FSharp.Core\Debug\net45\FSharp.Core.dll" to "D:\Projects\FSharp\tests\fsharpqa\testenv\bin\FSharp.Core.dll". Beginning retry 1 in 1000ms. The process cannot access the file 'D:\Projects\FSharp\tests\fsharpqa\testenv\bin\FSharp.Core.dll' because it is being used by another process. The file is locked by: "HostedCompilerServer (23152), HostedCompilerServer (25252), HostedCompilerServer (24704)" [D:\Projects\OpenSource\FSharp\tests\fsharpqa\testenv\src\ILComparer\ILComparer.fsproj]
 

docs/debug-emit.md

@@ -310,7 +310,7 @@ Breakpoints tend to be less problematic.
 
 ### FeeFee and F00F00 debug points (Hidden and JustMyCodeWithNoSource)
 
-Some fragments of code use constructs generate calls and other IL code that should not have debug points and not participate in "Step Into", for example. These are generated in IlxGen as "FeeFee" debug points. See the [the Portable PDB spec linked here](https://docs.microsoft.com/en-us/dotnet/api/system.reflection.metadata.sequencepoint.hiddenline?view=net-5.0).
+Some fragments of code use constructs generate calls and other IL code that should not have debug points and not participate in "Step Into", for example. These are generated in IlxGen as "FeeFee" debug points. See the [the Portable PDB spec linked here](https://learn.microsoft.com/dotnet/api/system.reflection.metadata.sequencepoint.hiddenline?view=net-5.0).
 
 > TODO: There is also the future prospect of generating `JustMyCodeWithNoSource` (0xF00F00) debug points but these are not yet emitted by F#.  We should check what this is and when the C# compiler emits these.
 

docs/fcs/interactive.fsx

@@ -273,7 +273,7 @@ Evaluating code in using FsiEvaluationSession generates a .NET dynamic assembly
 You can make generated code collectible by passing `collectible=true`.  However, code will only
 be collected if there are no outstanding object references involving types, for example
 `FsiValue` objects returned by `EvalExpression`, and you must have disposed the `FsiEvaluationSession`.
-See also [Restrictions on Collectible Assemblies](https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/dd554932(v=vs.100)#restrictions).
+See also [Restrictions on Collectible Assemblies](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/dd554932(v=vs.100)#restrictions).
 
 The example below shows the creation of 200 evaluation sessions. Note that `collectible=true` and
 `use session = ...` are both used.

docs/fsharp-core-notes.md

@@ -96,7 +96,7 @@ If you do have an explicit FSharp.Core reference in your C# project that you **n
 
 ## Guidance for older projects, compilers, and tools
 
-Modern .NET development, including F#, uses SDK-style projects. You can read about that here: https://docs.microsoft.com/dotnet/core/project-sdk/overview
+Modern .NET development, including F#, uses SDK-style projects. You can read about that here: https://learn.microsoft.com/dotnet/core/project-sdk/overview
 
 If you are not using SDK-style projects F# projects and/or have an older toolset, the following guidance applies.
 

eng/common/templates/job/job.yml

@@ -2,7 +2,7 @@
 # and some (Microbuild) should only be applied to non-PR cases for internal builds.
 
 parameters:
-# Job schema parameters - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
+# Job schema parameters - https://learn.microsoft.com/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
   cancelTimeoutInMinutes: ''
   condition: ''
   container: ''

eng/common/templates/job/onelocbuild.yml

@@ -2,7 +2,7 @@ parameters:
   # Optional: dependencies of the job
   dependsOn: ''
 
-  # Optional: A defined YAML pool - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#pool
+  # Optional: A defined YAML pool - https://learn.microsoft.com/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#pool
   pool: ''
 
   CeapexPat: $(dn-bot-ceapex-package-r) # PAT for the loc AzDO instance https://dev.azure.com/ceapex

eng/common/templates/job/publish-build-assets.yml

@@ -13,7 +13,7 @@ parameters:
   # Optional: Include PublishBuildArtifacts task
   enablePublishBuildArtifacts: false
 
-  # Optional: A defined YAML pool - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#pool
+  # Optional: A defined YAML pool - https://learn.microsoft.com/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#pool
   pool: {}
 
   # Optional: should run as a public build even in the internal project

eng/common/templates/jobs/codeql-build.yml

@@ -1,7 +1,7 @@
 parameters:
   # See schema documentation in /Documentation/AzureDevOps/TemplateSchema.md
   continueOnError: false
-  # Required: A collection of jobs to run - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
+  # Required: A collection of jobs to run - https://learn.microsoft.com/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
   jobs: []
   # Optional: if specified, restore and use this version of Guardian instead of the default.
   overrideGuardianVersion: ''

eng/common/templates/jobs/jobs.yml

@@ -21,7 +21,7 @@ parameters:
     # Optional: Include toolset dependencies in the generated graph files
     includeToolset: false
 
-  # Required: A collection of jobs to run - https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
+  # Required: A collection of jobs to run - https://learn.microsoft.com/azure/devops/pipelines/yaml-schema?view=vsts&tabs=schema#job
   jobs: []
 
   # Optional: Override automatically derived dependsOn value for "publish build assets" job

eng/common/tools.ps1

@@ -497,7 +497,7 @@ function InitializeXCopyMSBuild([string]$packageVersion, [bool]$install) {
 #       Two part minimal VS version, e.g. "15.9", "16.0", etc.
 #   "components": ["componentId1", "componentId2", ...]
 #       Array of ids of workload components that must be available in the VS instance.
-#       See e.g. https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-enterprise?view=vs-2017
+#       See e.g. https://learn.microsoft.com/visualstudio/install/workload-component-id-vs-enterprise?view=vs-2017
 #
 # Returns JSON describing the located VS instance (same format as returned by vswhere),
 # or $null if no instance meeting the requirements is found on the machine.

release-notes.md

@@ -2245,19 +2245,19 @@ Includes commits up to `3385e58aabc91368c8e1f551650ba48705aaa285`
 Features Added in F# Language Versions
 ======================================
 
-# [F# 4.7](https://docs.microsoft.com/en-us/dotnet/fsharp/whats-new/fsharp-47)
+# [F# 4.7](https://learn.microsoft.com/dotnet/fsharp/whats-new/fsharp-47)
 
 - Compiler support for `LangVersion`
 - Implicit `yield`s
 - No more required double underscore (wildcard identifier)
 - Indentation relaxations for parameters passed to constructors and static methods
 
-# [F# 4.6](https://docs.microsoft.com/en-us/dotnet/fsharp/whats-new/fsharp-46)
+# [F# 4.6](https://learn.microsoft.com/dotnet/fsharp/whats-new/fsharp-46)
 
 - Anonymous records
 - `ValueOption` module functions
 
-# [F# 4.5](https://docs.microsoft.com/en-us/dotnet/fsharp/whats-new/fsharp-45)
+# [F# 4.5](https://learn.microsoft.com/dotnet/fsharp/whats-new/fsharp-45)
 
 - Versioning alignment of binary, package, and language
 - Support for `Span<'T>` and related types
@@ -2329,13 +2329,13 @@ Features Added in F# Language Versions
 - Native interoperability
 - Computation expressions
 
-# [F# 1.1](https://docs.microsoft.com/en-us/archive/blogs/dsyme/a-taste-of-whats-new-in-f-1-1)
+# [F# 1.1](https://learn.microsoft.com/archive/blogs/dsyme/a-taste-of-whats-new-in-f-1-1)
 
 - Interactive environment
 - Object programming
 - Encapsulation Extensions
 
-# [F# 1.0](https://docs.microsoft.com/en-us/archive/blogs/dsyme/welcome-to-dons-f-blog)
+# [F# 1.0](https://learn.microsoft.com/archive/blogs/dsyme/welcome-to-dons-f-blog)
 
 - Discriminated unions
 - Records

src/Compiler/Driver/FxResolver.fs

@@ -853,7 +853,7 @@ type internal FxResolver
             //      System.Runtime.InteropServices.RuntimeInformation.RuntimeIdentifier
             // On Desktop framework compile it using osplatform+processarch+
             // Computer valid dotnet-rids for this environment:
-            //      https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
+            //      https://learn.microsoft.com/dotnet/core/rid-catalog
             //
             // Where rid is: win, win-x64, win-x86, osx-x64, linux-x64 etc ...
             let runningRid =

src/Compiler/Driver/XmlDocFileWriter.fsi

@@ -10,7 +10,7 @@ module XmlDocWriter =
     /// Writes the XML document signature to the XmlDocSig property of each
     /// element (field, union case, etc) of the specified compilation unit.
     /// The XmlDocSig is the unique identifier of this XmlDoc in the generated Xml documentation file.
-    /// The full format is described at https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/documentation-comments#id-string-format
+    /// The full format is described at https://learn.microsoft.com/dotnet/csharp/language-reference/language-specification/documentation-comments#id-string-format
     val ComputeXmlDocSigs: tcGlobals: TcGlobals * generatedCcu: CcuThunk -> unit
 
     /// Writes the XmlDocSig property of each element (field, union case, etc)

src/Compiler/Utilities/Activity.fsi

@@ -5,7 +5,7 @@ namespace FSharp.Compiler.Diagnostics
 open System
 
 /// For activities following the dotnet distributed tracing concept
-/// https://learn.microsoft.com/en-us/dotnet/core/diagnostics/distributed-tracing-concepts?source=recommendations
+/// https://learn.microsoft.com/dotnet/core/diagnostics/distributed-tracing-concepts?source=recommendations
 [<RequireQualifiedAccess>]
 module internal Activity =
 

src/Compiler/Utilities/RidHelpers.fs

@@ -5,7 +5,7 @@ open System.Runtime.InteropServices
 module internal RidHelpers =
 
     // Computer valid dotnet-rids for this environment:
-    //      https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
+    //      https://learn.microsoft.com/dotnet/core/rid-catalog
     //
     // Where rid is: win, win-x64, win-x86, osx-x64, linux-x64 etc ...
     let probingRids, baseRid, platformRid =

src/Compiler/Utilities/illib.fs

@@ -63,7 +63,7 @@ module internal PervasiveAutoOpens =
 
     let inline (===) x y = LanguagePrimitives.PhysicalEquality x y
 
-    /// Per the docs the threshold for the Large Object Heap is 85000 bytes: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/large-object-heap#how-an-object-ends-up-on-the-large-object-heap-and-how-gc-handles-them
+    /// Per the docs the threshold for the Large Object Heap is 85000 bytes: https://learn.microsoft.com/dotnet/standard/garbage-collection/large-object-heap#how-an-object-ends-up-on-the-large-object-heap-and-how-gc-handles-them
     /// We set the limit to be 80k to account for larger pointer sizes for when F# is running 64-bit.
     let LOH_SIZE_THRESHOLD_BYTES = 80_000
 

src/Compiler/Utilities/illib.fsi

@@ -44,7 +44,7 @@ module internal PervasiveAutoOpens =
 
     val inline (===): x: 'a -> y: 'a -> bool when 'a: not struct
 
-    /// Per the docs the threshold for the Large Object Heap is 85000 bytes: https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/large-object-heap#how-an-object-ends-up-on-the-large-object-heap-and-how-gc-handles-them
+    /// Per the docs the threshold for the Large Object Heap is 85000 bytes: https://learn.microsoft.com/dotnet/standard/garbage-collection/large-object-heap#how-an-object-ends-up-on-the-large-object-heap-and-how-gc-handles-them
     /// We set the limit to be 80k to account for larger pointer sizes for when F# is running 64-bit.
     val LOH_SIZE_THRESHOLD_BYTES: int
 

src/FSharp.Core/Query.fsi

@@ -16,7 +16,7 @@ namespace Microsoft.FSharp.Linq
     ///
     /// <namespacedoc><summary>
     ///   Library functionality for F# query syntax and interoperability with .NET LINQ Expressions. See
-    ///   also <a href="https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/query-expressions">F# Query Expressions</a> in the F# Language Guide.
+    ///   also <a href="https://learn.microsoft.com/dotnet/fsharp/language-reference/query-expressions">F# Query Expressions</a> in the F# Language Guide.
     /// </summary></namespacedoc>
     [<NoComparison; NoEquality; Sealed>]
     type QuerySource<'T, 'Q> =
@@ -31,7 +31,7 @@ namespace Microsoft.FSharp.Linq
         member Source: seq<'T>
 
     /// The type used to support the F# query syntax. Use 'query { ... }' to use the query syntax. See
-    /// also <a href="https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/query-expressions">F# Query Expressions</a> in the F# Language Guide.
+    /// also <a href="https://learn.microsoft.com/dotnet/fsharp/language-reference/query-expressions">F# Query Expressions</a> in the F# Language Guide.
     [<Class>]
     type QueryBuilder =
         /// <summary>Create an instance of this builder. Use 'query { ... }' to use the query syntax.</summary>

src/FSharp.Core/array.fsi

@@ -10,7 +10,7 @@ open System.Collections.Generic
 /// <summary>Contains operations for working with arrays.</summary>
 ///
 /// <remarks>
-///  See also <a href="https://docs.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.
+///  See also <a href="https://learn.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.
 /// </remarks>
 [<CompilationRepresentation(CompilationRepresentationFlags.ModuleSuffix)>]
 [<RequireQualifiedAccess>]

src/FSharp.Core/array2.fsi

@@ -9,7 +9,7 @@ open Microsoft.FSharp.Core
 /// <summary>Contains operations for working with 2-dimensional arrays.</summary>
 ///
 /// <remarks>
-///  <para>See also <a href="https://docs.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.</para>
+///  <para>See also <a href="https://learn.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.</para>
 ///
 /// <para>F# and CLI multi-dimensional arrays are typically zero-based.
 /// However, CLI multi-dimensional arrays used in conjunction with external

src/FSharp.Core/array3.fsi

@@ -10,7 +10,7 @@ open Microsoft.FSharp.Core.Operators
 /// <summary>Contains operations for working with rank 3 arrays.</summary>
 ///
 /// <remarks>
-///  See also <a href="https://docs.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.
+///  See also <a href="https://learn.microsoft.com/dotnet/fsharp/language-reference/arrays">F# Language Guide - Arrays</a>.
 /// </remarks>
 [<CompilationRepresentation(CompilationRepresentationFlags.ModuleSuffix)>]
 [<RequireQualifiedAccess>]