markdig fixes - Part 8 (#2565)

* markdig fixes - bare URLs

* feedback

Author: mairaw

xml/System.IO.IsolatedStorage/INormalizeForIsolatedStorage.xml

@@ -39,7 +39,7 @@
  ]]></format>
     </remarks>
     <block subset="none" type="overrides">
-      <para>Implement this interface when you are implementing custom evidence and need to determine if a store already exists. Serialized objects should not be used for comparisons in some instances, such as that of case sensitive strings. For example, www.MSN.com is equal to WWW.msn.com and will return a <see langword="true" /> when compared. To create an <see cref="T:System.IO.IsolatedStorage.INormalizeForIsolatedStorage" /> object, you need to implement the <see cref="M:System.IO.IsolatedStorage.INormalizeForIsolatedStorage.Normalize" /> method.</para>
+      <para>Implement this interface when you are implementing custom evidence and need to determine if a store already exists. Serialized objects should not be used for comparisons in some instances, such as that of case sensitive strings. For example, `www.MSN.com` is equal to `WWW.msn.com` and will return a <see langword="true" /> when compared. To create an <see cref="T:System.IO.IsolatedStorage.INormalizeForIsolatedStorage" /> object, you need to implement the <see cref="M:System.IO.IsolatedStorage.INormalizeForIsolatedStorage.Normalize" /> method.</para>
     </block>
     <block subset="none" type="usage">
       <para>Call the methods of this interface to normalize the instance before making comparisons between an assembly's evidence and currently existing isolated stores.</para>

xml/System.Net.NetworkInformation/IPStatus.xml

@@ -342,7 +342,7 @@
       </ReturnValue>
       <MemberValue>11004</MemberValue>
       <Docs>
-        <summary>The ICMP echo request failed because the destination computer that is specified in an ICMP echo message is not reachable, because it does not support the packet's protocol. This value applies only to IPv4. This value is described in IETF RFC 1812 as Communication Administratively Prohibited.</summary>
+        <summary>The ICMP echo request failed because the destination computer that is specified in an ICMP echo message is not reachable, because it does not support the packet's protocol. This value applies only to IPv4. This value is described in <see href="https://tools.ietf.org/html/rfc1812">IETF RFC 1812</see> as Communication Administratively Prohibited.</summary>
       </Docs>
     </Member>
     <Member MemberName="DestinationScopeMismatch">
@@ -771,7 +771,7 @@
       </ReturnValue>
       <MemberValue>11014</MemberValue>
       <Docs>
-        <summary>The ICMP echo request failed because the packet was divided into fragments for transmission and all of the fragments were not received within the time allotted for reassembly. RFC 2460 (available at www.ietf.org) specifies 60 seconds as the time limit within which all packet fragments must be received.</summary>
+        <summary>The ICMP echo request failed because the packet was divided into fragments for transmission and all of the fragments were not received within the time allotted for reassembly. <see href="https://tools.ietf.org/html/rfc2460">RFC 2460</see> specifies 60 seconds as the time limit within which all packet fragments must be received.</summary>
       </Docs>
     </Member>
     <Member MemberName="Unknown">

xml/System.Net/IPHostEntry.xml

@@ -40,7 +40,7 @@
    
   
 ## Examples  
