markdig fixes (#2702)

Author: mairaw

xml/System.Configuration/RsaProtectedConfigurationProvider.xml

@@ -31,7 +31,7 @@
  The <xref:System.Configuration.RsaProtectedConfigurationProvider> object uses the cryptography functions provided by <xref:System.Security.Cryptography.RSA> class to encrypt and decrypt configuration sections.  
   
 > [!NOTE]
->  Before ASP.NET can decrypt encrypted information in your configuration file, the identity of your ASP.NET application must have read access to the encryption key used to encrypt and decrypt the configuration data. For more information, see [Walkthrough: Encrypting Configuration Information Using Protected Configuration](https://docs.microsoft.com/previous-versions/dtkwfdky(v=vs.140).
+>  Before ASP.NET can decrypt encrypted information in your configuration file, the identity of your ASP.NET application must have read access to the encryption key used to encrypt and decrypt the configuration data. For more information, see [Walkthrough: Encrypting Configuration Information Using Protected Configuration](https://docs.microsoft.com/previous-versions/dtkwfdky(v=vs.140)).
 
 ## Examples  
 

xml/System.DirectoryServices.Protocols/DirectoryConnection.xml

@@ -119,7 +119,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For example, "http://fabrikam.com/platforms/adssoap.dll" represents a DSML server and "dc-01.fabrikam.com" represents an LDAP server.  
+ For example, `"http://fabrikam.com/platforms/adssoap.dll"` represents a DSML server and `"dc-01.fabrikam.com"` represents an LDAP server.  
   
  ]]></format>
         </remarks>

xml/System.IO.Packaging/PackUriHelper.xml

@@ -167,16 +167,16 @@
   
 |`packageUri`|`partUri`|`fragment`|Returned pack URI|  
 |------------------|---------------|----------------|-----------------------|  
-|http://www.proseware.com/mypackage.pkg|/page1.xaml|#intro|pack://http:,,www.proseware.com,mypackage.pkg/page1.xaml#intro|  
-|http://www.proseware.com/mypackage.pkg|/page2.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
-|http://www.proseware.com/mypackage.pkg|/a/page4.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
-|http://www.proseware.com/mypackage.pkg|/%41/%61.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
-|http://www.proseware.com/mypackage.pkg|/%25XY.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
-|http://www.proseware.com/mypackage.pkg|/a/page5.xaml|#summary|pack://http:,,www.proseware.com,mypackage.pkg/a/page5.xaml#summary|  
-|http://www.proseware.com/packages.aspx?pkg04|/page1.xaml|#intro|pack://http:,,www.proseware.com,packages.aspx%3fpkg04/page1.xaml#intro|  
-|http://www.proseware.com/mypackage.pkg|**null**|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
-|ftp://ftp.proseware.com/packages/mypackage1.abc|/a/mydoc.xaml|**null**|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/mydoc.xaml|  
-|file:///d:/packages/mypackage2.pkg|/a/bar.xaml|#xref|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml#xref|  
+|`http://www.proseware.com/mypackage.pkg`|/page1.xaml|#intro|pack://http:,,www.proseware.com,mypackage.pkg/page1.xaml#intro|  
+|`http://www.proseware.com/mypackage.pkg`|/page2.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/a/page4.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/%41/%61.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
+|`http://www.proseware.com/mypackage.pkg`|/%25XY.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
+|`http://www.proseware.com/mypackage.pkg`|/a/page5.xaml|#summary|pack://http:,,www.proseware.com,mypackage.pkg/a/page5.xaml#summary|  
+|`http://www.proseware.com/packages.aspx?pkg04`|/page1.xaml|#intro|pack://http:,,www.proseware.com,packages.aspx%3fpkg04/page1.xaml#intro|  
+|`http://www.proseware.com/mypackage.pkg`|**null**|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
+|`ftp://ftp.proseware.com/packages/mypackage1.abc`|/a/mydoc.xaml|**null**|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/mydoc.xaml|  
+|`file:///d:/packages/mypackage2.pkg`|/a/bar.xaml|#xref|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml#xref|  
   
  Composing a pack URI is a multi-step process.  For example, one step in forming a pack URI is to replace the forward slash (/) characters of the `packageUri` with commas (,).  
   
@@ -229,7 +229,7 @@
   
 |`packageUri`|Returned pack URI|  
 |------------------|-----------------------|  
-|http://www.proseware.com/mypackage.pkg|pack://http:,,www.proseware.com,mypackage.pkg|  
+|`http://www.proseware.com/mypackage.pkg`|pack://http:,,www.proseware.com,mypackage.pkg|  
 |ftp://ftp.proseware.com/packages/mypackage1.abc|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc|  
 |file:///d:/packages/mypackage2.pkg|pack://file:,,,d:,packages,mypackage2.pkg|  
   
@@ -300,11 +300,11 @@
   
 |`packageUri`|`partUri`|Returned pack URI|  
 |------------------|---------------|-----------------------|  
-|http://www.proseware.com/mypackage.pkg|/page2.xaml|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
-|http://www.proseware.com/mypackage.pkg|/a/page4.xaml|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
-|http://www.proseware.com/mypackage.pkg|/%41/%61.xml|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
-|http://www.proseware.com/mypackage.pkg|/%25XY.xml|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
-|http://www.proseware.com/mypackage.pkg|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
+|`http://www.proseware.com/mypackage.pkg`|/page2.xaml|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/a/page4.xaml|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/%41/%61.xml|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
+|`http://www.proseware.com/mypackage.pkg`|/%25XY.xml|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
+|`http://www.proseware.com/mypackage.pkg`|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
 |ftp://ftp.proseware.com/packages/mypackage1.abc|/a/mydoc.xaml|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/mydoc.xaml|  
 |file:///d:/packages/mypackage2.pkg|/a/bar.xaml|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml|  
   
@@ -378,16 +378,16 @@
   
 |`packageUri`|`partUri`|`fragment`|Returned pack URI|  
 |------------------|---------------|----------------|-----------------------|  
-|http://www.proseware.com/mypackage.pkg|/page1.xaml|#intro|pack://http:,,www.proseware.com,mypackage.pkg/page1.xaml#intro|  
-|http://www.proseware.com/mypackage.pkg|/page2.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
-|http://www.proseware.com/mypackage.pkg|/a/page4.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
-|http://www.proseware.com/mypackage.pkg|/%41/%61.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
-|http://www.proseware.com/mypackage.pkg|/%25XY.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
-|http://www.proseware.com/mypackage.pkg|/a/page5.xaml|#summary|pack://http:,,www.proseware.com,mypackage.pkg/a/page5.xaml#summary|  
-|http://www.proseware.com/packages.aspx?pkg04|/page1.xaml|#intro|pack://http:,,www.proseware.com,packages.aspx%3fpkg04/page1.xaml#intro|  
-|http://www.proseware.com/mypackage.pkg|**null**|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
-|ftp://ftp.proseware.com/packages/mypackage1.abc|/a/mydoc.xaml|**null**|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/mydoc.xaml|  
-|file:///d:/packages/mypackage2.pkg|/a/bar.xaml|#xref|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml#xref|  
+|`http://www.proseware.com/mypackage.pkg`|/page1.xaml|#intro|pack://http:,,www.proseware.com,mypackage.pkg/page1.xaml#intro|  
+|`http://www.proseware.com/mypackage.pkg`|/page2.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/page2.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/a/page4.xaml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/a/page4.xaml|  
+|`http://www.proseware.com/mypackage.pkg`|/%41/%61.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/A/a.xml|  
+|`http://www.proseware.com/mypackage.pkg`|/%25XY.xml|**null**|pack://http:,,www.proseware.com,mypackage.pkg/%25XY.xml|  
+|`http://www.proseware.com/mypackage.pkg`|/a/page5.xaml|#summary|pack://http:,,www.proseware.com,mypackage.pkg/a/page5.xaml#summary|  
+|`http://www.proseware.com/packages.aspx?pkg04`|/page1.xaml|#intro|pack://http:,,www.proseware.com,packages.aspx%3fpkg04/page1.xaml#intro|  
+|`http://www.proseware.com/mypackage.pkg`|**null**|**null**|pack://http:,,www.proseware.com,mypackage.pkg|  
+|`ftp://ftp.proseware.com/packages/mypackage1.abc`|/a/mydoc.xaml|**null**|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/mydoc.xaml|  
+|`file:///d:/packages/mypackage2.pkg`|/a/bar.xaml|#xref|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml#xref|  
   
  Composing a pack URI is a multi-step process.  For example, one step in forming a pack URI is to replace the forward slash (/) characters of the `packageUri` with commas (,).  
   
@@ -570,11 +570,11 @@
   
 |`packUri`|Returned Package URI|  
 |---------------|--------------------------|  
-|pack://http:,,www.proseware.com,mypackage.xyz/a/mydoc.xaml|http://www.proseware.com/mypackage.xyz|  
-|pack://http:,,www.proseware.com,packages.aspx%3fmypackage/a/bar.xaml|http://www.proseware.com/packages.aspx?mypackage|  
-|pack://http:,,www.proseware.com,mypackage.pkg|http://www.proseware.com/mypackage.pkg|  
-|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/picture.jpg|ftp://ftp.proseware.com/packages/mypackage1.abc|  
-|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml|file:///d:/packages/mypackage2.pkg|  
+|pack://http:,,www.proseware.com,mypackage.xyz/a/mydoc.xaml|`http://www.proseware.com/mypackage.xyz`|  
+|pack://http:,,www.proseware.com,packages.aspx%3fmypackage/a/bar.xaml|`http://www.proseware.com/packages.aspx?mypackage`|  
+|pack://http:,,www.proseware.com,mypackage.pkg|`http://www.proseware.com/mypackage.pkg`|  
+|pack://ftp:,,ftp.proseware.com,packages,mypackage1.abc/a/picture.jpg|`ftp://ftp.proseware.com/packages/mypackage1.abc`|  
+|pack://file:,,,d:,packages,mypackage2.pkg/a/bar.xaml|`file:///d:/packages/mypackage2.pkg`|  
   
  ]]></format>
         </remarks>

xml/System.IO.Packaging/PackagePart.xml

@@ -432,7 +432,7 @@
   
  If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.Internal>, `targetUri` must be a relative URI that is formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  The internal relative URI can be either an absolute path that starts with a forward slash ("/") character such as "/page1.xaml" or "/images/picture4.jpg", or a relative path such as "../imagespicture1.jpg" that resolves against the package root ("/") as the base URI.  
   
- If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  "https://www.microsoft.com/page2.xml" is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
+ If `targetMode` is specified as <xref:System.IO.Packaging.TargetMode.External>, `targetUri` can be either an absolute or relative URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification. `"https://www.microsoft.com/page2.xml"` is an example of an absolute URI that references an external target resource "page2.xml".  "images/picture1.jpg" is an example of a relative URI that also references an external target resource "1.jpg" but which resolves against the URI of the package itself.  
   
  `relationshipType` must be a [!INCLUDE[TLA2#tla_uri](~/includes/tla2sharptla-uri-md.md)] that is formed according to the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.  
   

xml/System.IO.Packaging/PackageRelationship.xml

@@ -176,17 +176,17 @@
 ## Remarks  
  The <xref:System.IO.Packaging.PackageRelationship.RelationshipType%2A> is specified in the call to the **Package**.<xref:System.IO.Packaging.Package.CreateRelationship%2A> or **PackagePart**.<xref:System.IO.Packaging.PackagePart.CreateRelationship%2A> method that created the relationship.  After the relationship is created, the <xref:System.IO.Packaging.PackageRelationship.RelationshipType%2A> cannot be changed.  
   
- <xref:System.IO.Packaging.PackageRelationship.RelationshipType%2A> is defined in a URI-like syntax and identifies the role of the relationship. For example, "http://schemas.microsoft.com/xps/2005/06/required-resource" identifies the relationship to a target part that is a "required-resource."  
+ <xref:System.IO.Packaging.PackageRelationship.RelationshipType%2A> is defined in a URI-like syntax and identifies the role of the relationship. For example, `"http://schemas.microsoft.com/xps/2005/06/required-resource"` identifies the relationship to a target part that is a "required-resource."  
   
  **Package-Wide Relationship Types**  
   
 |Description|Relationship Type|  
 |-----------------|-----------------------|  
-|Core Properties|http://schemas.microsoft.com/package/2006/relationships/metadata/core-properties|  
-|Digital Signature|http://schemas.microsoft.com/package/2006/relationships/digital-signature/signature|  
-|Digital Signature Certificate|http://schemas.microsoft.com/package/2006/relationships/digital-signature/certificate|  
-|Digital Signature Origin|http://schemas.microsoft.com/package/2006/relationships/digital-signature/origin|  
-|Thumbnail|http://schemas.microsoft.com/package/2006/relationships/metadata/thumbnail|  
+|Core Properties|`http://schemas.microsoft.com/package/2006/relationships/metadata/core-properties`|  
+|Digital Signature|`http://schemas.microsoft.com/package/2006/relationships/digital-signature/signature`|  
+|Digital Signature Certificate|`http://schemas.microsoft.com/package/2006/relationships/digital-signature/certificate`|  
+|Digital Signature Origin|`http://schemas.microsoft.com/package/2006/relationships/digital-signature/origin`|  
+|Thumbnail|`http://schemas.microsoft.com/package/2006/relationships/metadata/thumbnail`|  
   
  For more information about package relationship types see Chapter 3 and Appendix I of the *Open Packaging Conventions* specification available for download at <https://go.microsoft.com/fwlink/?LinkID=71255>.  
   

xml/System.IdentityModel.Protocols.WSTrust/RequestClaimCollection.xml

@@ -48,7 +48,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- After initialization, the <xref:System.IdentityModel.Protocols.WSTrust.RequestClaimCollection> is empty and the <xref:System.IdentityModel.Protocols.WSTrust.RequestClaimCollection.Dialect%2A> property is set to "http://schemas.xmlsoap.org/ws/2005/05/identity".  
+ After initialization, the <xref:System.IdentityModel.Protocols.WSTrust.RequestClaimCollection> is empty and the <xref:System.IdentityModel.Protocols.WSTrust.RequestClaimCollection.Dialect%2A> property is set to "<http://schemas.xmlsoap.org/ws/2005/05/identity>".  
   
  ]]></format>
         </remarks>

