Update README.md

5 files changed, 12 insertions, 14 deletions

diff --git a/general/echo/umdf/ReadMe.md b/general/echo/umdf/ReadMe.md
index 75ae46cd..e2123cd3 100644
--- a/general/echo/umdf/ReadMe.md
+++ b/general/echo/umdf/ReadMe.md
@@ -16,7 +16,7 @@ Related technologies
 Testing
 -------
 
-To test the Echo driver, you can run echoapp.exe which is built from src\\general\\echo\\exe.
+To test the Echo driver, you can run echoapp.exe which is built from \\echo\\exe.
 
 First install the device as described above. Then run echoapp.exe.
 
diff --git a/general/echo/umdfSocketEcho/ReadMe.md b/general/echo/umdfSocketEcho/ReadMe.md
index 8015044b..06819a47 100644
--- a/general/echo/umdfSocketEcho/ReadMe.md
+++ b/general/echo/umdfSocketEcho/ReadMe.md
@@ -61,7 +61,7 @@ To test this sample drivers on a checked operating system that you have installe
 Testing
 -------
 
-To test the SocketEcho driver, you can run socketechoserver.exe, which is built from the src\\general\\echo\\umdfSocketEcho\\Exe directory, and echoapp.exe, which is built from the Kernel-Mode Driver Framework (KMDF) samples in the src\\general\\echo\\kmdf directory.
+To test the SocketEcho driver, you can run socketechoserver.exe, which is built from the \\echo\\umdfSocketEcho\\Exe directory, and echoapp.exe, which is built from the Kernel-Mode Driver Framework (KMDF) samples in the \\echo\\kmdf directory.
 
 First, you must install the device as described earlier. Then, run socketechoserver.exe from a Command Prompt window.
 
diff --git a/general/ioctl/kmdf/ReadMe.md b/general/ioctl/kmdf/ReadMe.md
index 848acd06..c9a10365 100644
--- a/general/ioctl/kmdf/ReadMe.md
+++ b/general/ioctl/kmdf/ReadMe.md
@@ -23,8 +23,6 @@ This sample would be useful for writing a driver that does not interact with any
 
 The sample is accompanied by a simple multithreaded Win32 console application to test the driver.
 
-This sample is adapted from the original IOCTL sample present in WDK (src\\general\\ioctl).
-
 *Disclaimer*: This is a minimal driver meant to demonstrate an OS feature. Neither it nor its sample programs are intended for use in a production environment. Rather, they are intended for educational purposes and as a skeleton driver.
 
 
diff --git a/general/obcallback/ReadMe.md b/general/obcallback/ReadMe.md
index d91a209d..ca4069a2 100644
--- a/general/obcallback/ReadMe.md
+++ b/general/obcallback/ReadMe.md
@@ -14,18 +14,18 @@ The following is a command line usage scenario to exercise access restriction:
 ```
 C:\> obcallbacktestctrl.exe  -?                      (for command line help)
 C:\> obcallbacktestctrl.exe  -install                (installs the kernel driver)
-C:\> obcallbacktestctrl.exe  -name  notepad          (specifies that the string “notepad”  will be watched as a protected executable)
-                                                     (now you can start up  “notepad.exe”)
+C:\> obcallbacktestctrl.exe  -name  notepad          (specifies that the string "notepad"  will be watched as a protected executable)
+                                                     (now you can start up "notepad.exe")
 C:\> notepad
 
 C:\> tlist                                           (locate the process ID of notepad.exe)
 
 C:\> kill -f  2329                                   (attempt to kill off the notepad.exe with a PID of 2329)
-process notepad.exe (2329) - 'Untitled – Notepad' could not be killed
+process notepad.exe (2329) - 'Untitled - Notepad' could not be killed
 
 C:\> obcallbacktestctrl.exe  -deprotect              (remove the protections on the notepad process)
 
-C:\> kill -f  2329                                   (attempt to kill off the process – which will succeed)
+C:\> kill -f  2329                                   (attempt to kill off the process - which will succeed)
 C:\> obcallbacktestctrl.exe  -uninstall              (uninstall the kernel driver)
 ```
 