- The following example queries the DNS database for information on the host www.contoso.com and returns the information in an <xref:System.Net.IPHostEntry> instance.  
+ The following example queries the DNS database for information on the host `www.contoso.com` and returns the information in an <xref:System.Net.IPHostEntry> instance.  
   
  [!code-cpp[Classic Dns Example#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Classic Dns Example/CPP/source.cpp#1)]
  [!code-csharp[Classic Dns Example#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Classic Dns Example/CS/source.cs#1)]

xml/System.Net/ServicePoint.xml

@@ -51,7 +51,7 @@
    
   
 ## Examples  
- The following code example creates a <xref:System.Net.ServicePoint> object that connects to the URI www.contoso.com.  
+ The following code example creates a <xref:System.Net.ServicePoint> object that connects to the URI `www.contoso.com`.  
   
  [!code-cpp[System.Net.ServicePoint#1](~/samples/snippets/cpp/VS_Snippets_Remoting/System.Net.ServicePoint/CPP/servicepoint.cpp#1)]
  [!code-csharp[System.Net.ServicePoint#1](~/samples/snippets/csharp/VS_Snippets_Remoting/System.Net.ServicePoint/CS/servicepoint.cs#1)]

xml/System.Net/ServicePointManager.xml

@@ -43,7 +43,7 @@
    
   
 ## Examples  
- The following code example creates a <xref:System.Net.ServicePoint> object for connections to the URI www.contoso.com.  
+ The following code example creates a <xref:System.Net.ServicePoint> object for connections to the URI `www.contoso.com`.  
   
  [!code-cpp[Classic ServicePoint Example#1](~/samples/snippets/cpp/VS_Snippets_Remoting/Classic ServicePoint Example/CPP/source.cpp#1)]
  [!code-csharp[Classic ServicePoint Example#1](~/samples/snippets/csharp/VS_Snippets_Remoting/Classic ServicePoint Example/CS/source.cs#1)]
@@ -996,7 +996,7 @@ For versions of the .NET Framework through the .NET Framework 4.6.2, no default
 ## Remarks  
 An application can set the <xref:System.Net.ServicePointManager.ServerCertificateValidationCallback%2A> property to a method to use for custom validation by the client of the server certificate. When doing custom validation, the `sender` parameter passed to the <xref:System.Net.Security.RemoteCertificateValidationCallback> can be a host string name or an object derived from <xref:System.Net.WebRequest> (<xref:System.Net.HttpWebRequest>, for example) depending on the <xref:System.Net.ServicePointManager.CertificatePolicy%2A> property.  
   
-When custom validation is not used, the certificate name is compared with the host name used to create the request. For example, if <xref:System.Net.WebRequest.Create%28System.String%29> was passed a parameter of "https://www.contoso.com/default.html", the default behavior is for the client to check the certificate against www.contoso.com.  
+When custom validation is not used, the certificate name is compared with the host name used to create the request. For example, if <xref:System.Net.WebRequest.Create%28System.String%29> was passed a parameter of `"https://www.contoso.com/default.html"`, the default behavior is for the client to check the certificate against `www.contoso.com`.  
 
 Despite being a multicast delegate, only the value returned from the last-executed event handler is considered authoritative. 
 In other words, you can attach multiple delegates, and they all get a callback from <xref:System.Net.ServicePointManager.ServerCertificateValidationCallback%2A>. 

xml/System.Security.Cryptography.Xml/RSAKeyValue.xml

@@ -33,7 +33,7 @@
   
  If a key is not explicitly supplied to the constructor, a new <xref:System.Security.Cryptography.RSA> key pair is randomly generated.  
   
- For more information about the `<RSAKeyValue>` element, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about the `<RSAKeyValue>` element, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
    
   
@@ -209,7 +209,7 @@ Based upon [The RSAKeyValue Element](https://www.w3.org/TR/2002/REC-xmldsig-core
 ## Remarks  
  The <xref:System.Security.Cryptography.Xml.RSAKeyValue.Key%2A> property represents the public key to add to an XML digital signature using the `<Modulus>` subelement and the `<Exponent>` subelement of the `<RSAKeyValue>` element.  
   
- For more information about XML digital signatures, see the W3C specification at www.w3.org/TR/xmldsig-core/.
+ For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).
 
           ]]></format>
         </remarks>

xml/System.Security.Cryptography.Xml/Reference.xml

@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.Xml.Reference> object represents the <`reference`> element of an XML digital signature defined by the XML digital signature specification.  
+ The <xref:System.Security.Cryptography.Xml.Reference> object represents the `<reference>` element of an XML digital signature defined by the XML digital signature specification.  
   
  Use the <xref:System.Security.Cryptography.Xml.Reference> object to specify the following information:  
   
@@ -41,7 +41,7 @@
   
 -   A unique identifier used to reference the current `<reference>` element.  This value is optional.  
   
- For more information about the <`reference`> element, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about the `<reference>` element, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
    
   
@@ -223,7 +223,7 @@
   
  Transforms are applied in the order in which they were added. If no transforms are specified, the minimum required transforms are added automatically.  
   
- For more information about XML digital signatures, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
    
   
@@ -275,11 +275,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.Xml.Reference.DigestMethod%2A> property uses a URI string to represent the <`DigestMethod`> element of an XML digital signature.  
+ The <xref:System.Security.Cryptography.Xml.Reference.DigestMethod%2A> property uses a URI string to represent the `<DigestMethod>` element of an XML digital signature.  
   
  The digest method is the algorithm used to hash the <xref:System.Security.Cryptography.Xml.Reference>. The default algorithm is <xref:System.Security.Cryptography.SHA1>.  
   
- For more information about XML digital signatures, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
  ]]></format>
         </remarks>
@@ -315,13 +315,13 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.Xml.Reference.DigestValue%2A> property uses an array of bytes to represent the <`DigestValue`> element of an XML digital signature.  
+ The <xref:System.Security.Cryptography.Xml.Reference.DigestValue%2A> property uses an array of bytes to represent the `<DigestValue>` element of an XML digital signature.  
   
  The <xref:System.Security.Cryptography.Xml.Reference.DigestValue%2A> property contains the Base 64 encoded value of the digest of the object described by the <xref:System.Security.Cryptography.Xml.Reference.Uri%2A> property.  
   
  The <xref:System.Security.Cryptography.Xml.Reference.DigestValue%2A> property is automatically populated with the appropriate value whenever you make a call to <xref:System.Security.Cryptography.Pkcs.SignedCms.ComputeSignature%2A>.  
   
- For more information about XML digital signatures, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
  ]]></format>
         </remarks>
@@ -471,11 +471,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.Xml.Reference.TransformChain%2A> property represents the <`Transform`> element and associated subelements of an XML digital signature.  
+ The <xref:System.Security.Cryptography.Xml.Reference.TransformChain%2A> property represents the `<Transform>` element and associated subelements of an XML digital signature.  
   
  The transform chain is an ordered list of transforms. The output of these transforms constitutes the input to the hash algorithm specified in the <xref:System.Security.Cryptography.Xml.Reference.DigestMethod%2A> property.  
   
- For more information about XML digital signatures, see the W3C specification at www.w3.org/TR/xmldsig-core/.  
+ For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/).  
   
  ]]></format>
         </remarks>
@@ -540,7 +540,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.Xml.Reference.Uri%2A> property uses a string Uniform Resource Identifier (URI) to represent the <`URI`> element of an XML digital signature.  
+ The <xref:System.Security.Cryptography.Xml.Reference.Uri%2A> property uses a string Uniform Resource Identifier (URI) to represent the `<URI>` element of an XML digital signature.  
   
  Use the <xref:System.Security.Cryptography.Xml.Reference.Uri%2A> property to specify the location of a document to sign, and to specify which element of the current XML document to sign or to indicate that the entire document should be signed.  
   

xml/System.Security.Cryptography.Xml/XmlDsigBase64Transform.xml

@@ -31,7 +31,7 @@
   
  The Uniform Resource Identifier (URI) that describes the <xref:System.Security.Cryptography.Xml.XmlDsigBase64Transform> object is defined by the <xref:System.Security.Cryptography.Xml.SignedXml.XmlDsigBase64TransformUrl> field.  
   
- For more information about the `Base64` decoding transform, see Section 6.6.2 of the XMLDSIG specification, which is available from the W3C at www.w3.org/TR/xmldsig-core/.  
+ For more information about the `Base64` decoding transform, see Section 6.6.2 of the W3C [XMLDSIG specification](https://www.w3.org/TR/xmldsig-core/).  
   
    
   

xml/System.Security.Cryptography.Xml/XmlDsigC14NTransform.xml

@@ -37,7 +37,7 @@
   
  You would only need to create a new instance of a canonicalization transform class for manually hashing an XML document or for using your own canonicalization algorithm.  
   
- For more information about the C14N transform, see Sections 6.5 and 6.6.1 of the XMLDSIG specification, which is available from the World Wide Web Consortium (W3C) at www.w3.org/TR/xmldsig-core/. The canonicalization algorithm is defined in the W3C Canonical XML specification, which is available at www.w3.org/TR/xml-c14n.  
+ For more information about the C14N transform, see Sections 6.5 and 6.6.1 of the W3C [XMLDSIG specification](https://www.w3.org/TR/xmldsig-core/). The canonicalization algorithm is defined in the W3C [Canonical XML specification](https://www.w3.org/TR/xml-c14n).  
   
    
   

xml/System.Security.Cryptography.Xml/XmlDsigC14NWithCommentsTransform.xml

@@ -37,12 +37,12 @@
   
  The URI that describes the <xref:System.Security.Cryptography.Xml.XmlDsigC14NWithCommentsTransform> class is defined by the <xref:System.Security.Cryptography.Xml.SignedXml.XmlDsigC14NWithCommentsTransformUrl> field and the <xref:System.Security.Cryptography.Xml.SignedXml.XmlDsigCanonicalizationWithCommentsUrl> field.  
   
- For more information about the C14N with comments transform, see Sections 6.5 and 6.6.1 of the XMLDSIG specification, which is available from the World Wide Web Consortium (W3C) at www.w3.org/TR/xmldsig-core/. The canonicalization algorithm is defined in the W3C Canonical XML specification, which is available at www.w3.org/TR/xml-c14n.  
+ For more information about the C14N with comments transform, see Sections 6.5 and 6.6.1 of the W3C [XMLDSIG specification](https://www.w3.org/TR/xmldsig-core/). The canonicalization algorithm is defined in the W3C [Canonical XML specification](https://www.w3.org/TR/xml-c14n).  
   
    
   
 ## Examples  
- This section contains two code examples. The first example demonstrates how to sign an XML file using a detached signature. This example creates a signature of www.microsoft.com in an XML file and then verifies the file. The second example demonstrates how to sign an XML file using an envelope signature.  This example creates a signature of an XML file and then saves the signature in new XML file.  
+ This section contains two code examples. The first example demonstrates how to sign an XML file using a detached signature. This example creates a signature of `www.microsoft.com` in an XML file and then verifies the file. The second example demonstrates how to sign an XML file using an envelope signature.  This example creates a signature of an XML file and then saves the signature in new XML file.  
   
  **Example #1**  
   
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- This section contains two code examples. The first example demonstrates how to sign an XML file using a detached signature. This example creates a signature of www.microsoft.com in an XML file and then verifies the file. The second example demonstrates how to sign an XML file using an envelope signature.  This example creates a signature of an XML file and then saves the signature in new XML file.  
+ This section contains two code examples. The first example demonstrates how to sign an XML file using a detached signature. This example creates a signature of `www.microsoft.com` in an XML file and then verifies the file. The second example demonstrates how to sign an XML file using an envelope signature.  This example creates a signature of an XML file and then saves the signature in new XML file.  
   
  **Example #1**