Replace NIB links with docs/previous equivalent (#3135)

* Replace NIB links with docs/previous equivalent

* apply @mairaw's suggestion

Make /previous-versions/ links absolute:
https://docs.microsoft.com/previous-versions/

Author: nemrism

xml/System.Web.Configuration/HttpModuleAction.xml

@@ -31,7 +31,7 @@
   
  The following configuration file example shows how to specify values declaratively for the `httpModules` section.  
   
- Refer to the [NIB: How to: Create and Configure an HTTP Module](https://msdn.microsoft.com/library/4174fd13-a9c4-4ff6-baa5-3f7d7fc73ef3) to see how to build and configure an HTTP module.  
+ Refer to the [How to: Create and Configure an HTTP Module](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/tfd6k449(v=vs.85)) to see how to build and configure an HTTP module.  
   
 ```  
 <httpModules>  

xml/System.Web.Configuration/HttpModuleActionCollection.xml

@@ -35,7 +35,7 @@
  [!code-csharp[System.Web.Configuration.HttpModuleActionCollection#1](~/samples/snippets/csharp/VS_Snippets_WebNet/System.Web.Configuration.HttpModuleActionCollection/CS/httpmoduleactioncollection.cs#1)]
  [!code-vb[System.Web.Configuration.HttpModuleActionCollection#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/System.Web.Configuration.HttpModuleActionCollection/VB/httpmoduleactioncollection.vb#1)]  
   
- The following example is an excerpt of the configuration file that enables ASP.NET to use a custom module. For a complete example of how to build and configure an HTTP module, see the [NIB: How to: Create and Configure an HTTP Module](https://msdn.microsoft.com/library/4174fd13-a9c4-4ff6-baa5-3f7d7fc73ef3).  
+ The following example is an excerpt of the configuration file that enables ASP.NET to use a custom module. For a complete example of how to build and configure an HTTP module, see the [How to: Create and Configure an HTTP Module](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/tfd6k449(v=vs.85)).  
   
 ```  
 <httpModules>  

xml/System.Web.Management/BufferedWebEventProvider.xml

@@ -25,7 +25,7 @@
  If you want to customize the health-event processing, you can derive from the <xref:System.Web.Management.BufferedWebEventProvider> class to create your own custom buffered provider.  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
    
   

xml/System.Web.Management/EventLogWebEventProvider.xml

@@ -25,7 +25,7 @@
  The <xref:System.Web.Management.EventLogWebEventProvider>, the failure audit, and the error health-monitoring events are configured (enabled) by default. This means that the failure audit and the error health-monitoring events are logged in the Windows Application Event Log by default.  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
    
   
@@ -50,7 +50,7 @@
  ]]></format>
     </remarks>
     <related type="Article" href="https://msdn.microsoft.com/library/e003f224-70fe-4cd8-a71a-2dc81e2d7e4c">ASP.NET Health Monitoring Overview</related>
-    <related type="Article" href="https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c">ASP.NET Health-Monitoring Custom Provider Sample</related>
+    <related type="Article" href="https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)">ASP.NET Health-Monitoring Custom Provider Sample</related>
     <related type="Article" href="https://msdn.microsoft.com/library/ab894e83-7e2f-4af8-a116-b1bff8f815b2">Installing and Configuring ASP.NET Providers</related>
   </Docs>
   <Members>

xml/System.Web.Management/MailWebEventProvider.xml

@@ -25,7 +25,7 @@
  The <xref:System.Web.Management.MailWebEventProvider> class is a base class for building providers that monitor Web events and send email for selected events. This class supports the .NET Framework infrastructure and is not intended to be inherited from or used directly from your code.  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
  ]]></format>
     </remarks>

xml/System.Web.Management/SqlWebEventProvider.xml

@@ -25,7 +25,7 @@
  This provider has a comprehensive set of configuration attributes that you can use to customize its behavior.  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
    
   

xml/System.Web.Management/TraceWebEventProvider.xml

@@ -28,7 +28,7 @@
 >  The <xref:System.Web.Management.TraceWebEventProvider> object does not provide event buffering.  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `healthMonitoring` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
    
   

xml/System.Web.Management/WebEventProvider.xml

@@ -64,7 +64,7 @@
  ]]></format>
     </remarks>
     <related type="Article" href="https://msdn.microsoft.com/library/e003f224-70fe-4cd8-a71a-2dc81e2d7e4c">ASP.NET Health Monitoring Overview</related>
