Attempt to fix up problems

Author: agocke

xml/System.Reflection/Assembly.xml

@@ -4041,6 +4041,9 @@ This property is marked obsolete starting in .NET 5, and generates a compile-tim
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
+
+In .NET Core 2.0 and later, the target assembly will be loaded into the current <xref:System.Reflection.AssemblyLoadContext>. For more information on assembly loading, see <see cref="https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed#algorithm" />.
+
  <xref:System.IO.FileLoadException> is thrown if `assemblyRef` specifies the full assembly name and the first assembly that matches the simple name has a different version, culture, or public key token. The loader does not continue probing for other assemblies that match the simple name. Starting with .NET Framework 4, because execution of code in remote assemblies is disabled by default, a <xref:System.IO.FileLoadException> is also thrown if `assemblyRef` specifies a remote assembly. To enable execution of code loaded from remote locations, you can use the [`<loadFromRemoteSources>`](/dotnet/framework/configure-apps/file-schema/runtime/loadfromremotesources-element) configuration element.
 
 > [!NOTE]
@@ -4128,20 +4131,13 @@ Note: In <see href="https://go.microsoft.com/fwlink/?LinkID=247912">.NET for Win
         <param name="assemblyString">The long or short form of the assembly name.</param>
         <summary>Loads an assembly with the specified name.</summary>
         <returns>The loaded assembly.</returns>
-        <remarks FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0">
+        <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
-This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
-
-The assembly is loaded into the current AssemblyLoadContext.
-]]></format>
-        </remarks>
-        <remarks FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netstandard-2.0;netstandard-2.1netframework-4.8.1">
-          <format type="text/markdown"><![CDATA[
+In .NET Core 2.0 and later, the target assembly will be loaded into the current <xref:System.Reflection.AssemblyLoadContext>. For more information on assembly loading, see <see cref="https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed#algorithm" />.
 
-## Remarks
 To load the correct assembly, it's recommended to call the `Load` method by passing the long form of the assembly name. The long form of an assembly name consists of its simple name (such as "System" for the System.dll assembly) along with its version, culture, public key token, and optionally its processor architecture. It corresponds to the assembly's <xref:System.Reflection.Assembly.FullName%2A> property. The following example illustrates the use of a long name to load the System.dll assembly for the .NET Framework 4:
 
  :::code language="csharp" source="~/snippets/csharp/System.Reflection/Assembly/Load/load11.cs" id="Snippet1":::
@@ -4241,20 +4237,12 @@ To load the correct assembly, it's recommended to call the `Load` method by pass
         <param name="rawSymbolStore">A byte array that contains the raw bytes representing the symbols for the assembly.</param>
         <summary>Loads the assembly with a common object file format (COFF)-based image containing an emitted assembly, optionally including symbols for the assembly.</summary>
         <returns>The loaded assembly.</returns>
-        <remarks FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0">
+        <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
-This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
-
-The assembly is loaded into the current AssemblyLoadContext.
-]]></format>
-        </remarks>
-        <remarks FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netstandard-2.0;netstandard-2.1netframework-4.8.1">
-          <format type="text/markdown"><![CDATA[
-
-## Remarks
+ In .NET Core 2.0 and later, the target assembly will be loaded into the current <xref:System.Reflection.AssemblyLoadContext>. For more information on assembly loading, see <see cref="https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed#algorithm" />.
 
  This method overload always creates a new <xref:System.Reflection.Assembly> object in its own isolated load context.
 
@@ -4640,20 +4628,15 @@ The assembly is loaded using the supplied evidence. The raw bytes representing t
         <param name="path">The fully qualified path of the file to load.</param>
         <summary>Loads the contents of an assembly file on the specified path.</summary>
         <returns>The loaded assembly.</returns>
-        <remarks FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0">
+        <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
-This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
+ This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
 
-The assembly is loaded into a new AssemblyLoadContext created for this purpose.
-]]></format>
-        </remarks>
-        <remarks FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netstandard-2.0;netstandard-2.1netframework-4.8.1">
-          <format type="text/markdown"><![CDATA[
+ The assembly is loaded into a new AssemblyLoadContext created for this purpose. For more information on assembly loading, see <see cref="https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed#algorithm" />.
 
-## Remarks
  Use the <xref:System.Reflection.Assembly.LoadFile%2A> method to load and examine assemblies that have the same identity, but are located in different paths. <xref:System.Reflection.Assembly.LoadFile%2A> does not load files into the load-from  context, and does not resolve dependencies using the load path, as the <xref:System.Reflection.Assembly.LoadFrom%2A> method does. <xref:System.Reflection.Assembly.LoadFile%2A> is useful in this limited scenario because <xref:System.Reflection.Assembly.LoadFrom%2A> cannot be used to load assemblies that have the same identities but different paths; it will load only the first such assembly.
 
 Starting with .NET Framework 4, if `path` specifies an assembly in a remote location, assembly loading is disabled by default, and the `LoadFile` method throws a <xref:System.IO.FileLoadException>. To enable execution of code loaded from remote locations, you can use the [`<loadFromRemoteSources>`](/dotnet/framework/configure-apps/file-schema/runtime/loadfromremotesources-element) configuration element.
@@ -4820,22 +4803,19 @@ Starting with .NET Framework 4, the ability to execute code in assemblies loaded
         <param name="assemblyFile">The name or path of the file that contains the manifest of the assembly.</param>
         <summary>Loads an assembly given its file name or path.</summary>
         <returns>The loaded assembly.</returns>
-        <remarks FrameworkAlternate="netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;net-5.0;net-6.0;net-7.0;net-8.0;net-9.0">
+        <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
-This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
+ This API is present in .NET Core for compatibility, but it is recommended to use <xref:System.Reflection.AssemblyLoadContext> overloads in .NET Core 2.0 and later.
 
-The assembly is loaded into the default AssemblyLoadContext.
-]]></format>
-        </remarks>
-        <remarks FrameworkAlternate="netframework-1.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netstandard-2.0;netstandard-2.1netframework-4.8.1">
-          <format type="text/markdown"><![CDATA[
+ The assembly is loaded into the default AssemblyLoadContext. For more information on assembly loading, see <see cref="https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/loading-managed#algorithm" />.
 
-## Remarks
  The `assemblyFile` parameter must refer to a URI without escape characters. This method supplies escape characters for all invalid characters in the URI.
 
+ Before .NET 5, the following applied:
+
 > [!NOTE]
 >  File transfer protocol (FTP) is not supported. If the URI supplied for `assemblyFile` is an FTP address, the assembly is not loaded. No exception is thrown.