Testing onboarding more samples

audio/sysvad/README.md

@@ -165,4 +165,4 @@ On the target computer, in a Command Prompt window, enter **devmgmt** to open De
 
 On the target computer, open Control Panel and navigate to **Hardware and Sound** \> **Manage audio devices**. In the Sound dialog box, select the speaker icon labeled as *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample*, then click **Set Default**, but do not click **OK**. This will keep the Sound dialog box open.
 
-Locate an MP3 or other audio file on the target computer and double-click to play it. Then in the Sound dialog box, verify that there is activity in the volume level indicator associated with the *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample* driver.
+Locate an MP3 or other audio file on the target computer and double-click to play it. Then in the Sound dialog box, verify that there is activity in the volume level indicator associated with the *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample* driver.

avstream/avscamera/README.md

@@ -31,4 +31,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a
 
 ## Building the sample
 
-The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.
+The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.

avstream/avscamera/mft0/README.md

@@ -30,4 +30,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a
 
 ## Building the sample
 
-The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.
+The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.

avstream/avshws/README.md

@@ -90,4 +90,4 @@ Code tour
 File | Description
 -----|------------
 Avshws.h | Main header file for the sample
-Avshws.inf | Sample installation file
+Avshws.inf | Sample installation file

avstream/avssamp/README.md

@@ -63,4 +63,4 @@ Purecall.h | _purecall stub necessary for virtual function usage in drivers.
 Video.cpp | Video capture pin implementation.
 Video.h | Video capture pin header.
 Wave.cpp | Wave object implementation
-Wave.h | Wave object header
+Wave.h | Wave object header

avstream/sampledevicemft/README.md

@@ -43,4 +43,4 @@ Related topics
 
 [Device app for camera sample](http://go.microsoft.com/fwlink/p/?linkid=249442)
 
-[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)
+[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)

avstream/samplemft0/README.md

@@ -41,4 +41,4 @@ Related topics
 
 [Device app for camera sample](http://go.microsoft.com/fwlink/p/?linkid=249442)
 
-[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)
+[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)

biometrics/README.md

@@ -90,4 +90,4 @@ WinBio Adapters are plug-in components that provide a standard interface layer b
 
 For many simple biometric devices, it will only be necessary to write a WBDI driver for the device plus an Engine Adapter to perform matching operations. Consult the programming guidelines in the WinBio Service documentation for more details.
 
-Each Adapter sample contains a well-known interface-discovery function, whose job is to return the address of a function dispatch table. When the WinBio Service loads an Adapter plug-in, it uses the interface-discovery function to locate the dispatch table, and then calls various methods in the table to communicate with the biometric device. The purpose, arguments, and return codes of each Adapter method are described in the WinBio Service programming guidelines. More information on adapter plug-ins is available at [WBDI Plug-in Reference](https://docs.microsoft.com/windows/desktop/SecBioMet/plug-in-reference).
+Each Adapter sample contains a well-known interface-discovery function, whose job is to return the address of a function dispatch table. When the WinBio Service loads an Adapter plug-in, it uses the interface-discovery function to locate the dispatch table, and then calls various methods in the table to communicate with the biometric device. The purpose, arguments, and return codes of each Adapter method are described in the WinBio Service programming guidelines. More information on adapter plug-ins is available at [WBDI Plug-in Reference](https://docs.microsoft.com/windows/desktop/SecBioMet/plug-in-reference).

bluetooth/bthecho/bthsrv/README.md

@@ -225,4 +225,4 @@ One transition to note here is that if disconnect is received in the connecting
 
 **Sending and receiving data from server**: When application writes data to the client, client sends this data to server on the connection opened for the given handle. Server would echo back this data. This data is retrieved by the application using a read operation. Echo Sample Client doesn't do any draining of echoed data on its own. Application read/write are handled using a parallel WDF I/O queue.
 
-**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open.
+**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open.

bluetooth/serialhcibus/README.md

@@ -74,4 +74,4 @@ device.h - header file for device.c
 
 driver.rc - driver version and name
 
-SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name.
+SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name.