Update *.md files to address some correctness/style issues reported by the next markdownlint release's MD037/no-space-in-emphasis rule. (#18341)

Author: DavidAnson

docs/csharp/misc/cs0436.md

@@ -10,7 +10,7 @@ ms.assetid: c4135d9d-3511-4bbc-9540-48c2091f869c
 # Compiler Warning (level 2) CS0436
 The type 'type' in 'assembly' conflicts with the imported type 'type2' in 'assembly'. Using the type defined in 'assembly'.  
 
- This warning is issued when a type in a source file (file_2) conflicts with an imported type in file _1. The compiler uses the one in the source file.  
+ This warning is issued when a type in a source file (file_2) conflicts with an imported type in file_1. The compiler uses the one in the source file.  
 
 ## Example  
 

docs/csharp/misc/cs0437.md

@@ -10,7 +10,7 @@ ms.assetid: cba5c9b6-a0bc-4f19-b1f0-c1f66436ee91
 # Compiler Warning (level 2) CS0437
 The type 'type' in 'assembly2' conflicts with the imported namespace 'namespace' in 'fassembly1'. Using the type defined in 'assembly'.  
 
- This warning is issued when a type in a source file, file_2, conflicts with an imported namespace in file _1. The compiler uses the type in the source file.  
+ This warning is issued when a type in a source file, file_2, conflicts with an imported namespace in file_1. The compiler uses the type in the source file.  
 
 ## Example  
 

docs/framework/data/adonet/ef/language-reference/how-entity-sql-differs-from-transact-sql.md

