Formatting fixes

Author: rcastley

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

@@ -5,14 +5,14 @@ weight: 2
 time: 5 minutes
 ---
 
-The diagram below details the architecture of the Spring PetClinic Java application running in Kubernetes with the Splunk OpenTelemetry Operator and automatic discovery and configuration enabled.
-
 The Spring PetClinic Java application is a simple microservices application that consists of a frontend and backend services. The frontend service is a Spring Boot application that serves a web interface to interact with the backend services. The backend services are Spring Boot applications that serve RESTful API's to interact with a MySQL database.
 
 By the end of this workshop, you will have a better understanding of how to enable **automatic discovery and configuration** for your Java-based applications running in Kubernetes.
 
+The diagram below details the architecture of the Spring PetClinic Java application running in Kubernetes with the Splunk OpenTelemetry Operator and automatic discovery and configuration enabled.
+
 ![Splunk Otel Architecture](../images/auto-instrumentation-java-diagram.png)
 
 ---
 
-Based on the [**example**](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/examples/enable-operator-and-auto-instrumentation/spring-petclinic-java.md) **Josh Voravong** has created.
+Based on the [**example**](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/examples/enable-operator-and-auto-instrumentation/spring-petclinic-java.md) **Josh Voravong** created.

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

@@ -51,10 +51,7 @@ helm install splunk-otel-collector \
 --set="splunkObservability.realm=$REALM" \
 --set="splunkObservability.accessToken=$ACCESS_TOKEN" \
 --set="clusterName=$INSTANCE-k3s-cluster" \
---set="splunkObservability.logsEnabled=false" \
---set="logsEngine=otel" \
 --set="splunkObservability.profilingEnabled=true" \
---set="splunkObservability.infrastructureMonitoringEventsEnabled=true" \
 --set="environment=$INSTANCE-workshop" \
 --set="splunkPlatform.endpoint=$HEC_URL" \
 --set="splunkPlatform.token=$HEC_TOKEN" \
@@ -136,11 +133,10 @@ kubectl logs -l app=splunk-otel-collector -f --container otel-collector
 {{% /tab %}}
 {{< /tabs >}}
 
-{{% notice title="Deleting a failed installation" style="info" %}}
-If you make an error installing the OpenTelemetry Collector you can start over by deleting the installation with the following command:
-
-``` sh
-helm delete splunk-otel-collector
-```
-
-{{% /notice %}}
+>[!INFO] Deleting a failed installation
+>If you make an error installing the OpenTelemetry Collector you can start over by deleting the
+>installation with the following command:
+>
+>``` bash
+>helm delete splunk-otel-collector
+>```

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

@@ -53,11 +53,11 @@ Please make a note of the `INSTANCE` environment variable value as this will use
 
 For this workshop, **all** of the above are required. If any have values missing, please contact your Instructor.
 
-{{% notice title="Delete any existing OpenTelemetry Collectors" style="warning" %}}
-If you have previously completed a Splunk Observability workshop using this EC2 instance, you need to ensure that any existing installation of the Splunk OpenTelemetry Collector is deleted. This can be achieved by running the following command:
-
-``` bash
-helm delete splunk-otel-collector
-```
-
-{{% /notice %}}
+> [!SPLUNK] Delete any existing OpenTelemetry Collectors
+>If you have previously completed a Splunk Observability workshop using this EC2 instance, you
+>need to ensure that any existing installation of the Splunk OpenTelemetry Collector is
+>deleted. This can be achieved by running the following command:
+>
+>``` bash
+>helm delete splunk-otel-collector
+>```

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

@@ -4,7 +4,6 @@ linkTitle: PetClinic Kubernetes Workshop
 weight: 2
 archetype: chapter
 description: Learn how to enable automatic discovery and configuration for your Java-based application running in Kubernetes. Experience real-time monitoring to help you maximize application behavior with end-to-end visibility.
-authors: ["Pieter Hagen"]
 time: 90 minutes
 ---
 
@@ -14,13 +13,11 @@ The workshop scenario will be created by installing a simple (**un-instrumented*
 
 By following the simple steps to install the Splunk OpenTelemetry Collector and enabling automatic discovery and configuration for existing Java based deployments you will learn how easy it is to send metrics, traces and logs to **Splunk Observability Cloud**.
 
-{{% notice title="Prerequisites" style="primary" icon="info" %}}
-
-* Outbound SSH access to port **2222**.
-* Outbound HTTP access to port **81**.
-* Familiarity with the Linux command line.
-
-{{% /notice %}}
+> [!SPLUNK]Prerequisites
+>
+> * Outbound SSH access to port **2222**.
+> * Outbound HTTP access to port **81**.
+> * Familiarity with the Linux command line.
 
 During this workshop we will cover the following components: