diff --git a/src/PerfView/SupportFiles/UsersGuide.htm b/src/PerfView/SupportFiles/UsersGuide.htm
index e57ec75f6..aae8b9ac4 100644
--- a/src/PerfView/SupportFiles/UsersGuide.htm
+++ b/src/PerfView/SupportFiles/UsersGuide.htm
@@ -504,7 +504,7 @@ <h4>
     <p>
         The bottom up view did an excellent job of determining that the get_Now() method
         as well as the &#39;SpinForASecond&#39; consume the largest amount of time and thus
-        are worth looking at closely.&nbsp;&nbsp;&nbsp;&nbsp; This corresponds beautify
+        are worth looking at closely.&nbsp;&nbsp;&nbsp;&nbsp; This corresponds
         to our expectations given the source code in <a href="Tutorial.cs.txt">Tutorial.cs</a>.&nbsp;&nbsp;&nbsp;
         However it can also be useful to understand where CPU time was consumed from the
         top down.&nbsp; This is what the <a href="#CallTreeView">CallTree view</a> is for.&nbsp;&nbsp;
@@ -529,7 +529,7 @@ <h4>
         stacks), which typically run in the 5-10% range.&nbsp;&nbsp; In this case it seems
         to be about 6%).&nbsp;&nbsp; The &#39;When&#39; column also clearly shows how one
         instance of RecSpin runs SpinForASecond (for exactly a second) and then calls a
-        RecSpinHelper which does consumes close to 100% of the CPU for the rest of the time.
+        RecSpinHelper which consumes close to 100% of the CPU for the rest of the time.
         .&nbsp;&nbsp; The call Tree is a wonderful top-down synopsis.&nbsp;
     </p>
     <h4>Getting a &#39;coarser&#39; view</h4>
@@ -539,9 +539,9 @@ <h4>Getting a &#39;coarser&#39; view</h4>
         use this fact and the &#39;Fold %&#39; functionality to get an even coarser view
         of the &#39;top&#39; of the call tree.&nbsp;&nbsp; With all nodes expanded, simply
         right click on the window and select &#39;Increase Fold %&#39; (or easier hit the
-        F7 key).&nbsp; This increases the number it the Fold % textbox by 1.6X.&nbsp;&nbsp;
+        F7 key).&nbsp; This increases the number in the Fold % textbox by 1.6X.&nbsp;&nbsp;
         By hitting the F7 key repeatedly you keep trimming down the &#39;bottoms&#39; of
-        the stacks until you only see only the methods that use a large amount of CPU time.&nbsp;&nbsp;&nbsp;
+        the stacks until you only see methods that use a large amount of CPU time.&nbsp;&nbsp;&nbsp;
         The following image shows the CallTreeView&nbsp; after hitting F7 seven times.&nbsp;&nbsp;
     </p>
     <center>
@@ -1804,7 +1804,7 @@ <h4>
     <p>
         A typical GC Memory investigation includes dump of the GC heap. While this gives
         very detailed information about the heap at the time the snapshot was taken, it
-        give no information about the GC behavior over time. This is what the GCStats report
+        gives no information about the GC behavior over time. This is what the GCStats report
         does. To get a GCStats reports you must <a href="#CollectingData">Collect Event Data</a>
         as you would for a CPU investigation (the GC events are on by default). When you
         open the resulting ETL file one of the children will be a 'GCStats' view. Opening