Update README.md

1 files changed, 22 insertions, 14 deletions

diff --git a/storage/msdsm/ReadMe.md b/storage/msdsm/ReadMe.md
index 6bfdbc06..4d4971a8 100644
--- a/storage/msdsm/ReadMe.md
+++ b/storage/msdsm/ReadMe.md
@@ -14,13 +14,13 @@ Building a Driver Using Visual Studio
 
 You build a driver the same way you build any project or solution in Visual Studio. When you create a new driver project using a Windows driver template, the template defines a default (active) project configuration and a default (active) solution build configuration. When you create a project from existing driver sources or convert existing driver code that was built with previous versions of the WDK, the conversion process preserves the target version information (operating systems and platform).
 
-The default Solution build configuration is Windows 8.1 Debug and Win32.
+The default Solution build configuration is **Debug** and **Win32**.
 
 ### To select a configuration and build a driver or an application
 
 1.  Open the driver project or solution in Visual Studio (find *samplename*.sln or *samplename*.vcxproj).
 2.  Right-click the solution in the **Solutions Explorer** and select **Configuration Manager**.
-3.  From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Windows 8.1 Debug or Windows 8.1 Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in.
+3.  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.
 4.  From the Build menu, click **Build Solution** (Ctrl+Shift+B).
 
 Building a Driver Using the Command Line (MSBuild)
@@ -31,7 +31,9 @@ You can build a driver from the command line using the Visual Studio Command Pro
 ### To select a configuration and build a driver or an application
 
 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.
-2.  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**.
+2.  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
 --------------------------
@@ -42,13 +44,15 @@ The installer sample only needs to be called one time with the INF/driver source
 
 The following annotated DSM INF file illustrates the correct format for your DSM. Replace only those items that are in bold italics. Remember, you must not use "GENDSM" or "MSISCDSM" or "MSDSM" as the name of your DSM. Therefore, you must replace any instances of those strings with the proper name of your DSM.
 
+```
 ;
 ; Copyright (c) <YOUR COMPANY NAME HERE>.  All rights reserved.
 ;
-
+```
 
 In the Version section, make sure the DriverVer is correct for your DSM. Ideally it should match the version in the RC file. You must specify a different catalog file since the MPIO core drivers now come pre-signed:
 
+```
 [Version]
 Signature   = "$WINDOWS NT$"
 Class       = System
@@ -66,10 +70,11 @@ DefaultDestDir = 12
 
 [Manufacturer]
 %std_mfg% = std_mfg
+```
 
 Substitute all instances of "gendsm" with the proper name for your DSM. For example, "mydsm":
 
-
+```
 [std_mfg]
 %mydsm_devicedesc% = mydsm_install, Root\MYDSM
 
@@ -87,7 +92,7 @@ ErrorControl   = %SERVICE_ERROR_NORMAL%
 ServiceBinary  = %12%\mydsm.sys
 LoadOrderGroup = "System Bus Extender"
 AddReg         = mydsm_addreg
-
+```
 
 This next section contains the Hardware ID strings for your devices. You can have more than one. Sample format: "VENDOR PRODUCT " - remember to use spaces in a field (vendor, product ID) to pad this to be eight characters for the vendor name (as registered with STA) and sixteen for the product ID (unless the supported devices share a common prefix, in which case the product ID can be less than 16 characters).
 
@@ -95,20 +100,22 @@ This next section contains the Hardware ID strings for your devices. You can hav
 
 In this sample, there are two different strings:
 
+```
 ;
 ; The following cannot be grouped (as above)
 ;
 
 HKLM, "SYSTEM\CurrentControlSet\Control\MPDEV", "MPIOSupportedDeviceList", %REG_MULTI_SZ_APPEND%, "VENDOR1 PRODUCT1        "
 HKLM, "SYSTEM\CurrentControlSet\Control\MPDEV", "MPIOSupportedDeviceList", %REG_MULTI_SZ_APPEND%, "VENDOR2 PRODUCT2        "
+```
 
 These are valid samples:
 
-
+```
 HKLM, "SYSTEM\CurrentControlSet\Control\MPDEV", "MPIOSupportedDeviceList", %REG_MULTI_SZ_APPEND%, "MAXTOR  ATLASU320_18_WLS"
 
 HKLM, "SYSTEM\CurrentControlSet\Control\MPDEV", "MPIOSupportedDeviceList", %REG_MULTI_SZ_APPEND%, "VENDOR3 PROD_PREFIX"
-
+```
 
 (to replace "VENDOR3 PROD\_PREFIX\_A ", "VENDOR3 PROD\_PREFIX\_B " and "VENDOR3 PROD\_PREFIX\_C ")
 
@@ -118,7 +125,7 @@ It is advisable to use this format if your storage devices generate product IDs
 
 Add one entry for each WMI GUID that you use in your DSM. This is required:
 
-
+```
 HKLM, "SYSTEM\CurrentControlSet\Control\WMI\Security", "04517f7e-92bb-4ebe-aed0-54339fa5f544",\%REG_BINARY_NOCLOBBER%,\
         01,00,04,80,14,00,00,00,24,00,00,00,00,00,00,00,\
         34,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,\
@@ -148,17 +155,18 @@ HKLM, "SYSTEM\CurrentControlSet\Control\WMI\Security", "d6dc1bf0-95fa-4246-afd7-
 ;
 ; Localizable Strings
 ;
-
+```
 
 Finally, modify the following strings:
 
+```
 [Strings]
 VNDR              = "Your Company Name Here"
 std_mfg           = "(Standard system devices)"
 mydsm_devicedesc = "<Your product> Multi-Path Device Specific Module"
-
+```
 The following string is displayed as the friendly name of your DSM:
-
+```
 mydsm_desc       = "<Your product name> Multi-Path DSM"
 
 ;
@@ -182,14 +190,14 @@ REG_MULTI_SZ_APPEND    = 0x00010008
 REG_EXPAND_SZ          = 0x00020000
 REG_DWORD              = 0x00010001
 REG_BINARY_NOCLOBBER   = 0x00030003
-
+```
 You should be aware of the following when you install the MPIO DSM sample:
 
 1.  The install sample assumes that all necessary files have already been copied over to a vendor specific directory (preferably a folder under Program Files) and takes that path as one of the parameters. This eliminates requests for the original media when new devices appear.
 
 2.  As the port filter needs to go on top of every adapter that hosts (or might host) a path to the disk, all SCSI adapters are restarted at the end of the install
 
-    It is expected that the adapter that hosts the system volumes (boot/paging) will not restart, but that should not be problem if you are not multipathing the boot volume. However, if you are multipathing the boot volume, you will need to restart the system.
+It is expected that the adapter that hosts the system volumes (boot/paging) will not restart, but that should not be problem if you are not multipathing the boot volume. However, if you are multipathing the boot volume, you will need to restart the system.
 
 **Note**  Other filter drivers installed as port filters may interfere with the proper operation of the MPIO port filter. Microsoft does not recommend the use of such filter drivers which may be supplied by HBA miniport vendors.