Update README.md (#425)8758187580875798757887577875768757587574875738757287571875708756987568875678756687565875648756387562

3 files changed, 28 insertions, 27 deletions

diff --git a/storage/class/cdrom/README.md b/storage/class/cdrom/README.md
index 56e68f15..4b081014 100644
--- a/storage/class/cdrom/README.md
+++ b/storage/class/cdrom/README.md
@@ -15,7 +15,9 @@ The CD ROM driver is used to provide access to CD, DVD and Blu-ray drives. It su
 ## Build the sample
 
 You can build the sample in two ways: using Microsoft Visual Studio or the command line (*MSBuild*).
-**Note:** When building in Visual Studio, INFVerifer will throw errors. This is intended. Fix those errors with your custom values to build successfully.
+
+> [!NOTE]
+> When building in Visual Studio, INFVerifer will throw errors. This is intended. Fix those errors with your custom values to build successfully.
 
 ## Building a Driver Using Visual Studio
 
@@ -24,8 +26,11 @@ You build a driver the same way you build any project or solution in Visual Stud
 The default Solution build configuration is Visual Studio Debug and Win32.
 
 1. Open the driver project or solution in Visual Studio (find *samplename*.sln or *samplename*.vcxproj).
+
 1. Right-click the solution in the **Solutions Explorer** and select **Configuration Manager**.
+
 1. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Debug or Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in.
+
 1. From the Build menu, click **Build Solution** (Ctrl+Shift+B).
 
 ## Building a Driver Using the Command Line (MSBuild)
@@ -33,25 +38,37 @@ The default Solution build configuration is Visual Studio Debug and Win32.
 You can build a driver from the command line using the Visual Studio Command Prompt window and the Microsoft Build Engine (MSBuild.exe) Previous versions of the WDK used the Windows Build utility (Build.exe) and provided separate build environment windows for each of the supported build configurations. You can now use the Visual Studio Command Prompt window for all build configurations.
 
 1. Open a Visual Studio Command Prompt window at the **Start** screen. From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file.
+
 1. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called *filtername*.vcxproj, navigate to the project directory and enter the following MSBuild command:
 
-    **msbuild /t:clean /t:build .\\***samplename***.vcxproj**.
+    `msbuild /t:clean /t:build .\<samplename>.vcxproj`
 
 ## Installation and Operation
 
 The in-box CD ROM driver is protected by the system, and thus a normal device driver update attempt through the Device Manager will fail. Users are not encouraged to replace the in-box CD ROM driver. The following work-around is provided in case there is a need, but the users are warned that this may harm the system.
 
 1. Locate the "cdrom.inf" file in the binary output directory, and update the file by replacing all "cdrom.sys" occurrences with "mycdrom.sys".
+
 1. Rename the "cdrom.inf" file to "mycdrom.inf".
+
 1. Copy "mycdrom.sys" and "mycdrom.inf" from the binary output directory to the test machine, if applicable.
+
 1. Launch the Device Manager
+
 1. Select the appropriate device under the "DVD/CD-ROM drives" category.
+
 1. On the right-click menu, select "Update Driver Software...".
+
 1. Select "Browse my computer for driver software".
+
 1. Select "Let me pick from a list of device drivers on my computer".
+
 1. Click "Have Disk...", and point to the directory that contains "mycdrom.inf" and "mycdrom.sys".
+
 1. Click "Next". If you get a warning dialog about installing unsigned driver, click "Yes".
+
 1. Click "Next" to complete the driver upgrade.
+
 1. After installation completes successfully, "mycdrom.sys" will be the effective driver for the device, "cdrom.sys" will no longer be used.
 
 For more information, see [CD-ROM Drivers](https://docs.microsoft.com/windows-hardware/drivers/storage/cd-rom-drivers) in the storage technologies design guide.
diff --git a/storage/class/classpnp/README.md b/storage/class/classpnp/README.md
index 2de5c329..f89e774a 100644
--- a/storage/class/classpnp/README.md
+++ b/storage/class/classpnp/README.md
@@ -8,17 +8,6 @@ products:
 - windows-wdk
 ---
 
-
-
-<!---
-    name: ClassPnP Class Driver Library 
-    platform: WDM
-    language: cpp
-    category: Storage
-    description: A library storage class driver used by disk, CDROM, and the tape class drivers.
-    samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617978
---->
-
 # ClassPnP Storage Class Driver Library
 
 This is the library for all storage drivers. It simplifies writing a storage class driver by implementing 90 percent of the code that you need to support Plug and Play (PnP), power management, and so on. This library is used by disk, CDROM, and the tape class drivers.
@@ -31,4 +20,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a
 
 The storage class drivers are used to interact with mass storage devices along with appropriate port driver. The class drivers are layered above the port drivers and manage mass storage devices of a specific class, regardless of their bus type. The classpnp sample contains the common routines that are required for all storage class drivers such as PnP and power management. It also provides I/O and error handling support.
 
-For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide.
\ No newline at end of file
+For more information, see [Introduction to Storage Class Drivers](https://docs.microsoft.com/windows-hardware/drivers/storage/introduction-to-storage-class-drivers) in the storage technologies design guide.
diff --git a/storage/class/disk/README.md b/storage/class/disk/README.md
index 8dd297bd..d1518c0e 100644
--- a/storage/class/disk/README.md
+++ b/storage/class/disk/README.md
@@ -8,17 +8,6 @@ products:
 - windows-wdk
 ---
 
-
-
-<!---
-    name: Disk Class Driver
-    platform: WDM
-    language: cpp
-    category: Storage
-    description: A class driver for disk devices.  
-    samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617979
---->
-
 # Disk Class Driver
 
 The disk class driver sample is used for managing disk devices
@@ -32,8 +21,11 @@ You build a driver the same way you build any project or solution in Visual Stud
 The default Solution build configuration is Debug and Win32.
 
 1. Open the driver project or solution in Visual Studio (find *samplename*.sln or *samplename*.vcxproj).
+
 1. Right-click the solution in the **Solutions Explorer** and select **Configuration Manager**.
+
 1. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Debug or Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in.
+
 1. From the Build menu, click **Build Solution** (Ctrl+Shift+B).
 
 ## Building a Driver Using the Command Line (MSBuild)
@@ -41,10 +33,13 @@ The default Solution build configuration is Debug and Win32.
 You can build a driver from the command line using the Visual Studio Command Prompt window and the Microsoft Build Engine (MSBuild.exe) Previous versions of the WDK used the Windows Build utility (Build.exe) and provided separate build environment windows for each of the supported build configurations. You can now use the Visual Studio Command Prompt window for all build configurations.
 
 1. Open a Visual Studio Command Prompt window at the **Start** screen. From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file.
-1. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called *filtername*.vcxproj, navigate to the project directory and enter the following MSBuild command: **msbuild /t:clean /t:build .\\***samplename***.vcxproj**.
+
+1. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called *filtername*.vcxproj, navigate to the project directory and enter the following MSBuild command:
+
+    `msbuild /t:clean /t:build .\<samplename>.vcxproj`
 
 ## Installation and Operation
 
 The disk class driver is used to interact with disk devices along with the appropriate port driver. The disk class driver is layered above the port driver and manages disk devices regardless of their bus type. This driver attaches to the disk devices that are enumerated by all of the storage port drivers. This driver exposes the required functionality to the file system drivers to access the disk devices.
 
-For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide.
\ No newline at end of file
+For more information, see [Introduction to Storage Class Drivers](https://docs.microsoft.com/windows-hardware/drivers/storage/introduction-to-storage-class-drivers) in the storage technologies design guide.