Workshop housekeeping

Author: rcastley

content/en/ninja-workshops/1-automatic-discovery/1-petclinic-monolith/1-otel-collector.md

@@ -6,7 +6,7 @@ weight: 1
 
 The Splunk OpenTelemetry Collector is the core component of instrumenting infrastructure and applications.  Its role is to collect and send:
 
-* Infrastructure metrics (disk, CPU, memory, etc)
+* Infrastructure metrics (disk, CPU, memory, etc.)
 * Application Performance Monitoring (APM) traces
 * Profiling data
 * Host and application logs
@@ -30,10 +30,10 @@ sudo sh /tmp/splunk-otel-collector.sh --uninstall
 To ensure your instance is configured correctly, we need to confirm that the required environment variables for this workshop are set correctly. In your terminal run the following command:
 
 ``` bash
-. ~/workshop/scripts/check_env.sh
+. ~/workshop/petclinic/scripts/check_env.sh
 ```
 
-In the output check that all of the following environment variables are present and have values set. If any are missing, please contact your instructor:
+In the output check that all the following environment variables are present and have values set. If any are missing, please contact your instructor:
 
 ```text
 ACCESS_TOKEN
@@ -44,7 +44,7 @@ HEC_URL
 INSTANCE
 ```
 
-We can then go ahead and install the Collector. Some additional parameters are passed to the install script, they are:
+We can then go ahead and install the Collector. Some additional parameters are passed to the installation script, they are:
 
 * `--with-instrumentation` - This will install the agent from the Splunk distribution of OpenTelemetry Java, which is then loaded automatically when the PetClinic Java application starts up. No configuration is required!
 * `--deployment-environment` - Sets the resource attribute `deployment.environment` to the value passed. This is used to filter views in the UI.

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/2-preparation/_index.md

@@ -49,9 +49,9 @@ INSTANCE = <instance_name>
 {{% /tab %}}
 {{< /tabs >}}
 
-Please make a note of the `INSTANCE` environment variable value as this will used later to filter data in **Splunk Observability Cloud**.
+Please make a note of the `INSTANCE` environment variable value as this will be used later to filter data in **Splunk Observability Cloud**.
 
-For this workshop, **all** of the above are required. If any have values missing, please contact your Instructor.
+For this workshop, **all** the above are required. If any have values missing, please contact your Instructor.
 
 > [!SPLUNK] Delete any existing OpenTelemetry Collectors
 >If you have previously completed a Splunk Observability workshop using this EC2 instance, you

content/en/ninja-workshops/3-opentelemetry-collector-workshops/2-advanced-collector/6-sensitive-data/6-2-test-delete-tag.md

@@ -20,10 +20,11 @@ In this exercise, we will **delete** the `user.account_password`, **update** the
 ../otelcol --config=agent.yaml
 ```
 
-**Start the Loadgen**:
+**Start the Load Generator**:
 
 1. In the **Spans terminal** window change into the `6-sensitive-data` directory.
 2. Start the `loadgen`:
+
 ```sh
 ../loadgen
 ```

content/en/scenarios/optimize_end_user_experiences/3-advanced-synthetics/_index.md

@@ -18,6 +18,7 @@ The exported JSON from the Chrome DevTools Recorder will then be used to create
 - Access to Splunk Observability Cloud
 
 ## Supporting resources
-1. Lantern: [advanced Selectors for multi-step browser tests](https://lantern.splunk.com/Observability/UCE/Proactive_response/Optimize_End-User_Experiences/Running_Synthetics_browser_tests/Selectors_for_multi-step_browser_tests)
+
+1. Lantern: [advanced Selectors for multistep browser tests](https://lantern.splunk.com/Observability/UCE/Proactive_response/Optimize_End-User_Experiences/Running_Synthetics_browser_tests/Selectors_for_multi-step_browser_tests)
 1. Chrome for Developers [DevTools Tips](https://developer.chrome.com/blog/devtools-tips-4)
-1. web.dev [Core Web Vitals](https://web.dev/explore/learn-core-web-vitals) reference
+1. web.dev [Core Web Vitals](https://web.dev/explore/learn-core-web-vitals) reference

legacy-content/en/99-imt-admin/_index.md

@@ -9,9 +9,9 @@ hidden: true
 
 During this _**technical**_ Splunk Observability Cloud Infrastructure Monitoring Workshop, you will build out an environment based on a [lightweight](https://k3s.io/) Kubernetes[^1] cluster.
 
-To simplify the workshop modules, a pre-configured AWS/EC2 instance is provided and the instructor will provide you with the login information for the instance that you will be using during the workshop.
+To simplify the workshop modules, a pre-configured AWS/EC2 instance is provided, and the instructor will provide you with the login information for the instance that you will be using during the workshop.
 
-The instance is pre-configured with all the software required to deploy the Splunk OpenTelemetry Connector[^2] in Kubernetes, deploy an NGINX^3 ReplicaSet^4 and finally deploy a microservices-based application which has been instrumented using OpenTelemetry to send metrics, traces, spans and logs[^5].
+The instance is pre-configured with all the software required to deploy the Splunk OpenTelemetry Connector[^2] in Kubernetes, deploy an NGINX[^3] ReplicaSet[^4] and finally deploy a microservices-based application which has been instrumented using OpenTelemetry to send metrics, traces, spans and logs[^5].
 
 The workshops also introduce you to dashboards, navigators editing and creating charts, creating detectors to fire alerts, Monitoring as Code and the Service Bureau[^6]
 
@@ -60,9 +60,9 @@ INSTANCE = <instance_name>
 {{% /tab %}}
 {{< /tabs >}}
 
-Please make a note of the `INSTANCE` environment variable value as this will used later to filter data in **Splunk Observability Cloud**.
+Please make a note of the `INSTANCE` environment variable value as this will be used later to filter data in **Splunk Observability Cloud**.
 
-For this workshop, **all** of the above are required. If any have values missing, please contact your Instructor.
+For this workshop, **all** the above are required. If any have values missing, please contact your Instructor.
 
 [^1]: [**Kubernetes**](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/) is a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation.
 [^2]: [**OpenTelemetry Collector**](https://opentelemetry.io/) offers a vendor-agnostic implementation on how to receive, process and export telemetry data. In addition, it removes the need to run, operate and maintain multiple agents/collectors to support open-source telemetry data formats (e.g. Jaeger, Prometheus, etc.) sending to multiple open-source or commercial back-ends.