Update README.md

7 files changed, 10 insertions, 12 deletions

diff --git a/print/XPSDrvSmpl/ReadMe.md b/print/XPSDrvSmpl/ReadMe.md
index bbf1948b..f90ae5cf 100644
--- a/print/XPSDrvSmpl/ReadMe.md
+++ b/print/XPSDrvSmpl/ReadMe.md
@@ -25,7 +25,7 @@ To build a driver solution using Windows Driver Kit (WDK) 10 and Visual Studio 2
   a. In the **Solution Explorer**, right click on the solution and choose **Add** > **New Project**. Choose **Driver Install Package** under Visual C++/Windows Driver/Package.
   b. In the **Solution Explorer**, right click the Package project and select **Properties**.
   c. In the left pane, click **Configuration Properties** \> **Driver Install** \> **Package Files**.
-  d. In the right pane, use the ellipsis button (...) to browse to the set of files that needs to be added to the driver package. All the data files that you added in **Step 2-c**, except the INF file, should be added.  This configuration is per-architecture, so this configuration must be repeated for each architecture that will be built.
+  d. In the right pane, use the ellipsis button (...) to browse to the set of files that needs to be added to the driver package. All the data files that you added in **Step 2-c**, except the INF file, should be added. This configuration is per-architecture, so this configuration must be repeated for each architecture that will be built.
   e. Click **OK**.
 4. Open the INF file and edit it to match the built output.
   a. Open the INF file.
@@ -34,7 +34,7 @@ To build a driver solution using Windows Driver Kit (WDK) 10 and Visual Studio 2
 
 At this point, Visual Studio 2015 will be able to build a driver package and output the files to disk. In order to configure driver signing and deployment, see [Developing, Testing, and Deploying Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554651(v=vs.85).aspx).
 
-**Note**  If you compile your sample driver with Microsoft Visual Studio version 10, or 11 with the \_DEBUG flag set, then you should not use CComVariant on the following two XPS Print Filter Pipeline properties:
+**Note** If you compile your sample driver with Microsoft Visual Studio version 10, or 11 with the \_DEBUG flag set, then you should not use CComVariant on the following two XPS Print Filter Pipeline properties:
 
 -   XPS\_FP\_USER\_TOKEN
 -   XPS\_FP\_PRINTER\_HANDLE
diff --git a/print/autoconfig/ReadMe.md b/print/autoconfig/ReadMe.md
index 821e1897..72f10042 100644
--- a/print/autoconfig/ReadMe.md
+++ b/print/autoconfig/ReadMe.md
@@ -27,7 +27,7 @@ But to build a signed driver package using Windows Driver Kit (WDK) 10 and Visua
 
 3. In **Configuration Manager**, select the **Configuration** and **Platform** that you want to build your driver for.
 
-**Note**  When the driver builds, it will be placed in the output folder for the architecture you selected.
+**Note** When the driver builds, it will be placed in the output folder for the architecture you selected.
 
 At this point, Visual Studio will be able to build a driver package and output the files to disk. In order to configure driver signing and deployment, see [Developing, Testing, and Deploying Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554651(v=vs.85).aspx).
 
diff --git a/print/v4PrintDriverSamples/PrinterExtensionSample/ReadMe.md b/print/v4PrintDriverSamples/PrinterExtensionSample/ReadMe.md
index e7ab1d25..ca5f6837 100644
--- a/print/v4PrintDriverSamples/PrinterExtensionSample/ReadMe.md
+++ b/print/v4PrintDriverSamples/PrinterExtensionSample/ReadMe.md
@@ -3,7 +3,7 @@ Printer Extension Sample
 
 This sample demonstrates how to use .NET to build a customized, desktop UI for a v4 print driver. This .NET app uses PrintTicket, PrintCapabilities and Bidi in order to communicate with the print system and is suitable for inclusion in a v4 print driver.
 
-**Note**  This sample is for the v4 print driver model.
+**Note** This sample is for the v4 print driver model.
 
 Related topics
 --------------
diff --git a/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/ReadMe.md b/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/ReadMe.md
index 60c78353..71a6f72b 100644
--- a/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/ReadMe.md
+++ b/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/ReadMe.md
@@ -10,7 +10,7 @@ The Constraints.js file in this sample demonstrates the implementation of JavaSc
 
 This sample does not demonstrate **ConvertPrintTicketToDevMode** or **ConvertDevModeToPrintTicket**, which utilize a property bag to store data in the private section of the DEVMODE structure.
 
-**Note**  This sample is for the v4 print driver model.
+**Note** This sample is for the v4 print driver model.
 
 Related topics
 --------------
diff --git a/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/ReadMe.md b/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/ReadMe.md
index 4a438be7..6d3b77d0 100644
--- a/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/ReadMe.md
+++ b/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/ReadMe.md
@@ -3,7 +3,7 @@ USB Host-Based Print Driver Sample
 
 This driver sample demonstrates how to support host-based devices that use the v4 print driver model, and are connected via USB.
 
-**Note**  This sample is for the v4 print driver model.
+**Note** This sample is for the v4 print driver model.
 
 Windows enables manufacturers to support Bidirectional Communication (Bidi) for USB devices, by using a combination of both a Bidi XML file and a Javascript file known as a USB Bidi extender. The *usb\_host\_based\_sample.js* file that is included with the sample, plays the role of the USB Bidi extender.
 
diff --git a/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/ReadMe.md b/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/ReadMe.md
index 753af28b..2f7ec05d 100644
--- a/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/ReadMe.md
+++ b/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/ReadMe.md
@@ -10,9 +10,9 @@ The following files are included in the sample:
 
 For more information, see [USB Bidi Extender](http://msdn.microsoft.com/en-us/library/windows/hardware/jj659903(v=vs.85).aspx).
 
-**Note**  This sample is for the v4 print driver model.
+**Note** This sample is for the v4 print driver model.
 
-**Note**  When you make calls to printerStream.read() in the sample, the printer returns an array which includes an additional element that represents the array length. The following JavaScript code can be used to copy the returned array into a new array, and also to remove the additional element.
+**Note** When you make calls to printerStream.read() in the sample, the printer returns an array which includes an additional element that represents the array length. The following JavaScript code can be used to copy the returned array into a new array, and also to remove the additional element.
 
 ```
 var readBuffer = [];
diff --git a/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/ReadMe.md b/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/ReadMe.md
index 514015d7..6556ab25 100644
--- a/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/ReadMe.md
+++ b/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/ReadMe.md
@@ -5,9 +5,7 @@ This sample demonstrates how to use an XML extension file to support bidirection
 
 The v4 print driver model continues to employ the WSDMon Bidi Extension file format, as well as the SNMP Bidi Extension file format.
 
-**Note**  
-
-Third-party port monitors and language monitors are not supported in the v4 driver model or with print class drivers.
+**Note** Third-party port monitors and language monitors are not supported in the v4 driver model or with print class drivers.
 
 The WSDMON port monitor is a printer port monitor that supports printing to network printers that comply with the Web Services for Devices (WSD) technology. The WSDMON port monitor listens for WSD events and updates the printer status accordingly.
 
@@ -41,7 +39,7 @@ WSDMON supports the following Xcv commands:
 
 -   ServiceID
 
-**Note**  This sample is for the v4 print driver model.
+**Note** This sample is for the v4 print driver model.
 
 For more information, see [V4 Driver Connectivity Architecture](http://msdn.microsoft.com/en-us/library/windows/hardware/) and [Bidirectional Communication Schema](http://msdn.microsoft.com/en-us/library/windows/hardware/ff545169(v=vs.85).aspx).