-    <related type="Article" href="https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c">Example: Custom Event Provider</related>
+    <related type="Article" href="https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)">Example: Custom Event Provider</related>
     <related type="Article" href="https://msdn.microsoft.com/library/ab894e83-7e2f-4af8-a116-b1bff8f815b2">Installing and Configuring ASP.NET Providers</related>
   </Docs>
   <Members>

xml/System.Web.Management/WmiWebEventProvider.xml

@@ -24,10 +24,10 @@
   
  ASP.NET uses this class to map health-monitoring events to WMI events. To enable the delivery of ASP.NET health-monitoring events to the WMI subsystem, you must configure the <xref:System.Web.Management.WmiWebEventProvider> class by adding the appropriate settings in the `<healthMonitoring>` section of the configuration file.  
   
- The information contained in the Aspnet.mof file describes the parameters of the WMI events raised when ASP.NET health-monitoring events are routed to the <xref:System.Web.Management.WmiWebEventProvider> class and mapped into WMI events. The Aspnet.mof file is stored in the .NET Framework build directory, for example %windir%\Microsoft.NET\Framework\\*BuildNumber*. For more information about reporting health-monitoring events as WMI events, see [NIB: Using WMI to Deliver ASP.NET Health Monitoring Events](https://msdn.microsoft.com/library/e57fea2f-610f-4432-9dd6-dd10a6c5bd10).  
+ The information contained in the Aspnet.mof file describes the parameters of the WMI events raised when ASP.NET health-monitoring events are routed to the <xref:System.Web.Management.WmiWebEventProvider> class and mapped into WMI events. The Aspnet.mof file is stored in the .NET Framework build directory, for example %windir%\Microsoft.NET\Framework\\*BuildNumber*. For more information about reporting health-monitoring events as WMI events, see [Using WMI to Deliver ASP.NET Health Monitoring Events](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/ms178709(v=vs.85)).  
   
 > [!NOTE]
->  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c).  
+>  In most cases you will be able to use the ASP.NET health-monitoring types as implemented, and you will control the health-monitoring system by specifying values in the `<healthMonitoring>` configuration section. You can also derive from the health-monitoring types to create your own custom events and providers. For an example of creating a custom provider, see [How to: Implement the Health Monitoring Custom Provider Example](https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)).  
   
    
   
@@ -57,7 +57,7 @@
  ]]></format>
     </remarks>
     <related type="Article" href="https://msdn.microsoft.com/library/e003f224-70fe-4cd8-a71a-2dc81e2d7e4c">ASP.NET Health Monitoring Overview</related>
-    <related type="Article" href="https://msdn.microsoft.com/library/bbb1c959-e6e4-42b2-be62-49b7ca5ab72c">ASP.NET Health-Monitoring Custom Provider Sample</related>
+    <related type="Article" href="https://docs.microsoft.com/previous-versions/ms178718(v=vs.140)">ASP.NET Health-Monitoring Custom Provider Sample</related>
     <related type="Article" href="https://msdn.microsoft.com/library/ab894e83-7e2f-4af8-a116-b1bff8f815b2">Installing and Configuring ASP.NET Providers</related>
   </Docs>
   <Members>

xml/System.Web.UI.HtmlControls/HtmlAnchor.xml

@@ -537,7 +537,7 @@
 > [!NOTE]
 >  The <xref:System.Web.UI.HtmlControls.HtmlAnchor.Target%2A> property renders as a `target` attribute. The `target` attribute on `a` elements is not allowed in the XHTML 1.1 document type definition. Do not set the <xref:System.Web.UI.HtmlControls.HtmlAnchor.Target%2A> property if the rendered output for the <xref:System.Web.UI.HtmlControls.HtmlAnchor> must be compliant with XHTML 1.1. For more information, see [XHTML Standards in Visual Studio and ASP.NET](https://msdn.microsoft.com/library/1b78d416-66bb-43a5-ac77-c703aab55b97).  
 >   
->  When creating accessible Web pages, avoid using the <xref:System.Web.UI.HtmlControls.HtmlAnchor.Target%2A> property to target another window. For more information, see [NIB: ASP.NET Accessibility](https://msdn.microsoft.com/library/9b5f3e05-e88d-4248-a5f4-9e64850fa0ae).  
+>  When creating accessible Web pages, avoid using the <xref:System.Web.UI.HtmlControls.HtmlAnchor.Target%2A> property to target another window. For more information, see [ASP.NET Accessibility](https://docs.microsoft.com/previous-versions/aspnet/ms228011(v=vs.100)).  
   
  The <xref:System.Web.UI.HtmlControls.HtmlAnchor.Target%2A> value must begin with a letter in the range of A to Z (case-insensitive), except for the following special values, which begin with an underscore.