xml/System.IdentityModel.Tokens/SessionSecurityToken.xml

@@ -888,7 +888,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IdentityModel.Tokens.SessionSecurityTokenHandler> base class supports WS-Secure Conversation Feb2005 and WS-Secure Conversation 1.3. The URIs for these versions of WS-Secure Conversation are "http://schemas.xmlsoap.org/ws/2005/02/sc" and "http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" respectively.  
+ The <xref:System.IdentityModel.Tokens.SessionSecurityTokenHandler> base class supports WS-Secure Conversation Feb2005 and WS-Secure Conversation 1.3. The URIs for these versions of WS-Secure Conversation are "<http://schemas.xmlsoap.org/ws/2005/02/sc>" and "<http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512>", respectively.  
   
  ]]></format>
         </remarks>

xml/System.IdentityModel.Tokens/SessionSecurityTokenHandler.xml

@@ -313,7 +313,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the namespace for the cookie element.</summary>
-        <value>The namespace for the cookie element. The default namespace is "http://schemas.microsoft.com/ws/2006/05/security".</value>
+        <value>The namespace for the cookie element. The default namespace is <c>"http://schemas.microsoft.com/ws/2006/05/security"</c>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

xml/System.Net.Configuration/ProxyElement+BypassOnLocalValues.xml

@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Local resources include the local server (http://localhost, http://loopback, or http://127.0.0.1) and a URI without a period (http://webserver).  
+ Local resources include the local server (`http://localhost`, `http://loopback`, or `http://127.0.0.1`) and a URI without a period (`http://webserver`).  
   
  ]]></format>
     </remarks>

xml/System.Net.Configuration/ProxyElement+UseSystemDefaultValues.xml

@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Local resources include the local server (http://localhost, http://loopback, or http://127.0.0.1) and a URI without a period (http://webserver).  
+ Local resources include the local server (`http://localhost`, `http://loopback`, or `http://127.0.0.1`) and a URI without a period (`http://webserver`).  
   
  ]]></format>
     </remarks>