Fixed typos

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

@@ -33,7 +33,7 @@ The following are requirements to run this lab:
 2. Setup Performance Monitor on Windows to track `SQL Statistics/Batch Requests/sec` counter. Alternatively, open the file `C:\Labs\Lab-AutoTuning\SCENARIO\Perfmon.htm` with Internet Explorer. Note you may receive a prompt warning that Internet Explorer blocked ActiveX content. Click on **Allow blocked content**. 
 
     - Once the file opens, click on the green arrow button to **Unfreeze display**.
-    - You receive a prompt warning *this action will erase the data in the graph*. Click **Yes** top continue. This resumes the performance counter session previously saved for convenience.
+    - You receive a prompt warning *this action will erase the data in the graph*. Click **Yes** to continue. This resumes the performance counter session previously saved for convenience.
     - Leave it open...
 
 3. While the scenario workload is running, double-click the file `Regression.cmd` in the same folder to execute it. Notice the drop in the *batch requests/sec* counter which means a performance regression was introduced in the workload.

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

@@ -11,78 +11,86 @@ author: Pam Lahoud
     Server 2019 CTP 2.3.
 
 2.  Open SQL Server Management Studio (SSMS) and connect to the
-    HkTempDBTestVM\\SQL2019\_CTP23 instance. Verify that the
+    **HkTempDBTestVM\\SQL2019\_CTP23** instance. Verify that the
     AdventureWorks database exists. If it does not, perform the
     following steps:
 
-    a.  Open and execute the script
-        C:\\Labs\\Memory-OptimizedTempDB\\00-AdventureWorks\_Setup.sql.
+    1.  Open and execute the script
+        `C:\Labs\Memory-OptimizedTempDB\00-AdventureWorks\_Setup.sql`.
         This will restore the AdventureWorks database and make
         configuration changes needed for the rest of the lab.
 
-    b.  Open and execute the script
-        C:\\Labs\\Memory-OptimizedTempDB\\01-SalesAnalysis\_Optimized.sql
-        to create the SalesAnalysis\_Optimized stored procedure.
+    2.  Open and execute the script
+        `C:\Labs\Memory-OptimizedTempDB\01-SalesAnalysis\_Optimized.sql`
+        to create the **SalesAnalysis\_Optimized** stored procedure.
 
 3.  Verify that there are no startup trace flags set:
 
-    a.  Open SQL Server Configuration Manager
+    1.  Open **SQL Server Configuration Manager**.
 
-    b.  Click "SQL Server Services" in the left pane
+    2.  Click "SQL Server Services" in the left pane.
 
-    c.  Right-Click "SQL Server (SQL2019\_CTP23)" and choose
-        "Properties"
+    3.  Right-Click "SQL Server (SQL2019\_CTP23)" and choose
+        ***Properties***.
 
-    d.  Click the "Startup Parameters" tab
+    4.  Click the ***Startup Parameters*** tab.
 
-    e.  Verify that there are no lines that being with "T-" in the list
-        of Existing parameters:\
-        ![StartupParametersNoFlag.png](../media/StartupParametersNoFlag.png)\
-        If any exist, highlight them and click "Remove"
+    5.  Verify that there are no lines that being with "-T" in the list
+        of existing parameters:    
 
-    f.  Click "OK" to close the Properties window, then click "OK" on
-        the Warning box that pops up
+        ![StartupParametersNoFlag.png](../media/StartupParametersNoFlag.png)
+
+        If any exist, highlight them and click "Remove".
+
+    6.  Click "OK" to close the *Properties* window, then click "OK" on
+        the Warning box that pops up.
 
-    g.  Restart the SQL Server service by right-clicking on "SQL Server
-        (SQL2019\_CTP23)" and choosing "Restart"
+    7.  Restart the SQL Server service by right-clicking on "SQL Server
+        (SQL2019\_CTP23)" and choosing **Restart**.
+
+4.  Browse to the `C:\Labs\Memory-OptimizedTempDB` folder and
+    double-click the file `SQL2019_CTP23_PerfMon.htm` file to open it in
+    Internet Explorer.    
+    
+    - Once the file opens, click on the green arrow button to **Unfreeze display**.
+    - You receive a prompt warning *this action will erase the data in the graph*.    
+        Click **Yes** to continue. This resumes the performance counter session 
+        previously saved in preparation for the lab.
+    - Leave it open...
 
-4.  Browse to the C:\\Labs\\Memory-OptimizedTempDB folder and
-    double-click the file SQL2019\_CTP23\_PerfMon.htm file to open it in
-    Internet Explorer. Click "Allow blocked content" to allow the script
-    to run. Right-click on the graph and then click "Yes" to erase the
-    existing data. This will clear the Performance Monitor graph in
-    preparation for the lab.
+5.  In SSMS, open the following script files:
 
-5.  In SSMS, open the following scripts:\
-    02-get waiting tasks and executing command.sql\
-    02-get summary of current waits.sql\
-    02-get object info from page resource sql 2019.sql\
-    These will be used to monitor the server while the workload is
-    running.
+    - `02-get waiting tasks and executing command.sql`
+    - `02-get summary of current waits.sql`
+    - `02-get object info from page resource sql 2019.sql`
+
+    These will be used to monitor the server while the workload 
+    is running.
 
 6.  Start the workload:
 
-    a.  Open a Command Prompt and browse to
-        C:\\Labs\\Memory-OptimizedTempDB
+    1.  Open a Command Prompt and browse to
+        `C:\Labs\Memory-OptimizedTempDB`
 
-    b.  Go back to the Internet Explorer window that has the Performance
+    2.  Go back to the Internet Explorer window that has the Performance
         Monitor collector open and click the play button to start the
-        collection
+        collection.
 
-    c.  From the Command Prompt window, execute
-        SQL2019\_CTP21\_Run\_SalesAnalysis\_Optimized.bat by typing or
-        pasting the file name and hitting Enter
+    3.  From the Command Prompt window, execute
+        `SQL2019_CTP21_Run_SalesAnalysis_Optimized.bat` by typing or
+        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. You can
-    then go to SSMS and run the various scripts to monitor the workload.
+    Monitor. You should see *Batch Requests per Second* 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
-    the 02-get object info from page resource sql 2019.sql you should
+    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. This is TempDB metadata contention
-    and is the scenario that this SQL 2019 improvement is targeted to
-    correct. Feel free to run the workload a few more times to examine
+    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
     the different scripts and performance counters. Each time you run
     it, the runtime will be reported in the Command Prompt window. It
     should take about 1 minute to run.
@@ -96,35 +104,37 @@ author: Pam Lahoud
 
 9.  Turn on Memory-Optimized TempDB:
 
-    a.  Open SQL Server Configuration Manager
+    1.  Open **SQL Server Configuration Manager**.
 
-    b.  Click "SQL Server Services" in the left pane
+    2.  Click "SQL Server Services" in the left pane.
 
-    c.  Right-Click "SQL Server (SQL2019\_CTP23)" and choose
-        "Properties"
+    3.  Right-Click "SQL Server (SQL2019\_CTP23)" and choose
+        ***Properties***.
 
-    d.  Click the "Startup Parameters" tab
+    4.  Click the ***Startup Parameters*** tab.
 
-    e.  In the "Specify a startup parameter:" box, type "T-3895" and
-        click the "Add" button
+    5.  In the "Specify a startup parameter:" box, type "-T3895" and
+        click the "Add" button.
 
-    f.  The "Existing parameters:" box should now look like this\
-        ![StartupParametersNoFlag.png](../media/StartupParametersNoFlag.png)
+    6.  The "Existing parameters:" box should now look like this:
 
-    g.  Click "OK" to close the Properties window, then click "OK" on
-        the Warning box that pops up
+       ![StartupParametersNoFlag.png](../media/StartupParametersNoFlag.png)
 
-    h.  Restart the SQL Server service by right-clicking on "SQL Server
-        (SQL2019\_CTP23)" and choosing "Restart"
+    7.  Click "OK" to close the *Properties* window, then click "OK" on
+        the Warning box that pops up.
+
+    8.  Restart the SQL Server service by right-clicking on "SQL Server
+        (SQL2019\_CTP23)" and choosing **Restart**.
 
 10. Go back to the Performance Monitor collector and click play to start
-    the collection
+    the collection.
 
-11. Start the workload the same way you did in Step 5
+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
-    be no Page Latch waits.
+    be no Page Latch waits.   
+
     > **Note:**
     > You may see a small bump of Page Latch waits the first
     time you run the workload after the restart. This should disappear