Starting to add some polish

Author: rcastley

content/en/s4r/1-workshop-goals/_index.md

@@ -26,7 +26,7 @@ Examine the real user data that has been provided by the telemetry received from
 
 ##### 6. Splunk Application Performance Monitoring
 
-Discover the power of **full end-to-end visibility** by jumping from a RUM trace (frontend) to an APM trace (backend). All the services are sending telemetry (traces and spans) that Splunk Observability Cloud can visualize, analyze and use to detect anomalies and errors.
+Discover the power of **full end-to-end visibility** by jumping from a RUM trace (front-end) to an APM trace (back-end). All the services are sending telemetry (traces and spans) that Splunk Observability Cloud can visualize, analyze and use to detect anomalies and errors.
 
 ##### 7. Using Logs with Splunk Log Observer
 

content/en/s4r/2-opentelemetry/_index.md

@@ -8,7 +8,7 @@ tags:
 
 With the rise of cloud computing, microservices architectures, and ever-more complex business requirements, the need for Observability has never been greater. Observability is the ability to understand the internal state of a system by examining its outputs. In the context of software, this means being able to understand the internal state of a system by examining its telemetry data, which includes **metrics**, **traces**, and **logs**.
 
-To make a system observable, it must be instrumented. That is, the code must emit traces, metrics, and logs. The instrumented data must then be sent to an Observability backend such as **Splunk Observability Cloud**.
+To make a system observable, it must be instrumented. That is, the code must emit traces, metrics, and logs. The instrumented data must then be sent to an Observability back-end such as **Splunk Observability Cloud**.
 
 {{< mermaid >}}
 
@@ -53,4 +53,4 @@ Since OpenTelemetry is vendor-neutral and supported by many industry leaders in
 
 Splunk has fully committed to OpenTelemetry so that our customers can collect and use **ALL** their data, in any type, any structure, from any source, on any scale, and all in real-time. OpenTelemetry is fundamentally changing the monitoring landscape, enabling IT and DevOps teams to bring data to every question and every action. You will experience this during these workshops.
 
-![full stack Splunk](images/splunk-full-stack.png?width=40vw)
+![full stack Splunk](images/otel.png)

content/en/s4r/2-opentelemetry/images/pexels-gustavo-fring-6870313.jpg

@@ -4,13 +4,13 @@ linkTitle: 1. APM Overview
 weight: 1
 ---
 
-Splunk APM provides a **NoSample™** end-to-end visibility of every service and its dependency to solve problems quicker across monoliths and microservices. Teams can immediately detect problems from new deployments, confidently troubleshoot by scoping and isolating the source of an issue, and optimize service performance by understanding how backend services impact end users and business workflows.
+Splunk APM provides a **NoSample™** end-to-end visibility of every service and its dependency to solve problems quicker across monoliths and microservices. Teams can immediately detect problems from new deployments, confidently troubleshoot by scoping and isolating the source of an issue, and optimize service performance by understanding how back-end services impact end users and business workflows.
 
 **Real-time monitoring and alerting:** Splunk provides a 10-second resolution on metrics to detect and alert on issues when they happen.  
 **Dynamic telemetry maps:** Easily visualize service performance in modern production environments in real-time. End-to-end visibility of service performance from infrastructure, applications, end users, and all dependencies helps quickly scope new issues and troubleshoot more effectively.  
 **Intelligent tagging and analysis:** View all tags from your business, infrastructure and applications in one place to easily compare new trends in latency or errors to their specific tag values.  
 **AI-directed troubleshooting identifies the most impactful issues:** Instead of manually digging through individual dashboards, isolate problems more efficiently. Automatically identify anomalies and the sources of errors that impact services and customers the most.  
-**Complete distributed tracing analyses every transaction:** Identify problems in your cloud-native environment more effectively. Splunk distributed tracing visualizes and correlates every transaction from the backend and frontend in context with your infrastructure, business workflows and applications.  
+**Complete distributed tracing analyses every transaction:** Identify problems in your cloud-native environment more effectively. Splunk distributed tracing visualizes and correlates every transaction from the back-end and front-end in context with your infrastructure, business workflows and applications.  
 **Full stack correlation:** Within Splunk Observability, APM links traces, metrics, logs and profiling together to easily understand the performance of every component and its dependency across your stack.  
 **Monitor database query performance:** Easily identify how slow and high execution queries from SQL and NoSQL databases impact your services, endpoints and business workflows — no instrumentation required.  
 

