Correct occurences of [[...]]

xml/System.Data/IDbDataAdapter.xml

@@ -32,7 +32,7 @@
       <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- The <xref:System.Data.IDbDataAdapter> interface inherits from the <xref:System.Data.IDataAdapter> interface and allows an object to create a DataAdapter designed for use with a relational database. The <xref:System.Data.IDbDataAdapter> interface and, optionally, the utility class, <xref:System.Data.Common.DbDataAdapter>, allow an inheriting class to implement a DataAdapter class, which represents the bridge between a data source and a <xref:System.Data.DataSet>. For more information about DataAdapter classes, see [Populating a DataSet from a DataAdapter](~/docs/framework/data/adonet/populating-a-dataset-from-a-dataadapter.md). For more information about implementing .NET Framework data providers, see [&#91;\<topic://cpconimplementingnetdataprovider>&#93;](https://msdn.microsoft.com/library/a9fa1926-071b-4c6f-997d-a16bac633852).  
+ The <xref:System.Data.IDbDataAdapter> interface inherits from the <xref:System.Data.IDataAdapter> interface and allows an object to create a DataAdapter designed for use with a relational database. The <xref:System.Data.IDbDataAdapter> interface and, optionally, the utility class, <xref:System.Data.Common.DbDataAdapter>, allow an inheriting class to implement a DataAdapter class, which represents the bridge between a data source and a <xref:System.Data.DataSet>. For more information about DataAdapter classes, see [Populating a DataSet from a DataAdapter](~/docs/framework/data/adonet/populating-a-dataset-from-a-dataadapter.md). For more information about implementing .NET Framework data providers, see [Implementing a .NET Framework Data Provider](https://docs.microsoft.com/previous-versions/dotnet/netframework-1.1/4ksaf9z5(v=vs.71)).  
 
  An application does not create an instance of the <xref:System.Data.IDbDataAdapter> interface directly, but creates an instance of a class that inherits <xref:System.Data.IDbDataAdapter> and <xref:System.Data.Common.DbDataAdapter>.  
 

xml/System.Net/HttpWebRequest.xml

@@ -1445,7 +1445,7 @@ Both <xref:System.Net.HttpWebRequest> constructors are obsolete and should not b
 >  Your application cannot mix synchronous and asynchronous methods for a particular request. If you call the <xref:System.Net.HttpWebRequest.BeginGetRequestStream%2A> method, you must use the <xref:System.Net.HttpWebRequest.BeginGetResponse%2A> method to retrieve the response.  
 
 > [!NOTE]
->  This member outputs trace information when you enable network tracing in your application. For more information, see [&#91;\<topic://conUsingNetworkTracing>&#93;](https://msdn.microsoft.com/library/e993b7c3-087f-45d8-9c02-9dded936d804).  
+>  This member outputs trace information when you enable network tracing in your application. For more information, see [Network Tracing in the .NET Framework](https://docs.microsoft.com/dotnet/framework/network-programming/network-tracing).  
 
 
 

xml/System.Net/WebRequest.xml

@@ -742,7 +742,7 @@
  The <xref:System.Net.WebRequest.Create%2A> method uses the `requestUriString` parameter to create a <xref:System.Uri> instance that it passes to the new <xref:System.Net.WebRequest>.  
   
 > [!NOTE]
->  This member outputs trace information when you enable network tracing in your application. For more information, see [&#91;\<topic://conUsingNetworkTracing>&#93;](https://msdn.microsoft.com/library/e993b7c3-087f-45d8-9c02-9dded936d804).  
+>  This member outputs trace information when you enable network tracing in your application. For more information, see [Network Tracing in the .NET Framework](https://docs.microsoft.com/dotnet/framework/network-programming/network-tracing).
   
    
   
@@ -834,7 +834,7 @@
  .NET includes support for the `http://`, `https://`, `ftp://`, and `file://` URI schemes. Custom <xref:System.Net.WebRequest> descendants to handle other requests are registered with the <xref:System.Net.WebRequest.RegisterPrefix%2A> method.  
   
 > [!NOTE]
->  This member outputs trace information when you enable network tracing in your application. For more information, see [&#91;\<topic://conUsingNetworkTracing>&#93;](https://msdn.microsoft.com/library/e993b7c3-087f-45d8-9c02-9dded936d804).  
+>  This member outputs trace information when you enable network tracing in your application. For more information, see [Network Tracing in the .NET Framework](https://docs.microsoft.com/dotnet/framework/network-programming/network-tracing).  
   
    
   

xml/System.Runtime.Remoting.Channels.Http/HttpServerChannel.xml

@@ -598,7 +598,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- Channel properties are used to configure the channel at run time. For a list of possible channel properties and an example, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
+ Channel properties are used to configure the channel at run time. For a list of possible channel properties and an example, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
 
  ]]></format>
         </remarks>

xml/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.xml

@@ -333,7 +333,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- For more information, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
+ For more information, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
 
  ]]></format>
         </remarks>

xml/System.Runtime.Remoting.Channels/BinaryServerFormatterSink.xml

@@ -265,7 +265,7 @@
           <format type="text/markdown"><![CDATA[  
 
 ## Remarks  
- For more information, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
+ For more information, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
 
  ]]></format>
         </remarks>

xml/System.Runtime.Remoting.Channels/IClientFormatterSinkProvider.xml

@@ -30,7 +30,7 @@
 ## Remarks  
  A <xref:System.Runtime.Remoting.Channels.IClientFormatterSinkProvider> creates client formatter sinks for the client channel through which remoting messages flow. The first sink on the client side must implement both the <xref:System.Runtime.Remoting.Messaging.IMessageSink> and <xref:System.Runtime.Remoting.Channels.IClientChannelSink> interfaces, or the <xref:System.Runtime.Remoting.Channels.IClientFormatterSink> interface.  
 
- To use a `<formatter>` tag instead of a `<provider>` tag within a configuration file, the client channel sink provider must implement the <xref:System.Runtime.Remoting.Channels.IClientFormatterSinkProvider> interface instead of merely <xref:System.Runtime.Remoting.Channels.IClientChannelSinkProvider>. For additional information about remoting configuration, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)) and [Remoting Settings Schema](https://msdn.microsoft.com/library/dc2d1e62-9af7-4ca1-99fd-98b93bb4db9e).  
+ To use a `<formatter>` tag instead of a `<provider>` tag within a configuration file, the client channel sink provider must implement the <xref:System.Runtime.Remoting.Channels.IClientFormatterSinkProvider> interface instead of merely <xref:System.Runtime.Remoting.Channels.IClientChannelSinkProvider>. For additional information about remoting configuration, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)) and [Remoting Settings Schema](https://msdn.microsoft.com/library/dc2d1e62-9af7-4ca1-99fd-98b93bb4db9e).  
 
  Some formatter sink implementations use run-time formatters (<xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter> and <xref:System.Runtime.Serialization.Formatters.Soap.SoapFormatter>). Other implementations can use their own means to transform the channel message into the stream. On the return journey the formatter sink will transform the message stream back into the channel message elements (return message).  
 

xml/System.Runtime.Remoting.Channels/IServerFormatterSinkProvider.xml

@@ -30,7 +30,7 @@
 ## Remarks  
  A <xref:System.Runtime.Remoting.Channels.IServerFormatterSinkProvider> creates server formatter sinks for the server channel through which remoting messages flow.  
 
- To use a `<formatter>` tag instead of a `<provider>` tag within a configuration file, the server channel sink provider must implement the <xref:System.Runtime.Remoting.Channels.IClientFormatterSinkProvider> interface instead of <xref:System.Runtime.Remoting.Channels.IClientChannelSinkProvider>. For additional information about remoting configuration, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)) and [Remoting Settings Schema](https://msdn.microsoft.com/library/dc2d1e62-9af7-4ca1-99fd-98b93bb4db9e).  
+ To use a `<formatter>` tag instead of a `<provider>` tag within a configuration file, the server channel sink provider must implement the <xref:System.Runtime.Remoting.Channels.IClientFormatterSinkProvider> interface instead of <xref:System.Runtime.Remoting.Channels.IClientChannelSinkProvider>. For additional information about remoting configuration, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)) and [Remoting Settings Schema](https://msdn.microsoft.com/library/dc2d1e62-9af7-4ca1-99fd-98b93bb4db9e).  
 
  Some formatter sink implementations use run-time formatters (<xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter> and <xref:System.Runtime.Serialization.Formatters.Soap.SoapFormatter>). Other implementations can use their own means to transform the channel message into the stream. On the return journey, the formatter sink will transform the message stream back into the channel message elements (return message).  
 

xml/System.Runtime.Remoting.Contexts/Context.xml

@@ -33,7 +33,7 @@
 
  A new object's context is generally chosen based on meta-data attributes on the class. This mechanism is extensible through custom attributes. These are known as static-context properties, which are compiled into the class meta-data. Dynamic-context properties (also known as configuration properties) can be applied and configured by administrators.  
 
- For more information on contexts, see [&#91;\<topic://cpconboundariesprocessesapplicationdomainscontexts>&#93;](https://msdn.microsoft.com/library/7574180d-70df-44b8-8b78-55a119f2c96d).  
+ For more information on contexts, see [Boundaries: Processes and Application Domains](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kt21t9h7(v=vs.100)).  
 
  ]]></format>
     </remarks>

