scenario 4 minor changes

Author: swaretech

content/en/scenarios/optimize_end_user_experiences/1-synthetics/3-browser/_index.md

@@ -17,7 +17,7 @@ A page where your users commonly "land" is a good choice to start with a single
 2. Use the test Name and Custom properties to describe the scope of the test. Then click {{< button >}}+ Edit steps{{< /button >}}<p></p>
 ![](https://ajeuwbhvhr.cloudimg.io/colony-recorder.s3.amazonaws.com/files/2024-02-09/8e3f2a3f-31b3-49b5-9bd1-735775d84652/ascreenshot.jpeg?tl_px=137,197&br_px=1856,1158&force_format=png&width=1120.0&wat=1&wat_opacity=0.7&wat_gravity=northwest&wat_url=https://colony-recorder.s3.us-west-1.amazonaws.com/images/watermarks/FB923C_standard.png&wat_pad=524,276)
 
-3. Change the transaction label (top left) and step name (on the right) to something readable that describes the step. Add the URL you'd like to test. In the below example, the transaction is "Home" and the step name is "Go to homepage".<p></p>
+3. Change the transaction label (top left) and step name (on the right) to something readable that describes the step. Add the URL you'd like to test. Your workshop instructor can provide you with a URL as well. In the below example, the transaction is "Home" and the step name is "Go to homepage".<p></p>
 ![Transaction and step label](../_img/single-step.png)
 
 4. To validate the test, change the location as needed and click {{< button >}}Try now{{< /button >}}. See the docs for more information on the [try now feature](https://docs.splunk.com/observability/en/synthetics/test-config/try-now.html).<p></p>
@@ -35,4 +35,4 @@ A page where your users commonly "land" is a good choice to start with a single
 8. You can edit the Device and Frequency or leave them at their default values for now. Click {{% button style="blue" %}}Submit{{% /button %}} to save the test and start running it.<p></p>
 ![](https://ajeuwbhvhr.cloudimg.io/colony-recorder.s3.amazonaws.com/files/2024-02-09/a37a8de3-b1d2-4edc-929e-0ee9994d646a/ascreenshot.jpeg?tl_px=0,838&br_px=1719,1799&force_format=png&width=1120.0&wat=1&wat_opacity=0.7&wat_gravity=northwest&wat_url=https://colony-recorder.s3.us-west-1.amazonaws.com/images/watermarks/FB923C_standard.png&wat_pad=133,559)
 
-While our Synthetic tests are running, let's instrument RUM to start getting data from our real users!
+While our Synthetic tests are running, let's see how RUM is instrumented to start getting data from our real users!

content/en/scenarios/optimize_end_user_experiences/2-rum/1-overview.md

@@ -4,26 +4,24 @@ linkTitle: 1. Overview
 weight: 1
 ---
 
-## Overview of the RUM Workshop
-
 The aim of this Splunk Real User Monitoring (RUM) workshop is to let you:
 
-* Shop for some fantastic items on the Online Boutique to create traffic, and create a number of RUM User Sessions[^1] that you can view in the Splunk Observability Suite.
+* Shop for items on the Online Boutique to create traffic, and create a number of RUM User Sessions[^1] that you can view in the Splunk Observability Suite.
 
-* See an overview of the performance of all your application(s) in the Application Summary Dashboard (Both Mobile and Web based)
+* See an overview of the performance of all your application(s) in the Application Summary Dashboard
 
 * Examine the performance of a specific website or Mobile App with RUM metrics.
 
 * Investigate issues with your website and backend services.
 
 * (Optionally) See how to add RUM to your website.
 
-In order to reach this goal, we will use an online boutique to order various products. Whilst shopping on the online boutique you will create what is called a User Session.
+In order to reach this goal, we will use an online boutique to order various products. While shopping on the online boutique you will create what is called a User Session.
 
 You may encounter some issues with this web site, and you will use Splunk RUM to identify the issues, so they can be resolved by the developers.
 
 If this a standalone RUM workshop, the workshop host will provide you with a URL for an online boutique store that has RUM enabled.
 
-Each of these Online Boutiques are also being visited by a few synthetic users, this will allow us to generate more live data to be analyzed later.
+Each of these Online Boutiques are also being visited by a few synthetic users; this will allow us to generate more live data to be analyzed later.
 
-[^1]: A RUM Users session is a "recording" of a collection of user interactions on an application, basically collecting a website or app’s performance measured straight from the browser or Mobile App of the end user. To do this a small amount of JavaScript is embedded in each page. This script then collects data from each user as he or she explores the page, and transfers that data back for analysis.
+[^1]: A RUM User session is a "recording" of a collection of user interactions on an application, basically collecting a website or app’s performance measured straight from the browser or Mobile App of the end user. To do this a small amount of JavaScript is embedded in each page. This script then collects data from each user as he or she explores the page, and transfers that data back for analysis.

content/en/scenarios/optimize_end_user_experiences/2-rum/2-setup.md

@@ -15,7 +15,7 @@ Your workshop instructor will provide you with the Online Boutique URL that has
 
 ## 2.  Inspecting the HTML source
 
-The changes needed for RUM are placed in the `<head>` section of the hosts Web page. Below is the updated `<head>` section with the changes required to enable RUM:
+The changes needed for RUM are placed in the `<head>` section of the hosts Web page. Right click to view the page source or to inspect the code. Below is an example of the `<head>` section with RUM:
 
 ![Online Boutique](../images/rum-inst.png)
 
@@ -31,3 +31,7 @@ The above lines 21 and 23-30 are all that is required to enable RUM on your webs
 Lines 22 and 31-34 are optional if you want Session Replay instrumented.
 
 Line 36-39 `var tracer=Provider.getTracer('appModuleLoader');` will add a Custom Event for every page change, allowing you to better track your website conversions and usage.  
+
+{{% notice title="Exercise" style="green" icon="running" %}}
+Time to shop! Take a minute to open the workshop store URL in as many browsers and devices as you'd like, shop around, add items to cart, checkout, and feel free to close the shopping browsers when you're finished.
+{{% /notice %}}

content/en/scenarios/optimize_end_user_experiences/2-rum/8-alerting.md

@@ -9,6 +9,6 @@ With [RUM](https://docs.splunk.com/observability/en/rum/intro-to-rum.html) instr
 
 This workshop walks through how our demo site is instrumented and how to interpret the data. If you already have a RUM license, this will help you understand how RUM works and how you can use it to optimize your end user experience. 
 
+{{% notice title="Tip" style="primary"  icon="lightbulb" %}}
 Our Docs also contain guidance such as [scenarios using Splunk RUM](https://docs.splunk.com/observability/en/rum/rum-scenario-library/scenario-landingpage.html) and demo applications to test out [RUM for mobile apps](https://docs.splunk.com/observability/en/rum/sample-app.html).
-
-![Architecture Overview](images/rum-architecture.png)
+{{% /notice %}}

content/en/scenarios/optimize_end_user_experiences/2-rum/_index.md

@@ -3,13 +3,13 @@ title: 1.1 Recording a test
 weight: 1
 ---
 
-Write down a short user journey you want to test. Remember: smaller bites are easier to chew! In other words, get started with just a few steps. This is easier not only to create and maintain the test, but also to understand and act on ther results. Test the essential features to your users, like a support contact form, login widget, or date picker.
+Write down a short user journey you want to test. Remember: smaller bites are easier to chew! In other words, get started with just a few steps. This is easier not only to create and maintain the test, but also to understand and act on the results. Test the essential features to your users, like a support contact form, login widget, or date picker.
 
 {{% notice note %}}
 Record the test in the same type of viewport that you want to run it. For example, if you want to run a test on a mobile viewport, narrow your browser width to mobile and refresh before starting the recording. This way you are capturing the correct elements that could change depending on responsive style rules.
 {{% /notice %}}
 
-Open your starting URL in Chrome Incognito. This is important so you're not carrying cookies into the recording, that we won't have set up in the Synthetic test by default. If you would prefer to start on a demo site, feel free to use [https://frontend-eu.splunko11y.com](https://frontend-eu.splunko11y.com) or [https://frontend-us.splunko11y.com](https://frontend-us.splunko11y.com), which we are using in the examples below.
+Open your starting URL in Chrome Incognito. This is important so you're not carrying cookies into the recording, which we won't set up in the Synthetic test by default. If you workshop instructor does not have a custom URL, feel free to use [https://frontend-eu.splunko11y.com](https://frontend-eu.splunko11y.com) or [https://frontend-us.splunko11y.com](https://frontend-us.splunko11y.com), which are in the examples below.
 
 ## Open the Chrome DevTools Recorder
 
@@ -56,7 +56,7 @@ Select **JSON** as the format, then click on **Save**
 
 ---
 
-{{% expand "Click here to view the JSON file" %}}
+{{% expand "View the example JSON file for this browser test recording" %}}
 
 ```json
 {

content/en/scenarios/optimize_end_user_experiences/2-rum/images/rum-architecture.png

@@ -5,4 +5,9 @@ weight: 4
 hidden: false
 ---
 
-Provide a dashboard group for the workshop.
+Go to Dashboards and find the End User Experiences dashboard group. 
+
+Click the three dots on the top right to open the dashboard menu, and select Save As.
+
+Use your initials in the dashboard name, select "copy data links", and save to the dashboard group that matches your email address. Now you have your own copy of this dashboard to customize!
+

content/en/scenarios/optimize_end_user_experiences/3-advanced-synthetics/1-recording-a-test.md

@@ -18,12 +18,12 @@ Sections:
 - [Dashboard charts](./4-dashboards/_index.md) to capture our KPIs, show trends, and show data in context of our events
 - [Detectors](./5-detectors/_index.md) to alert on our KPIs
 
-{{% notice title="Tip" style="primary"  icon="lightbulb" %}}Keep in mind throughout the workshop: how can I prioritize strategically to get the fastest time to value for my end users and for myself/ my developers?{{% /notice %}}
+{{% notice title="Tip" style="primary"  icon="lightbulb" %}}Keep in mind throughout the workshop: how can I prioritize activities strategically to get the fastest time to value for my end users and for myself/ my developers?{{% /notice %}}
 
 
 ## Context
 
-As a reminder, we need frontend performance testing to capture everything that goes into our end user experience. If we're just monitoring the backend, we're missing all of the other resources that are critical to our users' success. Read [What the Fastly Outage Can Teach Us About Observability](https://www.splunk.com/en_us/blog/devops/what-the-fastly-outage-can-teach-us-about-observability.html) for a real world example.
+As a reminder, we need frontend performance monitoring to capture everything that goes into our end user experience. If we're just monitoring the backend, we're missing all of the other resources that are critical to our users' success. Read [What the Fastly Outage Can Teach Us About Observability](https://www.splunk.com/en_us/blog/devops/what-the-fastly-outage-can-teach-us-about-observability.html) for a real world example. Click the image below to zoom in.
 ![What goes into the front end](./_img/frontend.png)
 
 ## References