@@ -33,8 +33,8 @@ The following is another sample test you can run to prevent a process from being
 
 ```
 C:\> obcallbacktestctrl.exe  -install                (installs the kernel driver)
-C:\> obcallbacktestctrl.exe  -reject  notepad        (specifies that the string “notepad”  will be watched and prevented from starting as a process)
+C:\> obcallbacktestctrl.exe  -reject  notepad        (specifies that the string "notepad"  will be watched and prevented from starting as a process)
 
-C:\> notepad                                         (now you can start up  “notepad.exe”)
+C:\> notepad                                         (now you can start up "notepad.exe")
 Access is denied.
 ```
diff --git a/general/pcidrv/ReadMe.md b/general/pcidrv/ReadMe.md
index fcd56df2..04bf35b5 100644
--- a/general/pcidrv/ReadMe.md
+++ b/general/pcidrv/ReadMe.md
@@ -37,15 +37,15 @@ The following is a list of key KMDF interfaces demonstrated in this sample:
 
 Note: This sample provides an example of a minimal driver intended for educational purposes. Neither the driver nor its sample test programs are intended for use in a production environment.
 
-As stated earlier, this sample is meant to demonstrate how to write a KMDF driver for a generic PCI device and not for PCI network controllers. For network controllers, you should write a monolithic NDIS miniport driver based on the samples given under the src\\network\\ndis directory.
+As stated earlier, this sample is meant to demonstrate how to write a KMDF driver for a generic PCI device and not for PCI network controllers. For network controllers, you should write a monolithic NDIS miniport driver based on the samples given under the \\network\\ndis directory.
 
-Note that it is still possible to use a subset of KMDF APIs when writing a NDIS miniport (see src\\network\\ndis\\usbnwifi directory for a sample on how to use KMDF interfaces to talk to USB device in an NDIS miniport).
+Note that it is still possible to use a subset of KMDF APIs when writing a NDIS miniport (see \\network\\ndis\\usbnwifi directory for a sample on how to use KMDF interfaces to talk to USB device in an NDIS miniport).
 
 The sample driver has been tested on the following Intel Ethernet controllers:
 
 Device Description | Hardware ID
 -------------------|------------
-IBM Netfinity 10/100 Ethernet Adapter |  PCIVEN_8086&DEV_1229&SUBSYS_005C1014&REV_05
+IBM Netfinity 10/100 Ethernet Adapter |  PCIVEN_8086&DEV_1229&SUBSYS_005C1014&REV_05
 Intel(R) PRO/100+ Management Adapter with Alert On LAN | PCI\VEN_8086&DEV_1229&SUBSYS_000E8086&REV_08
 Intel 8255x-based PCI Ethernet Adapter (10/100) | PCI\VEN_8086&DEV_1229&SUBSYS_00000000&REV_01
 Intel Pro/100 S Server Adapter | PCI\VEN_8086&DEV_1229&SUBSYS_00508086&REV_0D
@@ -91,7 +91,7 @@ The PCIDRV sample acts as a power policy owner of the device and implements all
 INSTALLATION
 ------------
 
-The driver can be installed as a Net class driver or as a standalone driver (user defined class). The KMDF versions of the INF files are dynamically generated from .INX file. In addition to the driver files, you have to include the WDF coinstaller DLL from the src\\redist\\wdf folder of the WDK.
+The driver can be installed as a Net class driver or as a standalone driver (user defined class). The KMDF versions of the INF files are dynamically generated from .INX file. In addition to the driver files, you have to include the WDF coinstaller DLL from the \\redist\\wdf folder of the WDK.
 
 You can obtain redistributable framework updates by downloading the *wdfcoinstaller.msi* package from [WDK 8 Redistributable Components](http://go.microsoft.com/fwlink/p/?LinkID=226396). This package performs a silent install into the directory of your Windows Driver Kit (WDK) installation. You will see no confirmation that the installation has completed. You can verify that the redistributables have been installed on top of the WDK by ensuring there is a redist\\wdf directory under the root directory of the WDK, %ProgramFiles(x86)%\\Windows Kits\\8.0.