Refactor of Pet-Clinic workshop

Author: rcastley

content/en/pet-clinic/docs/apm.md

@@ -3,7 +3,7 @@ title: Zero Configuration Java application
 weight: 3
 ---
 
-## Spring PetClinic Application
+## 1. Spring PetClinic Application
 
 First thing we need to setup APM is... well, an application. For this exercise, we will use the Spring Pet Clinic application. This is a very popular sample java application built with Spring framework (Springboot).
 
@@ -67,7 +67,7 @@ Let's go visit our application again to generate some traffic `http://<VM_IP_ADD
 
 **Once your validation is complete you can stop the application by pressing** `Ctrl-c` **.**
 
-## Adding Resource Attributes to Spans
+## 2. Adding Resource Attributes to Spans
 
 Resource attributes can be added to every reported span. For example `version=0.314`. A comma separated list of resource attributes can also be defined e.g. `key1=val1,key2=val2`.
 

content/en/pet-clinic/docs/imt.md

@@ -1,9 +1,9 @@
 ---
-title: Install the OpenTelemetry Collector
+title: Install the OTel Collector
 weight: 2
 ---
 
-## Install The Open Telemetry Collector
+## 1. Introduction
 
 The OpenTelemetry Collector is the core component of instrumenting infrastructure and applications.  Its role is to collect and send:
 
@@ -14,6 +14,8 @@ The OpenTelemetry Collector is the core component of instrumenting infrastructur
 
 Splunk Observability Cloud offers wizards to walk you through the setup of the Collector on both your infrastructure and applications. By default, the wizard will only provide the commands to only install the collector.
 
+## 2. Configure environment variables
+
 If you have already completed the **Splunk IM** workshop you can take advantage of the existing environment variables. Otherwise, create the `ACCESS_TOKEN` and `REALM` environment variables to use in the proceeding OpenTelemetry Collector install command. For instance, if your realm is `us1`, you would type `export REALM=us1` and for `eu0` type `export REALM=eu0` etc.
 
 {{< tabpane >}}
@@ -32,6 +34,8 @@ export REALM="<replace_with_REALM>"
 If you have completed the Splunk IM workshop, please ensure you have deleted the collector running in Kubernetes before continuing. This can be done by running the following command: `helm delete splunk-otel-collector`.
 {{% /alert %}}
 
+## 3. Install the OpenTelemetry Collector
+
 We can then go ahead and install the Collector. There are two additional parameters passed to the install script, they are `--with-instrumentation` and `--deployment-environment`. The `--with-instrumentation` option the installer will install the agent from the Splunk distribution of OpenTelemetry Java, which is then loaded automatically when the Pet Clinic Java application starts up. No configuration required!
 
 ``` text

content/en/pet-clinic/docs/logobserver.md

@@ -3,11 +3,11 @@ title: Log Observer
 weight: 5
 ---
 
-## Splunk Log Observer
+## 1. Introduction
 
 For the Splunk Log Observer component, we will configure the Spring PetClinic application to write logs to a file in the filesystem and configure the Splunk OpenTelemetry Collect to read (tail) that log file and report the information to the Splunk Observability Platform.
 
-### FluentD Configuration
+## 2. FluentD Configuration
 
 We need to configure the Splunk OpenTelemetry Collector to tail the Spring Pet Clinic log file and report the data to the Splunk Observability Cloud endpoint.
 
@@ -48,7 +48,7 @@ And paste the contents from the snippet above. Once the file is created, we need
 sudo systemctl restart td-agent
 ```
 
-### PetClinic Logback Settings
+## 3. Logback Settings
 
 The Spring PetClinic application can be configure to use a number of different java logging libraries. In this scenario, we are using logback. Here's a sample logback configuration file:
 
@@ -109,6 +109,6 @@ And you can add a filter to select only log messages from your host and the Spri
 1. Add Filter → Fields → `host.name` → `<your host name>`
 2. Add Filter → Fields → `service.name` → `<your host name>-petclinic.service`
 
-### Summary
+## 4. Summary
 
 This the end of the exercise and we have certainly covered a lot of ground. At this point you should have metrics, traces, logs, database query performance and code profiling being reported into Splunk Observability Cloud. **Congratulations**!

content/en/pet-clinic/docs/rum.md

@@ -3,7 +3,7 @@ title: Real User Monitoring
 weight: 4
 ---
 
-## Splunk Real User Monitoring
+## 1. Enable RUM
 
 For the Real User Monitoring (RUM) instrumentation, we will add the Open Telemetry Javascript [https://github.com/signalfx/splunk-otel-js-web](https://github.com/signalfx/splunk-otel-js-web) snippet in the pages, we will use the wizard again **Data Management → Add Integration → RUM Instrumentation → Browser Instrumentation**.
 
@@ -41,7 +41,7 @@ vi src/main/resources/templates/fragments/layout.html
 
 and let's insert the snipped we generated above in the `<head>` section of the page. Now we need to rebuild the application and run it again:
 
-## Rebuild PetClinic
+## 2. Rebuild PetClinic
 
 run the maven command to compile/build/package PetClinic: