Use full docs links for IntelliSense (dotnet#8045)

Author: gewarren

xml/Microsoft.Extensions.Configuration/ConfigurationExtensions.xml

@@ -276,7 +276,7 @@
       <Docs>
         <param name="configuration">The <see cref="T:Microsoft.Extensions.Configuration.IConfiguration" /> to enumerate.</param>
         <param name="makePathsRelative">
-          <see langword="true" /> to trim the the current configuration's Path from the child keys returned; otherwise, <see langword="false" />.</param>
+          <see langword="true" /> to trim the current configuration's Path from the child keys returned; otherwise, <see langword="false" />.</param>
         <summary>Gets the enumeration of key-value pairs within the <see cref="T:Microsoft.Extensions.Configuration.IConfiguration" />.</summary>
         <returns>An enumeration of key-value pairs.</returns>
         <remarks>To be added.</remarks>

xml/Microsoft.Extensions.Configuration/ConfigurationManager.xml

@@ -183,7 +183,7 @@
       <Parameters />
       <Docs>
         <summary>Returns a <see cref="T:Microsoft.Extensions.Primitives.IChangeToken" /> that can be used to observe when this configuration is reloaded.</summary>
-        <returns>A token that can be used to observe the the configuration is reloaded.</returns>
+        <returns>A token that can be used to observe when the configuration is reloaded.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

xml/System.CodeDom/CodeNamespace.xml

@@ -49,10 +49,10 @@
   
  The <xref:System.CodeDom.CodeNamespace.Name%2A> property specifies the name of the namespace. The <xref:System.CodeDom.CodeNamespace.Imports%2A> property contains the namespace import directives for the namespace. The <xref:System.CodeDom.CodeNamespace.Types%2A> property contains the type declarations for the namespace. The <xref:System.CodeDom.CodeNamespace.Comments%2A> property contains the comments that apply at the namespace level.  
   
- In some languages, a namespace can function as a container for type declarations; all types in the same namespace are accessible without using fully-qualified type references, if the there is no conflict between type names.  
+ In some languages, a namespace can function as a container for type declarations; all types in the same namespace are accessible without using fully-qualified type references, if there is no conflict between type names.  
   
 > [!NOTE]
->  Use fully qualified type references to avoid potential ambiguity.  
+> Use fully qualified type references to avoid potential ambiguity.  
   
    
   

xml/System.Data.SqlClient/SqlError.xml

@@ -206,7 +206,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the text describing the error.</summary>
-        <value>The text describing the error. For more information on errors generated by SQL Server, see <see href="/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</value>
+        <value>The text describing the error. For more information on errors generated by SQL Server, see <see href="https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -320,7 +320,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the name of the stored procedure or remote procedure call (RPC) that generated the error.</summary>
-        <value>The name of the stored procedure or RPC. For more information on errors generated by SQL Server, see <see href="/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</value>
+        <value>The name of the stored procedure or RPC. For more information on errors generated by SQL Server, see <see href="https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

xml/System.Data.SqlClient/SqlException.xml

@@ -686,7 +686,7 @@ catch (Exception ex) {
         <ReturnType>System.Byte</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a numeric error code from SQL Server that represents an error, warning or "no data found" message. For more information about how to decode these values, see <see href="/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</summary>
+        <summary>Gets a numeric error code from SQL Server that represents an error, warning or "no data found" message. For more information about how to decode these values, see <see href="https://docs.microsoft.com/sql/relational-databases/errors-events/database-engine-events-and-errors">Database Engine Events and Errors</see>.</summary>
         <value>The number representing the error code.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

xml/System.Data/MissingSchemaAction.xml

@@ -118,7 +118,8 @@
       </ReturnValue>
       <MemberValue>4</MemberValue>
       <Docs>
-        <summary>Adds the necessary columns and primary key information to complete the schema. For more information about how primary key information is added to a <see cref="T:System.Data.DataTable" />, see <see cref="M:System.Data.IDataAdapter.FillSchema(System.Data.DataSet,System.Data.SchemaType)" />.To function properly with the .NET Framework Data Provider for OLE DB, <see langword="AddWithKey" /> requires that the native OLE DB provider obtains necessary primary key information by setting the DBPROP_UNIQUEROWS property, and then determines which columns are primary key columns by examining DBCOLUMN_KEYCOLUMN in the IColumnsRowset. As an alternative, the user may explicitly set the primary key constraints on each <see cref="T:System.Data.DataTable" />. This ensures that incoming records that match existing records are updated instead of appended. When using <see langword="AddWithKey" />, the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see <see href="/sql/t-sql/statements/set-fmtonly-transact-sql">SET FMTONLY (Transact-SQL)</see>.</summary>
+        <summary><para>Adds the necessary columns and primary key information to complete the schema. For more information about how primary key information is added to a <see cref="T:System.Data.DataTable" />, see <see cref="M:System.Data.IDataAdapter.FillSchema(System.Data.DataSet,System.Data.SchemaType)" />.</para>
+        <para>To function properly with the .NET Framework Data Provider for OLE DB, <see langword="AddWithKey" /> requires that the native OLE DB provider obtains necessary primary key information by setting the DBPROP_UNIQUEROWS property, and then determines which columns are primary key columns by examining DBCOLUMN_KEYCOLUMN in the IColumnsRowset. As an alternative, the user may explicitly set the primary key constraints on each <see cref="T:System.Data.DataTable" />. This ensures that incoming records that match existing records are updated instead of appended. When using <see langword="AddWithKey" />, the .NET Framework Data Provider for SQL Server appends a FOR BROWSE clause to the statement being executed. The user should be aware of potential side effects, such as interference with the use of SET FMTONLY ON statements. For more information, see <see href="https://docs.microsoft.com/sql/t-sql/statements/set-fmtonly-transact-sql">SET FMTONLY (Transact-SQL)</see>.</para></summary>
       </Docs>
     </Member>
     <Member MemberName="Error">

xml/System.Diagnostics.Eventing.Reader/EventRecord.xml

@@ -1031,7 +1031,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets the XML representation of the event. All of the event properties are represented in the event XML. The XML conforms to the <see href="/windows/win32/wes/eventschema-schema">event schema</see>.</summary>
+        <summary>Gets the XML representation of the event. All of the event properties are represented in the event XML. The XML conforms to the <see href="https://docs.microsoft.com/windows/win32/wes/eventschema-schema">event schema</see>.</summary>
         <returns>Returns a string that contains the XML representation of the event.</returns>
         <remarks>To be added.</remarks>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/bb671205(v=vs.90)">Technology Summary for Reading and Managing Event Logs</related>

xml/System.Diagnostics.SymbolStore/SymDocument.xml

@@ -64,8 +64,8 @@
         <Parameter Name="pDocument" Type="ISymUnmanagedDocument*" Index="0" FrameworkAlternate="netframework-1.1" />
       </Parameters>
       <Docs>
-        <param name="pDocument">A pointer to the <see href="/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> object.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Diagnostics.SymbolStore.SymDocument" /> class using the specified pointer to an unmanaged <see href="/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> object.</summary>
+        <param name="pDocument">A pointer to the <see href="https://docs.microsoft.com/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> object.</param>
+        <summary>Initializes a new instance of the <see cref="T:System.Diagnostics.SymbolStore.SymDocument" /> class using the specified pointer to an unmanaged <see href="https://docs.microsoft.com/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> object.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -448,8 +448,8 @@ Use the <xref:System.Diagnostics.SymbolStore.SymDocument.Finalize> method to rel
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets a pointer to the unmanaged <see href="/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> interface for this <see cref="T:System.Diagnostics.SymbolStore.SymDocument" /> instance.</summary>
-        <returns>A pointer to the unmanaged <see href="/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> interface for this <see cref="T:System.Diagnostics.SymbolStore.SymDocument" />.</returns>
+        <summary>Gets a pointer to the unmanaged <see href="https://docs.microsoft.com/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> interface for this <see cref="T:System.Diagnostics.SymbolStore.SymDocument" /> instance.</summary>
+        <returns>A pointer to the unmanaged <see href="https://docs.microsoft.com/dotnet/framework/unmanaged-api/diagnostics/isymunmanageddocument-interface">ISymUnmanagedDocument</see> interface for this <see cref="T:System.Diagnostics.SymbolStore.SymDocument" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[
 

xml/System.Diagnostics.SymbolStore/SymMethod.xml

@@ -62,7 +62,7 @@
         <Parameter Name="pMethod" Type="ISymUnmanagedMethod*" Index="0" FrameworkAlternate="netframework-1.1" />
       </Parameters>
       <Docs>
-        <param name="pMethod">A raw pointer to the unmanaged COM <see href="/dotnet/framework/unmanaged-api/diagnostics/isymunmanagedmethod-interface">ISymUnmanagedMethod</see> object.</param>
+        <param name="pMethod">A raw pointer to the unmanaged COM <see href="https://docs.microsoft.com/dotnet/framework/unmanaged-api/diagnostics/isymunmanagedmethod-interface">ISymUnmanagedMethod</see> object.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Diagnostics.SymbolStore.SymMethod" /> class from a raw pointer to an unmanaged interface.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[

xml/System.Diagnostics.Tracing/EventSource.xml

@@ -852,7 +852,7 @@ The following example shows an implementation of <xref:System.Diagnostics.Tracin
       </Parameters>
       <Docs>
         <param name="eventSourceType">The type of the event source.</param>
-        <param name="assemblyPathToIncludeInManifest">The path to the assembly file (.dll) to include in the <see href="/windows/win32/wes/eventmanifestschema-provider-eventstype-element">provider</see> element of the manifest.</param>
+        <param name="assemblyPathToIncludeInManifest">The path to the assembly file (.dll) to include in the <see href="https://docs.microsoft.com/windows/win32/wes/eventmanifestschema-provider-eventstype-element">provider</see> element of the manifest.</param>
         <summary>Returns a string of the XML manifest that is associated with the current event source.</summary>
         <returns>The XML data string.</returns>
         <remarks>
@@ -912,7 +912,7 @@ The following example shows an implementation of <xref:System.Diagnostics.Tracin
       </Parameters>
       <Docs>
         <param name="eventSourceType">The type of the event source.</param>
-        <param name="assemblyPathToIncludeInManifest">The path to the assembly file (.dll) file to include in the <see href="/windows/win32/wes/eventmanifestschema-provider-eventstype-element">provider</see> element of the manifest.</param>
+        <param name="assemblyPathToIncludeInManifest">The path to the assembly file (.dll) file to include in the <see href="https://docs.microsoft.com/windows/win32/wes/eventmanifestschema-provider-eventstype-element">provider</see> element of the manifest.</param>
         <param name="flags">A bitwise combination of the enumeration values that specify how the manifest is generated.</param>
         <summary>Returns a string of the XML manifest that is associated with the current event source.</summary>
         <returns>The XML data string or <see langword="null" />.</returns>