xml/System.Runtime.Remoting.Contexts/SynchronizationAttribute.xml

@@ -46,7 +46,7 @@
  When this attribute is applied to an object, only one thread can be executing in all contexts that share an instance of this property. This is done by contributing sinks that intercept and serialize incoming calls for the respective contexts. If the property is marked for reentry, then callouts are intercepted too. The callout interception allows other waiting threads to enter the synchronization domain for maximal throughput.  
   
 > [!NOTE]
->  There are two classes named `SynchronizationAttribute` : one in the <xref:System.Runtime.Remoting.Contexts> namespace, and the other in the <xref:System.EnterpriseServices> namespace. The <xref:System.EnterpriseServices.SynchronizationAttribute?displayProperty=nameWithType> class supports only synchronous calls, and can be used only with serviced components. (For more information on serviced components, see [&#91;\<topic://cpconservicedcomponentoverview>&#93;](https://msdn.microsoft.com/library/5133a620-9c8c-47bd-8e36-130e722fe463).) The <xref:System.Runtime.Remoting.Contexts.SynchronizationAttribute?displayProperty=nameWithType> supports both synchronous and asynchronous calls, and can be used only with context bound objects. (For more information on context bound objects, see the <xref:System.ContextBoundObject> class.)  
+>  There are two classes named `SynchronizationAttribute` : one in the <xref:System.Runtime.Remoting.Contexts> namespace, and the other in the <xref:System.EnterpriseServices> namespace. The <xref:System.EnterpriseServices.SynchronizationAttribute?displayProperty=nameWithType> class supports only synchronous calls, and can be used only with serviced components. (For more information on serviced components, see [Visual Studio 2005 Retired documentation](https://www.microsoft.com/download/details.aspx?id=55984).) The <xref:System.Runtime.Remoting.Contexts.SynchronizationAttribute?displayProperty=nameWithType> supports both synchronous and asynchronous calls, and can be used only with context bound objects. (For more information on context bound objects, see the <xref:System.ContextBoundObject> class.)  
   
 > [!NOTE]
 >  This class makes a link demand and an inheritance demand at the class level. A <xref:System.Security.SecurityException> is thrown when either the immediate caller or the derived class does not have infrastructure permission. For details about security demands, see [Link Demands](~/docs/framework/misc/link-demands.md) and [Inheritance Demands](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/x4yx82e6(v=vs.100)).  

xml/System.Runtime.Remoting.MetadataServices/SdlChannelSink.xml

@@ -257,7 +257,7 @@
 ## Remarks  
 
 > [!NOTE]
->  For more information, see [&#91;\<topic://cpconchannelformatterconfigurationproperties>&#93;](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
+>  For more information, see [Channel and Formatter Configuration Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kw7c6kwc(v=vs.100)).  
 
  ]]></format>
         </remarks>

xml/System.Runtime.Remoting/ActivatedClientTypeEntry.xml

@@ -31,7 +31,7 @@
 
  To activate a client-activated object type with the `new` keyword, you must first register the object type on the client using the <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterActivatedClientType%2A> method. By calling <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterActivatedClientType%2A> you are giving the remoting infrastructure the location of the remote application where `new` attempts to create it. If, on the other hand, you use the <xref:System.Activator.CreateInstance%2A?displayProperty=nameWithType> method to create a new instance of the client-activated object, you must supply the remote application's URL as a parameter, so no prior registration on the client end is necessary. To supply the <xref:System.Activator.CreateInstance%2A?displayProperty=nameWithType> method with the URL of the server on which you want to create the object, you must encapsulate the URL in an instance of the <xref:System.Runtime.Remoting.Activation.UrlAttribute> class.  
 
- For a detailed description of client activated objects and remote object activation see [&#91;\<topic://cpconActivation>&#93;](https://msdn.microsoft.com/library/e90d0c64-00da-4080-ae78-a6c558825c25).  
+ For a detailed description of client activated objects and remote object activation see [Activation of Remote Objects](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/cbzcxy2s(v=vs.100)).  
 
 
 

xml/System.Runtime.Remoting/ActivatedServiceTypeEntry.xml

@@ -33,7 +33,7 @@
 
  To activate a client-activated object type with the `new` keyword, you must first register the object type on the client using the <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterActivatedClientType%2A> method. By calling <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterActivatedClientType%2A> you are giving the remoting infrastructure the location of the remote application where `new` attempts to create it. If, on the other hand, you use the <xref:System.Activator.CreateInstance%2A> method to create a new instance of the client-activated object, you must supply the remote application's URL as a parameter, so no prior registration on the client is necessary. To supply the <xref:System.Activator.CreateInstance%2A> method with the URL of the server on which you want to create the object, you must encapsulate the URL in an instance of the <xref:System.Runtime.Remoting.Activation.UrlAttribute> class.  
 
- For a detailed description of client-activated objects and remote object activation, see [&#91;\<topic://cpconActivation>&#93;](https://msdn.microsoft.com/library/e90d0c64-00da-4080-ae78-a6c558825c25).  
+ For a detailed description of client-activated objects and remote object activation, see [Activation of Remote Objects](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/cbzcxy2s(v=vs.100)).  
 
 
 

xml/System.Runtime.Remoting/RemotingConfiguration.xml

@@ -260,7 +260,7 @@
 ## Remarks  
  Complete exception information includes the exact server exception and the server stack trace. Filtered information includes a standard remoting exception but no server stack trace.  
 
- The `CustomErrorsEnabled` method reflects configuration settings that were specified in the `mode` attribute of the `<customErrors>` element of the application configuration file. For more information about configuration options, see [&#91;\<topic://cpconconfiguration>&#93;](https://msdn.microsoft.com/library/92c0c097-d984-4315-835b-7490ecdf1097).  
+ The `CustomErrorsEnabled` method reflects configuration settings that were specified in the `mode` attribute of the `<customErrors>` element of the application configuration file. For more information about configuration options, see [Configuration of Remote Applications](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/b8tysty8(v=vs.100)).  
 
  The following table shows the three server channel property values that specify which callers receive exception information and what type of information they receive.  
 

xml/System.Runtime.Remoting/WellKnownClientTypeEntry.xml

@@ -31,7 +31,7 @@
 
  Any client that knows the URI of a registered server-activated object can obtain a proxy for this object by registering the channel it prefers with <xref:System.Runtime.Remoting.Channels.ChannelServices> and activating the object by calling `new` or <xref:System.Activator.GetObject%2A?displayProperty=nameWithType>. To activate a server-activated object with `new`, you must first register the server-activated object type on the client using the <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterWellKnownClientType%2A> method. By calling <xref:System.Runtime.Remoting.RemotingConfiguration.RegisterWellKnownClientType%2A>, you are giving the remoting infrastructure the location of the remote object, which allows the `new` keyword to create it. If, on the other hand, you use the <xref:System.Activator.GetObject%2A?displayProperty=nameWithType> method to activate a server-activated object, you must supply it with the object's URL as an argument, so no prior registration on the client is necessary.  
 
- For a detailed description of server-activated objects and remote object activation, see [&#91;\<topic://cpconActivation>&#93;](https://msdn.microsoft.com/library/e90d0c64-00da-4080-ae78-a6c558825c25).  
+ For a detailed description of server-activated objects and remote object activation, see [Activation of Remote Objects](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/cbzcxy2s(v=vs.100)).  
 
 
 

xml/System.Runtime.Remoting/WellKnownServiceTypeEntry.xml

@@ -33,7 +33,7 @@
 
  It is important to note that the remote object itself is not created by the registration process. This only happens when a client attempts to call a method on the object or activates the object from the client side.  
 
- For a more detailed description of server-activated objects and remote object activation, see [&#91;\<topic://cpconActivation>&#93;](https://msdn.microsoft.com/library/e90d0c64-00da-4080-ae78-a6c558825c25).  
+ For a more detailed description of server-activated objects and remote object activation, see [Activation of Remote Objects](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/cbzcxy2s(v=vs.100)).