Update README.md

3 files changed, 9 insertions, 9 deletions

diff --git a/storage/filters/addfilter/ReadMe.md b/storage/filters/addfilter/ReadMe.md
index ea8d4979..3981aa20 100644
--- a/storage/filters/addfilter/ReadMe.md
+++ b/storage/filters/addfilter/ReadMe.md
@@ -10,7 +10,7 @@ This initial sample does not check the filter for validity before it is added to
 
 The minifilter identifies implicit locks when it sees a non-shared write open request on a volume object. In this scenario, the minifilter closes its metadata file and sets a trigger that corresponds to the volume in its instance object. Later, each close operation is examined to identify if the implicit lock on the volume is being released and, if so, a re-open of the minifilter's metadata file is triggered.
 
-**Important**  If you attempt to add a non-existing filter to a boot device and then restart, the system might show the INACCESSIBLE\_BOOT\_DEVICE error message. If this message appears, you will be unable to start the computer. To fix this problem, when the startup menu is displayed when the computer starts up, go to the Advanced Options screen and select **Use Last Known Good Profile**.
+**Important** If you attempt to add a non-existing filter to a boot device and then restart, the system might show the INACCESSIBLE\_BOOT\_DEVICE error message. If this message appears, you will be unable to start the computer. To fix this problem, when the startup menu is displayed when the computer starts up, go to the Advanced Options screen and select **Use Last Known Good Profile**.
 
 The sample is intended for use with upper filter drivers only.
 
diff --git a/storage/msdsm/ReadMe.md b/storage/msdsm/ReadMe.md
index 4d4971a8..d43f1b68 100644
--- a/storage/msdsm/ReadMe.md
+++ b/storage/msdsm/ReadMe.md
@@ -32,8 +32,8 @@ You can build a driver from the command line using the Visual Studio Command Pro
 
 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**.
+    
+    **msbuild /t:clean /t:build .\\<*samplename*>.vcxproj**.
 
 Installation and Operation
 --------------------------
@@ -50,7 +50,7 @@ The following annotated DSM INF file illustrates the correct format for your DSM
 ;
 ```
 
-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:
+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]
@@ -96,7 +96,7 @@ 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).
 
-**Note**   Underscores that are part of the inquiry string (applies to vendor ID as well as product ID fields) must NOT be replaced with spaces.
+**Note** Underscores that are part of the inquiry string (applies to vendor ID as well as product ID fields) must NOT be replaced with spaces.
 
 In this sample, there are two different strings:
 
@@ -199,7 +199,7 @@ You should be aware of the following when you install the MPIO DSM sample:
 
 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.
+**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.
 
-**Note**  Since your DSM binary is not signed, you will get Unsigned Driver Pop-Ups. Ignore these and accept the installation of the new driver. Once your package has been successfully qualified by WHQL, your binaries will get signed and your customers will not get unsigned driver popups.
+**Note** Since your DSM binary is not signed, you will get Unsigned Driver Pop-Ups. Ignore these and accept the installation of the new driver. Once your package has been successfully qualified by WHQL, your binaries will get signed and your customers will not get unsigned driver popups.
 
diff --git a/storage/ramdisk/ReadMe.md b/storage/ramdisk/ReadMe.md
index 1ef67580..66e97691 100644
--- a/storage/ramdisk/ReadMe.md
+++ b/storage/ramdisk/ReadMe.md
@@ -8,11 +8,11 @@ Build the sample
 
 ### Open the driver solution in Visual Studio ###
 
-Navigate to the folder that has the extracted sample. Double click the solution file, ramdisk.sln. In Microsoft Visual Studio, locate Solution Explorer. (If this is not already open, choose **Solution Explorer** from the **View** menu.) In Solution Explorer, you can see one solution that has two projects. There is a driver project named **WdfRamdisk** and a package project named **package** (lower case).
+In Visual Studio, open the solution file, ramdisk.sln, and locate Solution Explorer (if this is not already open, choose **Solution Explorer** from the **View** menu). In Solution Explorer, you can see one solution that has two projects. There is a driver project named **WdfRamdisk** and a package project named **package** (lower case).
 
 ### Set the configuration and platform in Visual Studio
 
-In Visual Studio, in Solution Explorer, right click **Solution ‘ramdisk’ (2 projects)**, and choose **Configuration Manager**. Set the configuration and the platform. Make sure that the configuration and platform are the same for both the driver project and the package project. Do not check the **Deploy** boxes. Here are some examples of configuration and platform settings.
+In Visual Studio, in Solution Explorer, right click **Solution 'ramdisk'(2 projects)**, and choose **Configuration Manager**. Set the configuration and the platform. Make sure that the configuration and platform are the same for both the driver project and the package project. Do not check the **Deploy** boxes. Here are some examples of configuration and platform settings.
 
 ### Build the sample using Visual Studio ###