Update README.md

2 files changed, 3 insertions, 3 deletions

diff --git a/general/tracing/evntdrv/ReadMe.md b/general/tracing/evntdrv/ReadMe.md
index a560a0a4..4e64ecae 100644
--- a/general/tracing/evntdrv/ReadMe.md
+++ b/general/tracing/evntdrv/ReadMe.md
@@ -5,7 +5,7 @@ Eventdrv is a sample kernel-mode trace provider and driver. The driver does not
 
 Evntdrv registers as a provider by calling the [**EtwRegister**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff545603) API. If the registration is successful, it logs a StartEvent with the device's name, the length of the name, and the status code. Then, when the sample receives a DeviceIOControl call, it logs a SampleEventA event. Finally, when the driver gets unloaded, it logs an UnloadEvent event with a pointer to the device object
 
-**Note**  The Windows Pre-Processor (WPP) Tracing tools such as TraceView.exe cannot be used to start, stop, or view traces.
+**Note** The Windows Pre-Processor (WPP) Tracing tools such as TraceView.exe cannot be used to start, stop, or view traces.
 
 
 Run the sample
@@ -19,7 +19,7 @@ Run the sample
 
     Installing the manifest creates registry keys that enable tools to find the resource and message files that contain event provider information. For further details about the WevtUtil.exe tool, see the MSDN Library.
 
-    **Note**  Using a Visual Studio Command windows sets up the environment variables you need to run the tracing tools for this sample.
+    **Note** Using a Visual Studio Command windows sets up the environment variables you need to run the tracing tools for this sample.
 
 2.  Make a folder in the system directory called ETWDriverSample (for example, C:\\ETWDriverSample).
 
diff --git a/general/tracing/tracedriver/ReadMe.md b/general/tracing/tracedriver/ReadMe.md
index 3e95d383..064fb133 100644
--- a/general/tracing/tracedriver/ReadMe.md
+++ b/general/tracing/tracedriver/ReadMe.md
@@ -29,7 +29,7 @@ To test the Tracedrv event tracing provider, use the following procedure.
   tracelog -start TestTracedrv -guid tracedrv.ctl -f tracedrv.etl -flag 1
   ```
 
-  **Note**  Note: Without the -flag parameter, Tracedrv will not generate any trace messages.
+  **Note** Without the -flag parameter, Tracedrv will not generate any trace messages.
 
 5.  To generate trace messages, run Tracectl.exe. This executable file is built when you build the solution. Each time you type a character, other than **Q** or **q**, Tracectl sends an IOCTL to the driver that signals it to generate trace messages. To stop Tracectl, type **Q** or **q**.
 6.  To stop the trace session, use the following Tracelog command.