Update manifests

13 files changed, 12 insertions, 17 deletions

diff --git a/usb/UcmCxUcsi/README.md b/usb/UcmCxUcsi/README.md
index c9d64f14..aec7f7f1 100644
--- a/usb/UcmCxUcsi/README.md
+++ b/usb/UcmCxUcsi/README.md
@@ -68,4 +68,4 @@ The remainder of the files perform operations for UCSI and WDF, non-specific to
 
 ## When to write a UcmCx client driver
 
-UcmCx is intended for system port controller drivers. If you are bringing up a USB Type-C peripheral, you do not need to write a USB Type-C specific driver; a regular USB client driver will suffice. Refer to [Developing Windows client drivers for USB devices](https://msdn.microsoft.com/en-us/library/windows/hardware/hh406260(v=vs.85).aspx) to determine what type of driver, if any, you need to write to make your USB device work with Windows. You may look at [Do I need to write a driver for my USB Type-C hardware?](https://blogs.msdn.microsoft.com/usbcoreblog/2016/06/20/do-i-need-to-write-a-driver-for-my-usb-type-c-hardware/) for a more detailed overview.
+UcmCx is intended for system port controller drivers. If you are bringing up a USB Type-C peripheral, you do not need to write a USB Type-C specific driver; a regular USB client driver will suffice. Refer to [Developing Windows client drivers for USB devices](https://msdn.microsoft.com/en-us/library/windows/hardware/hh406260(v=vs.85).aspx) to determine what type of driver, if any, you need to write to make your USB device work with Windows. You may look at [Do I need to write a driver for my USB Type-C hardware?](https://blogs.msdn.microsoft.com/usbcoreblog/2016/06/20/do-i-need-to-write-a-driver-for-my-usb-type-c-hardware/) for a more detailed overview.
\ No newline at end of file
diff --git a/usb/UcmTcpciCxClientSample/README.md b/usb/UcmTcpciCxClientSample/README.md
index 2dfab641..5919ee07 100644
--- a/usb/UcmTcpciCxClientSample/README.md
+++ b/usb/UcmTcpciCxClientSample/README.md
@@ -219,4 +219,4 @@ Microsoft USB Test Tools
 
 Tracelog Command Syntax
 
-<https://msdn.microsoft.com/en-us/library/windows/hardware/ff553012(v=vs.85).aspx>
+<https://msdn.microsoft.com/en-us/library/windows/hardware/ff553012(v=vs.85).aspx>
\ No newline at end of file
diff --git a/usb/UcmUcsiAcpiSample/README.md b/usb/UcmUcsiAcpiSample/README.md
index f2ac668b..fc163389 100644
--- a/usb/UcmUcsiAcpiSample/README.md
+++ b/usb/UcmUcsiAcpiSample/README.md
@@ -61,4 +61,4 @@ The remainder of the files perform operations for UCSI and WDF, non-specific to
 
 ## When to write a UcmUcsiCx client driver
 
-UcmUcsiCx is intended to abstract UCSI protocol from UCSI based driver support. If you have a system that implements PPM logic in an Embedded controller which is connected to the system over a non ACPI transport - e.g. USB, PCI, I2C or UART, it is advised that you write a UcmUcsiCx client driver that implements the necessary transport. Ideally, you would just need to replace Acpi class and implement your way to talk to the PPM. Please note, UcmUcsiCx client is the power policy owner. The class extension does handle S0 idling if you chose to enable it in the client driver.
+UcmUcsiCx is intended to abstract UCSI protocol from UCSI based driver support. If you have a system that implements PPM logic in an Embedded controller which is connected to the system over a non ACPI transport - e.g. USB, PCI, I2C or UART, it is advised that you write a UcmUcsiCx client driver that implements the necessary transport. Ideally, you would just need to replace Acpi class and implement your way to talk to the PPM. Please note, UcmUcsiCx client is the power policy owner. The class extension does handle S0 idling if you chose to enable it in the client driver.
\ No newline at end of file
diff --git a/usb/kmdf_enumswitches/README.md b/usb/kmdf_enumswitches/README.md
index c22cfa8f..1d4e0319 100644
--- a/usb/kmdf_enumswitches/README.md
+++ b/usb/kmdf_enumswitches/README.md
@@ -58,4 +58,4 @@ Here is the overview of the device:
 - Device moves data from IN endpoint to OUT endpoint.
   - Device does not change the values of the data it receives nor does it internally create any data.
   - Endpoints are always double buffered.
-  - Maximum packet size depends on speed (64 Full speed, 512 High speed).
+  - Maximum packet size depends on speed (64 Full speed, 512 High speed).
\ No newline at end of file
diff --git a/usb/kmdf_fx2/README.md b/usb/kmdf_fx2/README.md
index f2c90029..a31a908d 100644
--- a/usb/kmdf_fx2/README.md
+++ b/usb/kmdf_fx2/README.md
@@ -383,5 +383,3 @@ To trace, you can use the in-box tools, logman and tracerpt, or download XPerf (
 4.  View the trace file using Xperf:
 
     `xperfview OSRUSBFX2.etl`
-
-
diff --git a/usb/ufxclientsample/README.md b/usb/ufxclientsample/README.md
index 7d8b65f0..3197795f 100644
--- a/usb/ufxclientsample/README.md
+++ b/usb/ufxclientsample/README.md
@@ -39,4 +39,4 @@ This sample is not a functional driver. It is a skeleton driver intended to illu
 
 ## Installation Note
 
-Installation on Windows 10 Mobile requires the creation of a package.  To properly interact with the USB UI on Windows 10 Mobile, the package must include a Security Element that specifies the ID_CAP_USB capability with DEVICE_READ and DEVICE_WRITE rights.
+Installation on Windows 10 Mobile requires the creation of a package.  To properly interact with the USB UI on Windows 10 Mobile, the package must include a Security Element that specifies the ID_CAP_USB capability with DEVICE_READ and DEVICE_WRITE rights.
\ No newline at end of file
diff --git a/usb/umdf2_fx2/README.md b/usb/umdf2_fx2/README.md
index 4a486fd0..ce1742cd 100644
--- a/usb/umdf2_fx2/README.md
+++ b/usb/umdf2_fx2/README.md
@@ -67,4 +67,4 @@ As an alternative to building the driver sample in Visual Studio, you can build
 
     **msbuild /p:configuration=Win8 Release /p:platform=Win32 umdf2\_fx2.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).
+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).
\ No newline at end of file
diff --git a/usb/umdf_filter_kmdf/README.md b/usb/umdf_filter_kmdf/README.md
index a5a8af0d..e938c44a 100644
--- a/usb/umdf_filter_kmdf/README.md
+++ b/usb/umdf_filter_kmdf/README.md
@@ -64,4 +64,4 @@ You can test this sample either by using the [Custom driver access](http://go.mi
 | Folder | Description |
 | --- | --- |
 | usb\umdf_filter_kmdf\kmdf_driver | This directory contains source code for the kmdf_fx2 sample driver. |
-| usb\umdf_filter_kmdf\umdf_filter | This directory contains the UMDF filter driver. |
\ No newline at end of file
+| usb\umdf_filter_kmdf\umdf_filter | This directory contains the UMDF filter driver. |
diff --git a/usb/umdf_filter_umdf/README.md b/usb/umdf_filter_umdf/README.md
index ace83811..f9db0a44 100644
--- a/usb/umdf_filter_umdf/README.md
+++ b/usb/umdf_filter_umdf/README.md
@@ -48,4 +48,4 @@ You can test this sample either by using the [Custom driver access](http://go.mi
 | Folder | Description |
 | --- | --- |
 | usb\umdf_filter_umdf\umdf_driver | This directory contains source code for the umdf_fx2 sample driver. |
-| usb\umdf_filter_umdf\umdf_filter | This directory contains the UMDF filter driver. |
+| usb\umdf_filter_umdf\umdf_filter | This directory contains the UMDF filter driver. |
\ No newline at end of file
diff --git a/usb/umdf_fx2/README.md b/usb/umdf_fx2/README.md
index 0b57018e..89c7cadf 100644
--- a/usb/umdf_fx2/README.md
+++ b/usb/umdf_fx2/README.md
@@ -341,5 +341,4 @@ This directory contains a test application that can be used to drive the UMDF dr
 
 usb\\umdf\_fx2\\deviceMetadata
 
-This directory contains the device metadata package for the sample. You must copy the device metadata to the system before installing the device. For information on how to update and deploy device metadata, see [Custom driver access sample](http://go.microsoft.com/fwlink/p/?LinkID=248288).
-
+This directory contains the device metadata package for the sample. You must copy the device metadata to the system before installing the device. For information on how to update and deploy device metadata, see [Custom driver access sample](http://go.microsoft.com/fwlink/p/?LinkID=248288).
\ No newline at end of file
diff --git a/usb/usbsamp/README.md b/usb/usbsamp/README.md
index b9d13ad8..54a9f860 100644
--- a/usb/usbsamp/README.md
+++ b/usb/usbsamp/README.md
@@ -151,4 +151,4 @@ The sample includes a test application, usbsamp.exe. This console application en
 
 - To skip validation of the data to be read or written in a particular request, use the command with **-x** option as follows:
 
-    **usbsamp.exe -r 1024 -w 1024 -c 100 -x**
+    **usbsamp.exe -r 1024 -w 1024 -c 100 -x**
\ No newline at end of file
diff --git a/usb/usbview/README.md b/usb/usbview/README.md
index 688800bc..5e06c913 100644
--- a/usb/usbview/README.md
+++ b/usb/usbview/README.md
@@ -86,4 +86,4 @@ The file Enum.c contains the routines that enumerate the USB bus and populate th
 1. Enumerate Hubs (Root Hubs and External Hubs). Given the name of a hub, use CreateFile() to open the hub. Send the hub an IOCTL\_USB\_GET\_NODE\_INFORMATION request to get info about the hub, such as the number of downstream ports. Create a node in the tree view to represent each hub.
 1. Enumerate Downstream Ports. Given a handle to an open hub and the number of downstream ports on the hub, send the hub an IOCTL\_USB\_GET\_NODE\_CONNECTION\_INFORMATION request for each downstream port of the hub to get info about the device (if any) attached to each port. If there is a device attached to a port, send the hub an IOCTL\_USB\_GET\_NODE\_CONNECTION\_NAME request to get the symbolic link name of the hub attached to the downstream port. If there is a hub attached to the downstream port, recurse to step (2). Create a node in the tree view to represent each hub port and attached device. USB configuration and string descriptors are retrieved from attached devices in GetConfigDescriptor() and GetStringDescriptor() by sending an IOCTL\_USB\_GET\_DESCRIPTOR\_FROM\_NODE\_CONNECTION() to the hub to which the device is attached.
 
-The file Display.c contains routines that display information about selected devices in the application edit control. Information about the device was collected during the enumeration of the device tree. This information includes USB device, configuration, and string descriptors and connection and configuration information that is maintained by the USB stack. The routines in this file simply parse and print the data structures for the device that were collected when it was enumerated. The file Dispaud.c parses and prints data structures that are specific to USB audio class devices.
+The file Display.c contains routines that display information about selected devices in the application edit control. Information about the device was collected during the enumeration of the device tree. This information includes USB device, configuration, and string descriptors and connection and configuration information that is maintained by the USB stack. The routines in this file simply parse and print the data structures for the device that were collected when it was enumerated. The file Dispaud.c parses and prints data structures that are specific to USB audio class devices.
\ No newline at end of file
diff --git a/usb/wdf_osrfx2_lab/README.md b/usb/wdf_osrfx2_lab/README.md
index 5455a8c7..e244b09b 100644
--- a/usb/wdf_osrfx2_lab/README.md
+++ b/usb/wdf_osrfx2_lab/README.md
@@ -382,6 +382,4 @@ The most basic step. The source file contains a minimal amount of code to get th
 </ol></td>
 </tr>
 </tbody>
-</table>
-
-
+</table>
\ No newline at end of file