Fix table formatting per markdownlint (#39121)

Author: gewarren

docs/core/compatibility/6.0.md

@@ -71,10 +71,10 @@ For information on other breaking changes for containers in .NET 6, see [.NET 6
 | [Set timestamp on read-only file on Windows](core-libraries/6.0/set-timestamp-readonly-file.md) | ❌ | ✔️ |
 | [Standard numeric format parsing precision](core-libraries/6.0/numeric-format-parsing-handles-higher-precision.md) | ✔️ | ❌ |
 | [Static abstract members in interfaces](core-libraries/6.0/static-abstract-interface-methods.md) | ❌ | ✔️ |
-| [StringBuilder.Append overloads and evaluation order](core-libraries/6.0/stringbuilder-append-evaluation-order.md) | ❌ | ✔️
+| [StringBuilder.Append overloads and evaluation order](core-libraries/6.0/stringbuilder-append-evaluation-order.md) | ❌ | ✔️ |
 | [Strong-name APIs throw PlatformNotSupportedException](core-libraries/6.0/strong-name-signing-exceptions.md) | ❌ | ✔️ |
 | [System.Drawing.Common only supported on Windows](core-libraries/6.0/system-drawing-common-windows-only.md) | ❌ | ❌ |
-| [System.Security.SecurityContext is marked obsolete](core-libraries/6.0/securitycontext-obsolete.md) | ✔️ | ❌
+| [System.Security.SecurityContext is marked obsolete](core-libraries/6.0/securitycontext-obsolete.md) | ✔️ | ❌ |
 | [Task.FromResult may return singleton](core-libraries/6.0/task-fromresult-returns-singleton.md) | ❌ | ✔️ |
 | [Unhandled exceptions from a BackgroundService](core-libraries/6.0/hosting-exception-handling.md) | ✔️ | ❌ |
 

docs/core/compatibility/cryptography/5.0/instantiating-default-implementations-of-cryptographic-abstractions-not-supported.md

@@ -85,7 +85,7 @@ Best practice dictates that libraries that consume cryptographic primitives (suc
   | <xref:System.Security.Cryptography.HashAlgorithm.Create?displayProperty=nameWithType> | <xref:System.Security.Cryptography.SHA1.Create?displayProperty=nameWithType> | The SHA-1 algorithm is considered broken. Consider using a stronger algorithm if possible. Consult your security advisor for further guidance. |
   | <xref:System.Security.Cryptography.HMAC.Create?displayProperty=nameWithType> | <xref:System.Security.Cryptography.HMACSHA1.%23ctor> | The HMACSHA1 algorithm is discouraged for most modern applications. Consider using a stronger algorithm if possible. Consult your security advisor for further guidance. |
   | <xref:System.Security.Cryptography.KeyedHashAlgorithm.Create?displayProperty=nameWithType> | <xref:System.Security.Cryptography.HMACSHA1.%23ctor> | The HMACSHA1 algorithm is discouraged for most modern applications. Consider using a stronger algorithm if possible. Consult your security advisor for further guidance. |
-  | <xref:System.Security.Cryptography.SymmetricAlgorithm.Create?displayProperty=nameWithType> | <xref:System.Security.Cryptography.Aes.Create?displayProperty=nameWithType> |
+  | <xref:System.Security.Cryptography.SymmetricAlgorithm.Create?displayProperty=nameWithType> | <xref:System.Security.Cryptography.Aes.Create?displayProperty=nameWithType> | |
 
 - If you must continue to call the obsolete parameterless `Create()` overloads, you can suppress the `SYSLIB0007` warning in code.
 

docs/core/compatibility/globalization/5.0/listseparator-value-change.md

@@ -16,7 +16,7 @@ For all operating systems in .NET 5.0.1 and later versions, the values for <xref
 The following table summarizes the changes for <xref:System.Globalization.TextInfo.ListSeparator?displayProperty=nameWithType> values.
 
 | | .NET Framework<br/>.NET Core 1.0 - 3.1 | .NET 5 | .NET 5.0.1 |
--|-|-|-
+|-|-|-|-|
 | **Windows** | Obtain from NLS | Decimal separator from ICU.<br/>Can switch back to NLS. | Equivalent to NLS |
 | **Linux and macOS** | Decimal separator from ICU | Decimal separator from ICU | Equivalent to NLS |
 

docs/core/dependency-loading/loading-managed.md

@@ -16,18 +16,18 @@ The most common mechanism to trigger a managed assembly load is a static assembl
 
 The direct use of the following APIs will also trigger loads:
 
-|API  |Description  |`Active` <xref:System.Runtime.Loader.AssemblyLoadContext> |
-|---------|---------|---------|
+| API | Description | `Active` <xref:System.Runtime.Loader.AssemblyLoadContext> |
+|-----|-------------|-----------------------------------------------------------|
 |<xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyName%2A?displayProperty=nameWithType>|`Load-by-name`|The [this](../../csharp/language-reference/keywords/this.md) instance.|
 |<xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath%2A?displayProperty=nameWithType><br/><xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromNativeImagePath%2A?displayProperty=nameWithType>|Load from path.|The [this](../../csharp/language-reference/keywords/this.md) instance.|
-<xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromStream%2A?displayProperty=nameWithType>|Load from object.|The [this](../../csharp/language-reference/keywords/this.md) instance.|
+| <xref:System.Runtime.Loader.AssemblyLoadContext.LoadFromStream%2A?displayProperty=nameWithType>|Load from object.|The [this](../../csharp/language-reference/keywords/this.md) instance.|
 |<xref:System.Reflection.Assembly.LoadFile%2A?displayProperty=nameWithType>|Load from path in a new <xref:System.Runtime.Loader.AssemblyLoadContext> instance|The new <xref:System.Runtime.Loader.AssemblyLoadContext> instance.|
-<xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType>|Load from path in the <xref:System.Runtime.Loader.AssemblyLoadContext.Default%2A?displayProperty=nameWithType> instance.<br/>Adds an <xref:System.AppDomain.AssemblyResolve?displayProperty=nameWithType> handler. The handler will load the assembly's dependencies from its directory.|The <xref:System.Runtime.Loader.AssemblyLoadContext.Default%2A?displayProperty=nameWithType> instance.|
+| <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType>|Load from path in the <xref:System.Runtime.Loader.AssemblyLoadContext.Default%2A?displayProperty=nameWithType> instance.<br/>Adds an <xref:System.AppDomain.AssemblyResolve?displayProperty=nameWithType> handler. The handler will load the assembly's dependencies from its directory.|The <xref:System.Runtime.Loader.AssemblyLoadContext.Default%2A?displayProperty=nameWithType> instance.|
 |<xref:System.Reflection.Assembly.Load(System.Reflection.AssemblyName)?displayProperty=nameWithType><br/><xref:System.Reflection.Assembly.Load(System.String)?displayProperty=nameWithType><br/><xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=nameWithType>|`Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Runtime.Loader.AssemblyLoadContext> methods.|
 |<xref:System.Reflection.Assembly.Load(System.Byte[])?displayProperty=nameWithType><br/><xref:System.Reflection.Assembly.Load(System.Byte[],System.Byte[])?displayProperty=nameWithType>|Load from object in a new <xref:System.Runtime.Loader.AssemblyLoadContext> instance.|The new <xref:System.Runtime.Loader.AssemblyLoadContext> instance.|
-<xref:System.Type.GetType(System.String)?displayProperty=nameWithType><br/><xref:System.Type.GetType(System.String,System.Boolean)?displayProperty=nameWithType><br/><xref:System.Type.GetType(System.String,System.Boolean,System.Boolean)?displayProperty=nameWithType>|`Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Type.GetType%2A?displayProperty=nameWithType> methods with an `assemblyResolver` argument.|
-<xref:System.Reflection.Assembly.GetType%2A?displayProperty=nameWithType>|If type `name` describes an assembly qualified generic type, trigger a `Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Type.GetType%2A?displayProperty=nameWithType> when using assembly qualified type names.|
-<xref:System.Activator.CreateInstance(System.String,System.String)?displayProperty=nameWithType><br/><xref:System.Activator.CreateInstance(System.String,System.String,System.Object[])?displayProperty=nameWithType><br/><xref:System.Activator.CreateInstance(System.String,System.String,System.Boolean,System.Reflection.BindingFlags,System.Reflection.Binder,System.Object[],System.Globalization.CultureInfo,System.Object[])?displayProperty=nameWithType>|`Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Activator.CreateInstance%2A?displayProperty=nameWithType> methods taking a <xref:System.Type> argument.|
+| <xref:System.Type.GetType(System.String)?displayProperty=nameWithType><br/><xref:System.Type.GetType(System.String,System.Boolean)?displayProperty=nameWithType><br/><xref:System.Type.GetType(System.String,System.Boolean,System.Boolean)?displayProperty=nameWithType>|`Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Type.GetType%2A?displayProperty=nameWithType> methods with an `assemblyResolver` argument.|
+| <xref:System.Reflection.Assembly.GetType%2A?displayProperty=nameWithType>|If type `name` describes an assembly qualified generic type, trigger a `Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Type.GetType%2A?displayProperty=nameWithType> when using assembly qualified type names.|
+| <xref:System.Activator.CreateInstance(System.String,System.String)?displayProperty=nameWithType><br/><xref:System.Activator.CreateInstance(System.String,System.String,System.Object[])?displayProperty=nameWithType><br/><xref:System.Activator.CreateInstance(System.String,System.String,System.Boolean,System.Reflection.BindingFlags,System.Reflection.Binder,System.Object[],System.Globalization.CultureInfo,System.Object[])?displayProperty=nameWithType>|`Load-by-name`.|Inferred from caller.<br/>Prefer <xref:System.Activator.CreateInstance%2A?displayProperty=nameWithType> methods taking a <xref:System.Type> argument.|
 
 ## Algorithm
 

docs/core/diagnostics/collect-dumps-crash.md

@@ -10,15 +10,15 @@ Configuring your application to collect a dump on crash is done by setting speci
 
 The following table shows the environment variables you can configure for collecting dumps on a crash.
 
-|Environment variable|Description|Default value|
-|-------|---------|---|
+| Environment variable | Description | Default value |
+|----------------------|-------------|---------------|
 |`COMPlus_DbgEnableMiniDump` or `DOTNET_DbgEnableMiniDump`|If set to 1, enable core dump generation.|0|
 |`COMPlus_DbgMiniDumpType` or `DOTNET_DbgMiniDumpType`|Type of dump to be collected. For more information, see [Types of mini dumps](#types-of-mini-dumps).|2 (`Heap`)|
 |`COMPlus_DbgMiniDumpName` or `DOTNET_DbgMiniDumpName`|Path to a file to write the dump to. Ensure that the user under which the dotnet process is running has write permissions to the specified directory.|`/tmp/coredump.<pid>`|
 |`COMPlus_CreateDumpDiagnostics` or `DOTNET_CreateDumpDiagnostics`|If set to 1, enables diagnostic logging of dump process.|0|
-|`COMPlus_EnableCrashReport` or `DOTNET_EnableCrashReport`|(Requires .NET 6 or later; not supported on Windows.)<br/>If set to 1, the runtime generates a JSON-formatted crash report that includes information about the threads and stack frames of the crashing application. The crash report name is the dump path or name with *.crashreport.json* appended.
+|`COMPlus_EnableCrashReport` or `DOTNET_EnableCrashReport`|(Requires .NET 6 or later; not supported on Windows.)<br/>If set to 1, the runtime generates a JSON-formatted crash report that includes information about the threads and stack frames of the crashing application. The crash report name is the dump path or name with *.crashreport.json* appended.| |
 |`COMPlus_CreateDumpVerboseDiagnostics` or `DOTNET_CreateDumpVerboseDiagnostics`|(Requires .NET 7 or later.)<br/>If set to 1, enables verbose diagnostic logging of the dump process.|0|
-|`COMPlus_CreateDumpLogToFile` or `DOTNET_CreateDumpLogToFile`|(Requires .NET 7 or later.)<br/>The path of the file to which the diagnostic messages should be written. If unset, the diagnostic messages are written to the console of the crashing application.|
+|`COMPlus_CreateDumpLogToFile` or `DOTNET_CreateDumpLogToFile`|(Requires .NET 7 or later.)<br/>The path of the file to which the diagnostic messages should be written. | If unset, the diagnostic messages are written to the console of the crashing application. |
 
 > [!NOTE]
 > .NET 7 standardizes on the prefix `DOTNET_` instead of `COMPlus_` for these environment variables. However, the `COMPlus_` prefix will continue to work. If you're using a previous version of the .NET runtime, you should still use the `COMPlus_` prefix for environment variables.