updated the profiling workshop

Author: dmitchsplunk

content/en/scenarios/debug_problems/3-enable-profiling.md

@@ -80,9 +80,8 @@ Let's open the AlwaysOn Profiler to review the CPU stack trace in more detail.
 
 ![Flamegraph and table](../images/flamegraph_and_table.png)
 
-By default, the AlwaysOn Profiler shows both the table and [flamegraph](https://www.brendangregg.com/flamegraphs.html). Take some time to explore this view by doing some of the following:
+The AlwaysOn Profiler includes both a table and a [flamegraph](https://www.brendangregg.com/flamegraphs.html). Take some time to explore this view by doing some of the following:
 
-* toggle between flamegraph and table views
 * click a table item and notice the change in flamegraph
 * navigate the flamegraph by clicking on a stack frame to zoom in, and a parent frame to zoom out
 * add a search term like `splunk` or `jetty` to highlight some matching stack frames

content/en/scenarios/debug_problems/5-fix-ingame-slowness.md

@@ -8,7 +8,7 @@ weight: 5
 
 Now that our game startup slowness has been resolved, let's play several rounds of the Door Game and ensure the rest of the game performs quickly. 
 
-As you play the game, do you notice any slowness?  Let's look at the data in **Splunk Observability** Cloud to put some numbers on what we're seeing. 
+As you play the game, do you notice any other slowness?  Let's look at the data in **Splunk Observability** Cloud to put some numbers on what we're seeing. 
 
 ### Review Game Performance in Splunk Observability Cloud