Remove references to Technet

xml/System.Web.Configuration/MachineKeySection.xml

@@ -165,7 +165,7 @@
 
 -   The framework will not produce signed-only payloads. Forms authentication tickets will always be both encrypted and signed, regardless of how the `protection` attribute of the `forms` element is set in the Web.config file. View state will always be both encrypted and signed if either `EnableViewStateMac` or `RequireViewStateEncryption` is set for a given page.  
 
- As a result of the security update that is described in [Microsoft security bulletin MS10-070](https://technet.microsoft.com/security/bulletin/MS10-070), the default encryption behavior is the same for the `Framework20SP1` and `Framework20SP2` settings. Changing the default behavior is not recommended, but if you want to do that, see [How to configure legacy encryption mode in ASP.NET](https://support.microsoft.com/kb/2425938).  
+ As a result of the security update that is described in [Microsoft security bulletin MS10-070](https://docs.microsoft.com/security-updates/SecurityBulletins/2010/ms10-070), the default encryption behavior is the same for the `Framework20SP1` and `Framework20SP2` settings. Changing the default behavior is not recommended, but if you want to do that, see [How to configure legacy encryption mode in ASP.NET](https://support.microsoft.com/kb/2425938).  
 
  ]]></format>
         </remarks>

xml/System.Web.Management/WebApplicationLifetimeEvent.xml

@@ -37,7 +37,7 @@
 
 ```  
 
- The Application Lifetime Events performance counter contains the sum total of all ASP.NET lifetime events. To view this performance counter in System Monitor (PerfMon), in the **Add Counters** window select **ASP.NET** from the **Performance object** drop-down list. Select the **Application Lifetime Events** performance counter, and click the **Add** button. For more information, see "Using the System Monitor (PerfMon) with ASP.NET Applications" on [MSDN](https://go.microsoft.com/fwlink/?linkid=37118). If you allow events to be logged by the standard <xref:System.Web.Management.EventLogWebEventProvider>, you can view them in Event Viewer by selecting the **Application** log. For more information, see [Event Viewer](https://go.microsoft.com/fwlink/?linkid=24845&clcid=0x409) in the Windows Server 2003 documentation on TechNet.  
+ The Application Lifetime Events performance counter contains the sum total of all ASP.NET lifetime events. To view this performance counter in System Monitor (PerfMon), in the **Add Counters** window select **ASP.NET** from the **Performance object** drop-down list. Select the **Application Lifetime Events** performance counter, and click the **Add** button. For more information, see "Using the System Monitor (PerfMon) with ASP.NET Applications" on [MSDN](https://go.microsoft.com/fwlink/?linkid=37118). If you allow events to be logged by the standard <xref:System.Web.Management.EventLogWebEventProvider>, you can view them in [Event Viewer](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2003/cc756915\(v=ws.10\)) by selecting the **Application** log.
 
 > [!CAUTION]
 >  Because the <xref:System.Web.Management.WebApplicationLifetimeEvent> object is a high-volume event, logging it is resource-intensive and might slow down your system. It can also cause other events to be overwritten in the case of the <xref:System.Web.Management.EventLogWebEventProvider> class due to the high volume of events and the way the event logging works.  

xml/ns-System.Diagnostics.PerformanceData.xml

@@ -37,13 +37,13 @@
 
     4.  Use the <xref:System.Diagnostics.PerformanceData.CounterSetInstance.Counters%2A?displayProperty=nameWithType> property to access and set the counter data for the counter.  
 
-4.  After you finish your provider, use the LodCtr tool to register the counters on the computer. For example,  
+4.  After you finish your provider, use the [LodCtr](https://docs.microsoft.com/windows/desktop/perfctrs/adding-counter-names-and-descriptions-to-the-registry#running-the-lodctr-tool) tool to register the counters on the computer. For example,  
 
     ```console  
     lodctr /m:provider.man  
     ```  
 
-     The example assumes the manifest and executable file are in the current directory. For complete details on using the LodCtr, see [Microsoft Technet](https://Go.Microsoft.Com/FWLink/?LinkId=84000).  
+     The example assumes the manifest and executable file are in the current directory.  
 
  You can use the classes in this namespace on computers that run the Windows Vista and later operating systems.