@@ -104,8 +104,8 @@ SELET Tab.a FROM Tab
 p.Address.City
 ```  
 
-## No Support for *  
- Transact-SQL supports the unqualified * syntax as an alias for the entire row, and the qualified \* syntax (t.\*) as a shortcut for the fields of that table. In addition, Transact-SQL allows for a special count(\*) aggregate, which includes nulls.  
+## No Support for \*  
+ Transact-SQL supports the unqualified \* syntax as an alias for the entire row, and the qualified \* syntax (t.\*) as a shortcut for the fields of that table. In addition, Transact-SQL allows for a special count(\*) aggregate, which includes nulls.  
 
  [!INCLUDE[esql](../../../../../../includes/esql-md.md)] does not support the * construct. Transact-SQL queries of the form `select * from T` and `select T1.* from T1, T2...` can be expressed in [!INCLUDE[esql](../../../../../../includes/esql-md.md)] as `select value t from T as t` and `select value t1 from T1 as t1, T2 as t2...`, respectively. Additionally, these constructs handle inheritance (value substitutability), while the `select *` variants are restricted to top-level properties of the declared type.  
 

docs/framework/migration-guide/net-framework-4-migration-issues.md

@@ -32,8 +32,8 @@ You can specify one or more of the following `sources`.
 | Source | Description |
 | ------ | ----------- |
 |`file`[,`target`]|Copies the contents of `file` (a module) to the file name specified by `target`. After copying, *Al.exe* compiles `target` into an assembly.|
-|**/embed[resource]:** `file`[,`name`[,`private`]]|Embeds the resource specified by `file` in the image that contains the assembly manifest; *Al.exe* copies the contents of `file` into the portable executable (PE) image.<br /><br /> The `name` parameter is an internal identifier for the resource. By default, resources are public in the assembly (visible to other assemblies). Specifying `private` makes the resource not visible to other assemblies.<br /><br /> If `file` is a .NET Framework resource file created, for example, by the [Resource File Generator (*Resgen.exe*)](resgen-exe-resource-file-generator.md) or in the development environment, it can be accessed with members in the <xref:System.Resources>. For more information, see <xref:System.Resources.ResourceManager>. For all other resources, use the `GetManifestResource`* methods in the <xref:System.Reflection.Assembly> to access the resource at run time.<br /><br /> If only resource files are passed to *Al.exe*, the output file is a satellite resource assembly.|
-|**/link[resource]:** `file`[,`name`[,`target`[,`private`]]]|Links a resource file to an assembly. The resource specified by `file` becomes part of the assembly; the file is not copied. The `file` parameter can be in any file format. For example, you can specify a native DLL as the `file` parameter. This will make the native DLL part of the assembly so that it can be installed into the global assembly cache and accessed from managed code in the assembly. You can also do this by using the **/linkresource** compiler option. For more information, see [-linkresource (C# Compiler Options)](../../csharp/language-reference/compiler-options/linkresource-compiler-option.md).<br /><br /> The `name` parameter is an internal identifier for the resource. The `target` parameter specifies a path and file name into which *Al.exe* copies the `file`*.* After copying, *Al.exe* compiles `target` into an assembly. By default, resources are public in the assembly (visible to other assemblies). Specifying `private` makes the resource not visible to other assemblies.<br /><br /> If `file` is a .NET Framework resource file created, for example, by the Resource File Generator (*Resgen.exe*) or in the development environment, it can be accessed with members in the <xref:System.Resources> namespace. For more information, see <xref:System.Resources.ResourceManager>. For all other resources, use the `GetManifestResource` * methods in the <xref:System.Reflection.Assembly> class to access the resource at run time.<br /><br /> If only resource files are passed to *Al.exe*, the output file is a satellite resource assembly.|
+|**/embed[resource]:** `file`[,`name`[,`private`]]|Embeds the resource specified by `file` in the image that contains the assembly manifest; *Al.exe* copies the contents of `file` into the portable executable (PE) image.<br /><br /> The `name` parameter is an internal identifier for the resource. By default, resources are public in the assembly (visible to other assemblies). Specifying `private` makes the resource not visible to other assemblies.<br /><br /> If `file` is a .NET Framework resource file created, for example, by the [Resource File Generator (*Resgen.exe*)](resgen-exe-resource-file-generator.md) or in the development environment, it can be accessed with members in the <xref:System.Resources>. For more information, see <xref:System.Resources.ResourceManager>. For all other resources, use the `GetManifestResource*` methods in the <xref:System.Reflection.Assembly> to access the resource at run time.<br /><br /> If only resource files are passed to *Al.exe*, the output file is a satellite resource assembly.|
+|**/link[resource]:** `file`[,`name`[,`target`[,`private`]]]|Links a resource file to an assembly. The resource specified by `file` becomes part of the assembly; the file is not copied. The `file` parameter can be in any file format. For example, you can specify a native DLL as the `file` parameter. This will make the native DLL part of the assembly so that it can be installed into the global assembly cache and accessed from managed code in the assembly. You can also do this by using the **/linkresource** compiler option. For more information, see [-linkresource (C# Compiler Options)](../../csharp/language-reference/compiler-options/linkresource-compiler-option.md).<br /><br /> The `name` parameter is an internal identifier for the resource. The `target` parameter specifies a path and file name into which *Al.exe* copies the `file`*.* After copying, *Al.exe* compiles `target` into an assembly. By default, resources are public in the assembly (visible to other assemblies). Specifying `private` makes the resource not visible to other assemblies.<br /><br /> If `file` is a .NET Framework resource file created, for example, by the Resource File Generator (*Resgen.exe*) or in the development environment, it can be accessed with members in the <xref:System.Resources> namespace. For more information, see <xref:System.Resources.ResourceManager>. For all other resources, use the `GetManifestResource*` methods in the <xref:System.Reflection.Assembly> class to access the resource at run time.<br /><br /> If only resource files are passed to *Al.exe*, the output file is a satellite resource assembly.|
 
 You can specify the following `options`; you must specify **/out**.
 

docs/framework/tools/al-exe-assembly-linker.md

@@ -36,7 +36,7 @@ HRESULT RequestProfilerDetach(
 |HRESULT|Description|  
 |-------------|-----------------|  
 |S_OK|The detach request is valid, and the detach procedure is now continuing on another thread. When the detach is fully complete, a `ProfilerDetachSucceeded` event is issued.|  
-|E_ CORPROF_E_CALLBACK3_REQUIRED|The profiler failed an [IUnknown::QueryInterface](/windows/win32/api/unknwn/nf-unknwn-iunknown-queryinterface(q)) attempt for the [ICorProfilerCallback3](icorprofilercallback3-interface.md) interface, which it must implement to support the detach operation. Detach was not attempted.|  
+|E_CORPROF_E_CALLBACK3_REQUIRED|The profiler failed an [IUnknown::QueryInterface](/windows/win32/api/unknwn/nf-unknwn-iunknown-queryinterface(q)) attempt for the [ICorProfilerCallback3](icorprofilercallback3-interface.md) interface, which it must implement to support the detach operation. Detach was not attempted.|  
 |CORPROF_E_IMMUTABLE_FLAGS_SET|Detachment is impossible because the profiler set immutable flags at startup. Detachment was not attempted; the profiler is still fully attached.|  
 |CORPROF_E_IRREVERSIBLE_INSTRUMENTATION_PRESENT|Detachment is impossible because the profiler used instrumented Microsoft intermediate language (MSIL) code, or inserted `enter`/`leave` hooks. Detachment was not attempted; the profiler is still fully attached.<br /><br /> **Note** Instrumented MSIL is code is code that is provided by the profiler using the [SetILFunctionBody](icorprofilerinfo-setilfunctionbody-method.md) method.|  
 |CORPROF_E_RUNTIME_UNINITIALIZED|The runtime has not been initialized yet in the managed application. (That is, the runtime has not been fully loaded.) This error code may be returned when detachment is requested inside the profiler callback's [ICorProfilerCallback::Initialize](icorprofilercallback-initialize-method.md) method.|  

docs/framework/unmanaged-api/profiling/icorprofilerinfo3-requestprofilerdetach-method.md

@@ -537,11 +537,14 @@ query {
 <td><code>EXISTS</code>
 <br />
 
+<!-- markdownlint-capture -->
+<!-- markdownlint-disable no-space-in-emphasis -->
 <pre><code class="lang-sql">SELECT * FROM Student
 WHERE EXISTS
   (SELECT * FROM CourseSelection
    WHERE CourseSelection.StudentID = Student.StudentID)
 </code></pre>
+<!-- markdownlint-restore -->
 </td>
 
 <td>
@@ -602,11 +605,14 @@ query {
 </td></tr><tr><td>
 Grouping with count condition.<br/>
 
+<!-- markdownlint-capture -->
+<!-- markdownlint-disable no-space-in-emphasis -->
 <pre><code class="lang-sql">SELECT Student.Age, COUNT( * )
 FROM Student
 GROUP BY Student.Age
 HAVING COUNT( * ) > 1
 </code></pre>
+<!-- markdownlint-restore -->
 
 </td><td>
 
@@ -646,12 +652,15 @@ query {
 </td></tr><tr><td>
 Grouping, counting, and ordering by count.<br/>
 
+<!-- markdownlint-capture -->
+<!-- markdownlint-disable no-space-in-emphasis -->
 <pre><code class="lang-sql">SELECT Student.Age, COUNT( * ) as myCount
 FROM Student
 GROUP BY Student.Age
 HAVING COUNT( * ) > 1
 ORDER BY COUNT( * ) DESC
 </code></pre>
+<!-- markdownlint-restore -->
 
 </td><td>
 
@@ -939,10 +948,13 @@ query {
 
 </td></tr><tr><td><code>UNION</code> of two queries.<br/>
 
+<!-- markdownlint-capture -->
+<!-- markdownlint-disable no-space-in-emphasis -->
 <pre><code class="lang-sql">SELECT * FROM Student
 UNION
 SELECT * FROM lastStudent
 </code></pre>
+<!-- markdownlint-restore -->
 
 </td><td>
 
@@ -964,10 +976,13 @@ query2.Union (query1)
 
 </td></tr><tr><td>Intersection of two queries.<br/>
 
+<!-- markdownlint-capture -->
+<!-- markdownlint-disable no-space-in-emphasis -->
 <pre><code class="lang-sql">SELECT * FROM Student
 INTERSECT
 SELECT * FROM LastStudent
 </code></pre>
+<!-- markdownlint-restore -->
 </td><td>
 
 <pre><code class="lang-fsharp">

docs/fsharp/language-reference/query-expressions.md

@@ -450,7 +450,7 @@ The following table describes how the punctuation symbols found in the state tra
 |------------|-----------------|
 |||Either method or state (the one before the bar or the one after it) can be called.|
 |?|The method or state that precedes the question mark is optional but if it is called it can only be called once.|
-|*|The method or state that precedes the * symbol is optional, and can be called more than once.|
+|\*|The method or state that precedes the \* symbol is optional, and can be called more than once.|
 
 ## Validation Context
 

docs/standard/data/xml/xmlschemavalidator-push-based-validation.md

@@ -336,7 +336,7 @@ Non-compliant type | Description | CLS-compliant alternative
 
 The .NET Framework Class Library or any other class library may include other types that aren't CLS-compliant; for example:
 
-* Boxed value types. The following C# example creates a class that has a public property of type `int`* named `Value`. Because an `int`* is a boxed value type, the compiler flags it as non-CLS-compliant.
+* Boxed value types. The following C# example creates a class that has a public property of type `int*` named `Value`. Because an `int*` is a boxed value type, the compiler flags it as non-CLS-compliant.
 
 ```csharp
 using System;