Update README.md (#421)8552485523855228552185520855198551885517855168551585514855138551285511855108550985508855078550685505

6 files changed, 6 insertions, 6 deletions

diff --git a/general/DCHU/README.md b/general/DCHU/README.md
index a4d1dd25..f2a4addb 100644
--- a/general/DCHU/README.md
+++ b/general/DCHU/README.md
@@ -23,7 +23,7 @@ There are three Visual Studio solutions in this sample.  Each one represents a s
 Both `osrfx2_DCHU_extension_loose` and `osrfx2_DCHU_extension_tight` provide the same functionality, so installing both on the same OSR FX2 device is unnecessary.  They are intended to show a different way to use extension and component INFs depending on a project's needs.
 
 > [!NOTE]
-> Information the user should notice even if skimmingosrfx2_DCHU_extension_tight will not currently build on Windows 10 version 1703.  You will see an error saying that the directive CopyINF does not work from extension INFs.  This has been fixed for the Windows 10 Fall Creators Update.
+> osrfx2_DCHU_extension_tight will not currently build on Windows 10 version 1703.  You will see an error saying that the directive CopyINF does not work from extension INFs.  This has been fixed for the Windows 10 Fall Creators Update.
 
 Each of these solutions can be built with the latest WDK on Visual Studio 2015.  Additionally, you can also download a [Universal Windows Platform app (UWP)](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/CustomCapability) that controls the OSR FX2 Learning Kit's device.  To learn how to pair a UWP app with a device, see [Hardware access for Universal Windows Platform apps](https://docs.microsoft.com/windows-hardware/drivers/devapps/hardware-access-for-universal-windows-platform-apps)
 
diff --git a/general/PLX9x5x/README.md b/general/PLX9x5x/README.md
index ec998813..39726800 100644
--- a/general/PLX9x5x/README.md
+++ b/general/PLX9x5x/README.md
@@ -12,7 +12,7 @@ products:
 
 This sample demonstrates how to write driver for a generic PCI device using Windows Driver Framework. The target hardware for this driver is PLX9656/9653RDK-LITE board. The product kit and the hardware specification are available at the [PLX Technology](http://www.plxtech.com) website.
 
-For more information, see [Peripheral Component Interconnect (PCI) Bus Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff537451).
+For more information, see the [PCI driver programming guide](https://docs.microsoft.com/windows-hardware/drivers/pci/).
 
 The device is a PCI device with port, memory, interrupt and DMA resources. The device can be stopped and started at run-time and also supports low power states. The driver is capable of doing concurrent read and write operations to the device but it can handle only one read or write request at any time. The following driver framework interfaces are demonstrated in this sample:
 
diff --git a/general/echo/umdf2/README.md b/general/echo/umdf2/README.md
index b5f1d461..6ddc0555 100644
--- a/general/echo/umdf2/README.md
+++ b/general/echo/umdf2/README.md
@@ -74,4 +74,4 @@ As an alternative to building the driver sample in Visual Studio, you can build
 
 `msbuild /p:configuration="Release" /p:platform="Win32" umdf2echo.sln`
 
-For more information about using MSBuild to build a driver package, see [MSBuild primer for WDK developers](https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/msbuild-primer-for-wdk-developers).
+For more information about using MSBuild to build a driver package, see [MSBuild primer for WDK developers](https://docs.microsoft.com/windows-hardware/drivers/devtest/msbuild-primer-for-wdk-developers).
diff --git a/general/echo/umdfSocketEcho/README.md b/general/echo/umdfSocketEcho/README.md
index 724e251e..d4a6077f 100644
--- a/general/echo/umdfSocketEcho/README.md
+++ b/general/echo/umdfSocketEcho/README.md
@@ -30,7 +30,7 @@ This sample driver is a minimal driver that is intended to demonstrate how to us
 
 ## Installation
 
-In Visual Studio, you can press F5 to build the sample and then deploy it to a target machine. For more information, see [Deploying a Driver to a Test Computer](http://msdn.microsoft.com/en-us/library/windows/hardware/hh454834). Alternatively, you can install the sample from the command line.
+In Visual Studio, you can press F5 to build the sample and then deploy it to a target machine. For more information, see [Deploying a Driver to a Test Computer](https://docs.microsoft.com/windows-hardware/drivers/develop/deploying-a-driver-to-a-test-computer). Alternatively, you can install the sample from the command line.
 
 To test this sample, you must have a test computer. This test computer can be a second computer or, if necessary, your development computer.
 
diff --git a/general/toaster/umdf2/README.md b/general/toaster/umdf2/README.md
index fbc282a3..fb3741c6 100644
--- a/general/toaster/umdf2/README.md
+++ b/general/toaster/umdf2/README.md
@@ -26,7 +26,7 @@ The process of moving the driver package to the target computer and installing t
 
 ### Automatic deployment (root enumerated)
 
-Before you automatically deploy a driver, you must provision the target computer. For instructions, see [Configuring a Computer for Driver Deployment, Testing, and Debugging](http://msdn.microsoft.com/en-us/library/windows/hardware/).
+Before you automatically deploy a driver, you must provision the target computer. For instructions, see [Provision a computer for driver deployment and testing](https://docs.microsoft.com/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1).
 
 1. On the host computer, in Visual Studio, in Solution Explorer, right click **package** (lower case), and choose **Properties**. Navigate to **Configuration Properties \> Driver Install \> Deployment**.
 
diff --git a/general/tracing/evntdrv/README.md b/general/tracing/evntdrv/README.md
index 392681f1..cf2d5f06 100644
--- a/general/tracing/evntdrv/README.md
+++ b/general/tracing/evntdrv/README.md
@@ -23,7 +23,7 @@ Evntdrv registers as a provider by calling the [**EtwRegister**](https://docs.mi
 
     `wevtutil im evntdrv.xml`
 
-    Installing the manifest creates registry keys that enable tools to find the resource and message files that contain event provider information. For further details about the WevtUtil.exe tool, see the MSDN Library.
+    Installing the manifest creates registry keys that enable tools to find the resource and message files that contain event provider information. For further details, see [wevtutil](https://docs.microsoft.com/windows-server/administration/windows-commands/wevtutil).
 
     > [!NOTE]
     > Using a Visual Studio Command windows sets up the environment variables you need to run the tracing tools for this sample.