Upgrade links to https and fix msdn link captions (#3420)

* Upgrade go.microsoft.com links to https

Contributes to #1200

* Upgrade rfc-editor.org link to https

Contributes to #1200

* Upgrade go2.microsoft.com links to https

Contributes to #1200

* Fix msdn.microsoft.com link names to be https

The msdn.microsoft.com links have been changed to https, but the link
names have not been adjusted accordingly.

This change corrects that. With this change the link name matches the
href again.

Contributes to #1200

Author: Kissaki

xml/System.CodeDom.Compiler/CompilerParameters.xml

@@ -393,7 +393,7 @@
       </AssemblyInfo>
       <Attributes>
         <Attribute FrameworkAlternate="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;xamarinmac-3.0;netframework-4.8">
-          <AttributeName>System.Obsolete("CAS policy is obsolete and will be removed in a future release of the .NET Framework. Please see http://go2.microsoft.com/fwlink/?LinkId=131738 for more information.")</AttributeName>
+          <AttributeName>System.Obsolete("CAS policy is obsolete and will be removed in a future release of the .NET Framework. Please see https://go2.microsoft.com/fwlink/?LinkId=131738 for more information.")</AttributeName>
         </Attribute>
       </Attributes>
       <ReturnValue>

xml/System.CodeDom.Compiler/CompilerResults.xml

@@ -204,7 +204,7 @@
           <AttributeName>System.Obsolete</AttributeName>
         </Attribute>
         <Attribute FrameworkAlternate="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">
-          <AttributeName>System.Obsolete("CAS policy is obsolete and will be removed in a future release of the .NET Framework. Please see http://go2.microsoft.com/fwlink/?LinkId=131738 for more information.")</AttributeName>
+          <AttributeName>System.Obsolete("CAS policy is obsolete and will be removed in a future release of the .NET Framework. Please see https://go2.microsoft.com/fwlink/?LinkId=131738 for more information.")</AttributeName>
         </Attribute>
       </Attributes>
       <ReturnValue>

xml/System.ComponentModel/Win32Exception.xml

@@ -47,7 +47,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Win32 error codes are translated from their numeric representations into a system message when they are displayed. Use <xref:System.ComponentModel.Win32Exception.NativeErrorCode%2A> to access the numeric representation of the error code associated with this exception. For more information about the error codes, see "Win32 Error Codes" in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ Win32 error codes are translated from their numeric representations into a system message when they are displayed. Use <xref:System.ComponentModel.Win32Exception.NativeErrorCode%2A> to access the numeric representation of the error code associated with this exception. For more information about the error codes, see "Win32 Error Codes" in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   

xml/System.Diagnostics/EventInstance.xml

@@ -37,7 +37,7 @@
   
  Create the new event source during the installation of your application. This allows time for the operating system to refresh its list of registered event sources and their configurations. If the operating system has not refreshed its list of event sources, and you attempt to write an event with the new source, the write operation will fail. You can configure a new source using an <xref:System.Diagnostics.EventLogInstaller>, or using the <xref:System.Diagnostics.EventLog.CreateEventSource%2A> method. You must have administrative rights on the computer to create a new event source.  
   
- For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com).  
+ For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com).  
   
    
   
@@ -565,7 +565,7 @@ SVC_UPDATE.EXE
   
  Event categories are optional. If your application does not use categories, do not set the <xref:System.Diagnostics.EventInstance.CategoryId%2A> for the event log entry.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/). For details about defining event categories in resource files, see the "Event Categories" topic in the Platform SDK  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/). For details about defining event categories in resource files, see the "Event Categories" topic in the Platform SDK  
   
    
   
@@ -898,7 +898,7 @@ SVC_UPDATE.EXE
 ## Remarks  
  The <xref:System.Diagnostics.EventInstance.InstanceId%2A> property uniquely identifies an event entry for a configured event source. For events defined in message resource files, the <xref:System.Diagnostics.EventInstance.InstanceId%2A> corresponds to the resource identifier compiled from the message definition fields in the message text file. Your application can write localized event log entries by setting the <xref:System.Diagnostics.EventInstance.InstanceId%2A> to a resource identifier. The Event Viewer uses the <xref:System.Diagnostics.EventInstance.InstanceId%2A> resource identifier to find and display the corresponding string from the localized resource file based on current language settings. You must register the source with the corresponding resource file before you write events using resource identifiers.  
   
- For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/). For details about event log identifiers, see the "Event Identifiers" topic in the Platform SDK.  
+ For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/). For details about event log identifiers, see the "Event Identifiers" topic in the Platform SDK.  
   
    
   

xml/System.Diagnostics/EventLogEntry.xml

@@ -433,7 +433,7 @@
   
  If the application wrote the event entry using one of the <xref:System.Diagnostics.EventLog.WriteEntry%2A> methods, the <xref:System.Diagnostics.EventLogEntry.InstanceId%2A> property matches the optional `eventId` parameter. If the application wrote the event using <xref:System.Diagnostics.EventLog.WriteEvent%2A>, the <xref:System.Diagnostics.EventLogEntry.InstanceId%2A> property matches the resource identifier specified in the <xref:System.Diagnostics.EventInstance.InstanceId%2A> of the `instance` parameter. If the application wrote the event using the Windows API `ReportEvent`, the <xref:System.Diagnostics.EventLogEntry.InstanceId%2A> property matches the resource identifier specified in the `dwEventID` parameter.  
   
- For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/). For details about event log identifiers, see the "Event Identifiers" topic in the Platform SDK.  
+ For details about defining event messages and building event log resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/). For details about event log identifiers, see the "Event Identifiers" topic in the Platform SDK.  
   
    
   

xml/System.Diagnostics/EventLogInstaller.xml

@@ -117,7 +117,7 @@
   
  Event categories are optional; if your application does not use categories, do not set the <xref:System.Diagnostics.EventLogInstaller.CategoryCount%2A> and <xref:System.Diagnostics.EventLogInstaller.CategoryResourceFile%2A> properties.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -292,7 +292,7 @@ SVC_UPDATE.EXE
   
  Event categories are optional; if your application does not use categories, do not set the <xref:System.Diagnostics.EventLogInstaller.CategoryCount%2A> and <xref:System.Diagnostics.EventLogInstaller.CategoryResourceFile%2A> properties.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -645,7 +645,7 @@ SVC_UPDATE.EXE
   
  If the <xref:System.Diagnostics.EventLog.MachineName%2A> property is not the local computer identifier ("."), the .NET Framework assumes that the resource file is on a remote computer. If the <xref:System.Diagnostics.EventLogInstaller.MessageResourceFile%2A> property value contains a drive letter, the resource file is assumed to be on the \\\\<machinename\>\\<drive\>$ share (for example, \\\server\c$). If the value contains the string %systemroot%, the resource file is assumed to be on the \\\\<machinename\>\admin$ share (for example, \\\server\admin$).  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -845,7 +845,7 @@ TRIGGER.EXE
   
  If your application writes event message strings directly to the event log, or if your <xref:System.Diagnostics.EventLogInstaller.MessageResourceFile%2A> does not contain messages with parameter insertion placeholders, do not set the <xref:System.Diagnostics.EventLogInstaller.ParameterResourceFile%2A> property.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   

xml/System.Diagnostics/EventSourceCreationData.xml

@@ -275,7 +275,7 @@ SVC_UPDATE.EXE
   
  Event categories are optional; if your application does not use categories, do not set the <xref:System.Diagnostics.EventSourceCreationData.CategoryCount%2A> and <xref:System.Diagnostics.EventSourceCreationData.CategoryResourceFile%2A> properties.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -448,7 +448,7 @@ SVC_UPDATE.EXE
   
  Event categories are optional; if your application does not use categories, do not set the <xref:System.Diagnostics.EventSourceCreationData.CategoryCount%2A> and <xref:System.Diagnostics.EventSourceCreationData.CategoryResourceFile%2A> properties.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -742,7 +742,7 @@ SVC_UPDATE.EXE
   
  If your application writes event message strings directly, rather than using a resource identifier in a localized resource file, do not set the <xref:System.Diagnostics.EventSourceCreationData.MessageResourceFile%2A> property.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   
@@ -939,7 +939,7 @@ TRIGGER.EXE
   
  If your application writes event message strings directly to the event log, or if your <xref:System.Diagnostics.EventSourceCreationData.MessageResourceFile%2A> property does not contain messages with parameter insertion placeholders, do not set the <xref:System.Diagnostics.EventSourceCreationData.ParameterResourceFile%2A> property.  
   
- For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [http://msdn.microsoft.com](https://msdn.microsoft.com/).  
+ For details about defining event messages and building event resource files, see the "Message Compiler" topic in the Platform SDK documentation at [https://msdn.microsoft.com](https://msdn.microsoft.com/).  
   
    
   

xml/System.DirectoryServices.ActiveDirectory/ActiveDirectorySchemaClass.xml

@@ -396,8 +396,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the ldapDisplayName of the <see cref="T:System.DirectoryServices.ActiveDirectory.ActiveDirectorySchemaClass" /> object. For more information, see the topic [LDAP-Display-Name](https://msdn.microsoft.com/library/default.asp?url=/library/adschema/adschema/a_ldapdisplayname.asp) in the MSDN Library at [http://msdn.microsoft.com](https://msdn.microsoft.com/).</summary>
-        <value>A <see cref="T:System.String" /> that contains the ldapDisplayName of the <see cref="T:System.DirectoryServices.ActiveDirectory.ActiveDirectorySchemaClass" /> object. For more information, see the topic [LDAP-Display-Name](https://msdn.microsoft.com/library/default.asp?url=/library/adschema/adschema/a_ldapdisplayname.asp) in the MSDN Library at [http://msdn.microsoft.com](https://msdn.microsoft.com/).</value>
+        <summary>Gets the ldapDisplayName of the <see cref="T:System.DirectoryServices.ActiveDirectory.ActiveDirectorySchemaClass" /> object. For more information, see the topic [LDAP-Display-Name](https://msdn.microsoft.com/library/default.asp?url=/library/adschema/adschema/a_ldapdisplayname.asp) in the MSDN Library at [https://msdn.microsoft.com](https://msdn.microsoft.com/).</summary>
+        <value>A <see cref="T:System.String" /> that contains the ldapDisplayName of the <see cref="T:System.DirectoryServices.ActiveDirectory.ActiveDirectorySchemaClass" /> object. For more information, see the topic [LDAP-Display-Name](https://msdn.microsoft.com/library/default.asp?url=/library/adschema/adschema/a_ldapdisplayname.asp) in the MSDN Library at [https://msdn.microsoft.com](https://msdn.microsoft.com/).</value>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.DirectoryServices.ActiveDirectory.ActiveDirectorySchemaClass.Save" />
       </Docs>

xml/System.DirectoryServices/ActiveDirectoryRights.xml

@@ -157,7 +157,7 @@
       </ReturnValue>
       <MemberValue>256</MemberValue>
       <Docs>
-        <summary>A customized control access right. For a list of possible extended rights, see the topic "Extended Rights" in the MSDN Library at [http://msdn.microsoft.com](https://msdn.microsoft.com/). For more information about extended rights, see the topic "Control Access Rights" in the MSDN Library at [http://msdn.microsoft.com](https://msdn.microsoft.com/).</summary>
+        <summary>A customized control access right. For a list of possible extended rights, see the topic "Extended Rights" in the MSDN Library at [https://msdn.microsoft.com](https://msdn.microsoft.com/). For more information about extended rights, see the topic "Control Access Rights" in the MSDN Library at [https://msdn.microsoft.com](https://msdn.microsoft.com/).</summary>
       </Docs>
     </Member>
     <Member MemberName="GenericAll">
@@ -267,7 +267,7 @@
       </ReturnValue>
       <MemberValue>4</MemberValue>
       <Docs>
-        <summary>The right to list children of this object. For more information about this right, see the topic "Controlling Object Visibility" in the MSDN Library [http://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
+        <summary>The right to list children of this object. For more information about this right, see the topic "Controlling Object Visibility" in the MSDN Library [https://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
       </Docs>
     </Member>
     <Member MemberName="ListObject">
@@ -289,7 +289,7 @@
       </ReturnValue>
       <MemberValue>128</MemberValue>
       <Docs>
-        <summary>The right to list a particular object. For more information about this right, see the topic "Controlling Object Visibility" in the MSDN Library at [http://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
+        <summary>The right to list a particular object. For more information about this right, see the topic "Controlling Object Visibility" in the MSDN Library at [https://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
       </Docs>
     </Member>
     <Member MemberName="ReadControl">

xml/System.DirectoryServices/AuthenticationTypes.xml

@@ -136,7 +136,7 @@ LDAP://CN=jsmith,DC=fabrikam,DC=Com
       </ReturnValue>
       <MemberValue>32</MemberValue>
       <Docs>
-        <summary>Specifies that ADSI will not attempt to query the Active Directory Domain Services objectClass property.  Therefore, only the base interfaces that are supported by all ADSI objects will be exposed.  Other interfaces that the object supports will not be available. A user can use this option to boost the performance in a series of object manipulations that involve only methods of the base interfaces. However, ADSI does not verify if any of the request objects actually exist on the server. For more information, see the topic "Fast Binding Option for Batch Write/Modify Operations" in the MSDN Library at [http://msdn.microsoft.com/library](https://msdn.microsoft.com/library).  For more information about the objectClass property, see the "Object-Class" topic in the MSDN Library at [http://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
+        <summary>Specifies that ADSI will not attempt to query the Active Directory Domain Services objectClass property.  Therefore, only the base interfaces that are supported by all ADSI objects will be exposed.  Other interfaces that the object supports will not be available. A user can use this option to boost the performance in a series of object manipulations that involve only methods of the base interfaces. However, ADSI does not verify if any of the request objects actually exist on the server. For more information, see the topic "Fast Binding Option for Batch Write/Modify Operations" in the MSDN Library at [https://msdn.microsoft.com/library](https://msdn.microsoft.com/library).  For more information about the objectClass property, see the "Object-Class" topic in the MSDN Library at [https://msdn.microsoft.com/library](https://msdn.microsoft.com/library).</summary>
       </Docs>
     </Member>
     <Member MemberName="None">