content/en/s4r/2-opentelemetry/images/splunk-full-stack.png

@@ -8,7 +8,7 @@ Splunk Synthetic Monitoring provides visibility across URLs, APIs and critical w
 
 **Ensure Availability:** Proactively monitor and alert on the health and availability of critical services, URLs and APIs with customizable browser tests to simulate multi-step workflows that make up the user experience.  
 **Improve Metrics:** Core Web Vitals and modern performance metrics allow users to view all their performance defects in one place, measure and improve page load, interactivity and visual stability, and find and fix JavaScript errors to improve page performance.  
-**Frontend to Backend:** Integrations with Splunk APM, Infrastructure Monitoring, On-Call and ITSI help teams view endpoint uptime against backend services, the underlying infrastructure and within their incident response coordination so they can troubleshoot across their entire environment, in a single UI.  
+**front-end to back-end:** Integrations with Splunk APM, Infrastructure Monitoring, On-Call and ITSI help teams view endpoint uptime against back-end services, the underlying infrastructure and within their incident response coordination so they can troubleshoot across their entire environment, in a single UI.  
 **Detect and Alert:** Monitor and simulate end-user experiences to detect, communicate and resolve issues for APIs, service endpoints and critical business transactions before they impact customers.  
 **Business Performance:** Easily define multi-step user flows for key business transactions and start recording and testing your critical user journeys in minutes. Track and report SLAs and SLOs for uptime and performance.  
 **Filmstrips and Video Playback:** View screen recordings, film strips, and screenshots alongside modern performance scores, competitive benchmarking, and metrics to visualize artificial end-user experiences. Optimize how fast you deliver visual content, and improve page stability and interactivity to deploy better digital experiences.

content/en/s4r/2-opentelemetry/images/tree-pillars.png

@@ -19,7 +19,7 @@ This brings up the APM Performance Summary. Having this end-to-end (RUM to APM)
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * You will see **paymentservice** and **checkoutservice** are in an error state as per the screenshot above.
-* Under **Workflow Name** click on **frontend:/cart/checkout**, this will bring up the APM Service Map.
+* Under **Workflow Name** click on **front-end:/cart/checkout**, this will bring up the APM Service Map.
 
 {{% /notice %}}
 

content/en/s4r/3-initial-tour/3-apm-home/1-apm-overview.md

@@ -5,6 +5,6 @@ weight: 6
 archetype: chapter
 ---
 
-Discover the power of full end-to-end visibility by jumping from a RUM trace (frontend) to an APM trace (backend). All the services are sending telemetry (traces and spans) that Splunk Observability Cloud can visualize, analyze and use to detect anomalies and errors.
+Discover the power of full end-to-end visibility by jumping from a RUM trace (front-end) to an APM trace (back-end). All the services are sending telemetry (traces and spans) that Splunk Observability Cloud can visualize, analyze and use to detect anomalies and errors.
 
 RUM and APM are two sides of the same coin. RUM is the client-side view of the application and APM is the server-side view. In this section, we will use APM to drilldown and identify where the problem is.

content/en/s4r/3-initial-tour/5-synthetics-home/1-synthetics-overview.md

@@ -18,6 +18,10 @@ One core tenet in building the Splunk Observability Cloud is to unify telemetry
 
 The workshop uses a microservices-based application that is deployed on AWS EC2 instances. The application is a simple e-commerce application that allows users to browse products, add them to a cart, and checkout. The application is instrumented with OpenTelemetry.
 
+---
+
 **[OpenTelemetry](https://opentelemetry.io)** is a collection of tools, APIs, and software development kits (SDKs), used to instrument, generate, collect, and export telemetry data (metrics, traces, and logs) to help you analyze your software’s performance and behavior.
 
 The OpenTelemetry community is growing. As a joint project between Splunk, Google, Microsoft, Amazon, and many other organizations, it currently has the second-largest number of contributors in the Cloud Native Computing Foundation after Kubernetes.
+
+![Full Stack](images/splunk-full-stack.png)