K8s screenshots updated

Author: rcastley

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

@@ -1,7 +1,7 @@
 ---
 title: PetClinic Monolith Workshop
 weight: 1
-description: A workshop using automatic discovery and configuration for Java.
+description: Hands-on workshop demonstrating Splunk Observability Cloud's automatic discovery and configuration capabilities for Java applications using the Spring PetClinic sample application.
 archetype: chapter
 authors: ["Robert Castley"]
 time: 30 minutes

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/3-verify-setup/_index.md

@@ -7,16 +7,18 @@ time: 10 minutes
 
 Once the installation has completed, you can log in to **Splunk Observability Cloud** and verify that the metrics are flowing in from your Kubernetes cluster.
 
-From the left-hand menu, click on **Infrastructure** and select **Kubernetes**, then select the **Kubernetes nodes** pane. Once you are in the **Kubernetes nodes** view, change the **Time** filter from **-4h** to the last 15 minutes **(-15m)** to focus on the latest data.
-
-Next, from the list of nodes, select the Node name of your workshop instance. Note: You can get the unique part from your cluster name by using the `INSTANCE` from the output from the shell script you ran earlier. **(1)**
+From the left-hand menu, click on **Infrastructure** and select **Kubernetes**, then select the **Kubernetes nodes** tile.
 
 ![NavigatorList](../images/navigatorlist.png)
 
-Open the **Hierarchy Map** by clicking on the *Hierarchy Map* link in the gray pane to show the graphical representation of your node.
+Once you are in the **Kubernetes nodes** overview, change the **Time** filter from **-4h** to the last 15 minutes **(-15m)** to focus on the latest data, then select **Table** to list all the nodes that are reporting metrics.
+
+Next, from the list of nodes, select the **Node name** of your workshop instance.
 
-![HeirarchyMap](../images/hierarchymap.png)
+{{% notice title="Tip" style="info" icon="lightbulb" %}}
+To identify your specific cluster, use the `INSTANCE` value from the shell script output you ran during setup. This unique identifier helps you locate your workshop cluster among other nodes in the list.
+{{% /notice %}}
 
-You will now only have your cluster visible. Scroll down the page to see the metrics coming in from your cluster. Locate the **Node log events rate** **(1)** chart and click on a vertical bar to see the log entries coming in from your cluster.
+You will now only have your cluster visible. Scroll down the page to see the metrics coming in from your cluster. Locate the **Node log events rate** chart and click on a vertical bar to see the log entries coming in from your cluster.
 
 ![Logs](../images/k8s-peek-at-logs.png)

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/4-apm/2-apm-data.md

@@ -4,8 +4,13 @@ linkTitle: 2. Viewing APM Data
 weight: 2
 ---
 
-In the left-hand menu click on **APM** to see the data generated by the traces from the newly instrumented services. Change the **Environment** filter **(1)** to the name of your workshop instance in the dropdown box. (Note: this will be **`<INSTANCE>-workshop`** where **`INSTANCE`** is the value from the shell script you ran earlier. Ensure it is the only one selected.)
+In the left-hand menu click on **APM** to see the data generated by the traces from the newly instrumented services.
+
+Change the **Environment** filter **(1)** to the name of your workshop instance in the dropdown box.
+
+> [!NOTE]
+> This will be **`<INSTANCE>-workshop`** where **`INSTANCE`** is the value from the shell script you ran earlier. Ensure it is the only one selected.
 
 ![apm](../../images/zero-config-first-services-overview.png)
 
-If you see a Critical Alert, you can ignore it as it is caused by the sudden request increase generated by the load generator **(2)**. Click on the **Service Map** **(3)** pane to get ready for the next section.
+Click on the **Service Map** **(2)** pane to get ready for the next section.

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/images/hierarchymap.png

@@ -37,4 +37,4 @@ In the second part, we’ll shift to alerting and monitoring with detectors:
 * Exploring alert timelines and history
 * Best practices for building actionable detectors
  -->
-<!-- {{% children containerstyle="ul" depth="1" description="true" %}} -->
+<!-- {{% children type="card" depth="1" description="true" %}} -->

content/en/ninja-workshops/1-automatic-discovery/2-petclinic-kubernetes/images/k8s-navigator-restarted-pods.png

@@ -7,7 +7,7 @@ time: 5 minutes
 
 After you have registered and logged into Splunk Observability Cloud you will be taken to the home or landing page. Here, you will find several useful features to help you get started.
 
-![home page](../images/home-screen.png)
+![home page](../images/home-page.png)
 
 1. **Expand/Contract Main Menu:** Expand **>>** / Collapse **<<** the main menu if space is at a premium.
 2. **Org Switcher:** Switch between Organizations (if you are a member of more than one Organization).
@@ -19,7 +19,7 @@ Let's start with our first exercise:
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* Click on your name in the top right and check the Organization name. 
+* Click on your name in the top right and check the Organization name.
 * If you are not in **Observability Workshop AMER**, select it now.
 * At the bottom of the menu, select your preferred appearance: **Light**, **Dark** or **Auto** mode.
 * Did you also notice this is where the **Log Out** option is? Please don't 😊 !