Update README.md

3 files changed, 9 insertions, 10 deletions

diff --git a/usb/kmdf_fx2/ReadMe.md b/usb/kmdf_fx2/ReadMe.md
index b58a2a01..81edf40a 100644
--- a/usb/kmdf_fx2/ReadMe.md
+++ b/usb/kmdf_fx2/ReadMe.md
@@ -366,7 +366,7 @@ To trace, you can use the in-box tools, logman and tracerpt, or download XPerf (
 
     `logman start sample -o osrusbfx2.etl -ets -p OSRUSBFX2`
 
-2.  Generate activity through the osrusbfx2 test application, such as `osrusbfx2.exe –a`.
+2.  Generate activity through the osrusbfx2 test application, such as `osrusbfx2.exe -a`.
 3.  Stop tracing by using the following command:
 
     `Logman stop sample`
@@ -381,7 +381,7 @@ To trace, you can use the in-box tools, logman and tracerpt, or download XPerf (
 
     `xperf -start sample -f osrusbfx2.etl -on OSRUSBFX2`
 
-2.  Generate activity through the osrusbfx2 test application, such as `osrusbfx2.exe –a`.
+2.  Generate activity through the osrusbfx2 test application, such as `osrusbfx2.exe -a`.
 3.  Stop tracing by using the following command:
 
     `xperf -stop sample`
diff --git a/usb/usbsamp/ReadMe.md b/usb/usbsamp/ReadMe.md
index 5519d726..c7a20320 100644
--- a/usb/usbsamp/ReadMe.md
+++ b/usb/usbsamp/ReadMe.md
@@ -10,7 +10,8 @@ For information about USB, see [Universal Serial Bus (USB) Drivers](http://msdn.
 ## Universal Windows Driver Compliant
 This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP.
 
-**Hardware requirements**
+Hardware requirements
+---------------------
 
 The sample driver can be loaded as the function driver for any of these devices:
 
@@ -52,8 +53,7 @@ The computer where you install the driver is called the *target computer* or the
 
 The process of moving the driver package to the target computer and installing the driver is called *deploying the driver*. You can deploy the USBSAMP sample automatically or manually.
 
-Automatic deployment
---------------------
+### Automatic deployment
 
 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/).
 
@@ -61,8 +61,7 @@ Before you automatically deploy a driver, you must provision the target computer
 2.  Check **Enable deployment**, and check **Remove previous driver versions before deployment**. For **Target Computer Name**, select the name of a target computer that you provisioned previously. Select **Install and Verify**. Click **OK**.
 3.  On the **Build** menu, choose **Deploy Package** or **Build Solution**.
 
-Manual deployment
------------------
+### Manual deployment
 
 Before you manually deploy a driver, you must turn on test signing and install a certificate on the target computer. You also need to copy the [DevCon](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544707) tool to the target computer. For instructions, see [Preparing a Computer for Manual Driver Deployment](http://msdn.microsoft.com/en-us/library/windows/hardware/dn265571).
 
@@ -81,9 +80,9 @@ Build the sample using MSBuild
 
 As an alternative to building the USBSAMP sample in Visual Studio, you can build it in a Visual Studio Command Prompt window. In Visual Studio, on the **Tools** menu, choose **Visual Studio Command Prompt**. In the Visual Studio Command Prompt window, navigate to the folder that has the solution file, Usbsamp.sln. Use the MSBuild command to build the solution. Here are some examples:
 
-**msbuild /p:configuration=”Win7 Debug” /p:platform=”x64” Usbsamp.sln**
+**msbuild /p:configuration="Debug" /p:platform="x64" Usbsamp.sln**
 
-**msbuild /p:configuration=”Win8 Release” /p:platform=”Win32” Usbsamp.sln**
+**msbuild /p:configuration="Release" /p:platform="Win32" Usbsamp.sln**
 
 For more information about using MSBuild to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644).
 
diff --git a/usb/usbview/ReadMe.md b/usb/usbview/ReadMe.md
index b627f091..cd117f82 100644
--- a/usb/usbview/ReadMe.md
+++ b/usb/usbview/ReadMe.md
@@ -3,7 +3,7 @@ USBView sample application
 
 Usbview.exe is a Windows GUI application that allows you to browse all USB controllers and connected USB devices on your system. The left pane in the main application window displays a connection-oriented tree view, and the right pane displays the USB data structures pertaining to the selected USB device, such as the Device, Configuration, Interface, and Endpoint Descriptors, as well as the current device configuration.
 
-**Important**  If you need UsbView as a tool, do not download this sample. Instead get UsbView.exe from the [Windows Driver Kit (WDK)](http://go.microsoft.com/fwlink/p?linkid=391063) in the Windows Kits\\*\<version\>*\\Tools\\*\<arch\>* folder. If you need to see the source code for UsbView, open the **Browse code** tab.
+**Important** If you need UsbView as a tool, do not download this sample. Instead get UsbView.exe from the [Windows Driver Kit (WDK)](http://go.microsoft.com/fwlink/p?linkid=391063) in the Windows Kits\\*\<version\>*\\Tools\\*\<arch\>* folder. If you need to see the source code for UsbView, open the **Browse code** tab.
 
 This functional application sample demonstrates how a user-mode application can enumerate USB host controllers, USB hubs, and attached USB devices, and query information about the devices from the registry and through USB requests to the devices.