Fixed typos

Sessions/Winter-Ready-2019/Lab-AutoTuning.md

@@ -52,9 +52,9 @@ The following are requirements to run this lab:
     SET AUTOMATIC_TUNING ( FORCE_LAST_GOOD_PLAN = ON )
     ```
 
-7. double-click the file `Auto_tune.cmd`  in the same folder to execute it. This uses the above command to set automatic plan correct ON for WideWorldImporters, and restarts the workload file `Scenario.cmd`.
+7. Double-click the file `Auto_tune.cmd`  in the same folder to execute it. This uses the above command to set automatic plan correct ON for WideWorldImporters, and restarts the workload file `Scenario.cmd`.
 
 8. Repeat steps 3-5 as above, and note the following:     
-    - In the Performance Monitor windwo you will see the **batch requests/sec** counter dip, but within a second go right back up.    
+    - In the Performance Monitor window you will see the **Batch Requests/sec** counter dip, but within a second go right back up.    
     This is because SQL Server detected the regression and automatically reverted to the last known good query plan found in the Query Store. 
     - If closed, re-open the file `C:\Labs\Lab-AutoTuning\SCENARIO\recommendations.sql` with SQL Server Management Studio or SQL Operations Studio, execute it and notice the *state_transition_reason* column value is now ***LastGoodPlanForced***.

Sessions/Winter-Ready-2019/Lab-Memory-OptimizedTempDB.md

@@ -81,13 +81,13 @@ author: Pam Lahoud
         pasting the file name and hitting **Enter**.
 
 7.  While the workload is running, watch the counters in Performance
-    Monitor. You should see *Batch Requests per Second* around 500 and
-    there should be *Page Latch* waits throughout the workload.    
+    Monitor. You should see **Batch Requests/sec** around 500 and
+    there should be **Page Latch** waits throughout the workload.    
     You can then go to SSMS and run the various scripts to monitor the workload.   
-    You should see several sessions waiting on PAGELATCH, and when using
+    You should see several sessions waiting on `PAGELATCH`, and when using
     the `02-get object info from page resource sql 2019.sql` you should
     see the sessions are waiting on pages that belong to TempDB system
-    tables, most often sysschobjs.    
+    tables, most often `sysschobjs`.    
     This is TempDB metadata contention and is the scenario that this 
     SQL Server 2019 improvement is targeted to correct.    
     Feel free to run the workload a few more times to examine
@@ -131,8 +131,8 @@ author: Pam Lahoud
 
 11. Start the workload the same way you did in Step 5.
 
-12. Again, watch the Performance Monitor counters. You should see Batch
-    Requests per Second higher this time, around 600, and there should
+12. Again, watch the Performance Monitor counters. You should see **Batch Requests/sec**
+    higher this time, around 600, and there should
     be no Page Latch waits.   
 
     > **Note:**

Sessions/Winter-Ready-2019/Lab-QTA.md

@@ -18,7 +18,8 @@ Starting with SSMS v18, the new **Query Tuning Assistant (QTA)** feature will gu
 
 ![Recommended database upgrade workflow using QTA](../media/qta-usage.png "Recommended database upgrade workflow using QTA")
 
-Note that QTA does not generate user workload so users must ensure that a representative test workload can be executed on the target instance. 
+> **Note:** 
+> QTA does not generate user workload so users must ensure that a representative test workload can be executed on the target instance. 
 
 ## Lab requirements (pre-installed)
 The following are requirements to run this lab: