Removed reference to configuring environment variables

Author: rcastley

content/en/apm/online-boutique/_index.md

@@ -19,7 +19,7 @@ description: Verify the Online Boutique application is deployed into Kubernetes
 
 This workshop module assumes you are completing this after you have run the IM workshop, and still have access to your EC2 instance.
 
-If this is the case, continue with [Deploy Online Boutique](#2-deploy-online-boutique), otherwise if you have received a fresh instance, please run the first two (2) sections of [Deploy the OTel Collector](../../imt/gdi/) to get the system ready for the APM workshop, then continue with the next section.
+If this is the case, continue with [**Deploy Online Boutique**](#2-deploy-online-boutique), otherwise, if you have received a fresh instance, please run the first two (2) sections of [**Deploy the OTel Collector**](../../imt/gdi/) to get the system ready for the APM workshop, then continue with the next section.
 
 ## 2. Deploy Online Boutique
 
@@ -125,20 +125,21 @@ Use the **Cluster** dropdown to select the cluster name, you will see the new po
 
 ![Back to cluster](../images/online-boutique-k8s.png)
 
-If you select the **WORKLOADS** tab again you should now see that there are a number of Deployments and ReplicaSets:
+If you select the **WORKLOADS** tab again you should now see that there are some Deployments and ReplicaSets:
 
 ![Online Boutique loaded](../images/online-boutique-workload.png)
 
 ## Visit the Online Boutique
 
 {{% expand title="{{% badge style=primary icon=user-ninja %}}**Ninja** - Visit the Online Boutique you just deployed{{% /badge %}}" %}}
 {{% notice style="blue" %}}
+
 The Online Boutique is viewable on port 81 of the EC2 instance's IP address. The IP address is the one you used to SSH into the instance at the beginning of the workshop.
 
 Open your web browser and go to `http://<ec2-ip-address>:81/` where you will then be able to see the Online Boutique running.
 {{% /notice %}}
 {{% /expand %}}
 
-Your Workshop instructor will provide you with URL to access the Online Boutique. Enter this URL into your browser and you will see the Online Boutique homepage.
+Your Workshop instructor will provide you with a URL to access the Online Boutique. Enter this URL into your browser and you will see the Online Boutique homepage.
 
 ![Online Boutique](../images/online-boutique.png)

content/en/imt/gdi/_index.md

@@ -13,47 +13,9 @@ weight: 2
 
 ---
 
-## 1. Obtain Access Token
+## 1. Installation using Helm
 
-You will need to obtain your Access Token[^1] from the Splunk UI. You can find the workshop Access Token by clicking **>>** bottom left and then selecting **Settings → Access Tokens**.
-
-Expand the workshop token that your host has instructed you to use e.g. **O11y-Workshop-ACCESS**, then click on **Show Token** to expose your token. Click the {{% button style="grey" %}}Copy{{% /button %}} button to copy to clipboard. Please do not use the **Default** token!
-
-![Access Token](../images/access-token.png)
-
-{{% notice title="Please do not attempt to create your own token" style="warning" %}}
-We have created a Token specifically for this workshop with the appropriate settings for the exercises you will be performing so have allocated it both Ingest and API Permissions.  Best practice in production is to only allocate a single permission to a Token such as Ingest OR API OR RUM and use multiple Tokens where required.
-{{% /notice %}}
-
-You will also need to obtain the name of the Realm[^2] for your Splunk account.  At the top of the side menu, click on your name. This will direct you to the **Account Settings** Page. Click the **Organizations**-tab. The Realm can be found at the top of the displayed information in the tab.  In this example it is `eu0`.
-
-![Account Settings](../images/account-settings.png)
-
-## 2. Installation using Helm
-
-Create the `ACCESS_TOKEN` and `REALM` environment variables to use in the proceeding Helm install command. For instance, if your realm is `us1`, you would type `export REALM=us1` and for `eu0` type `export REALM=eu0`.
-
-{{< tabs >}}
-{{% tab title="Export ACCESS TOKEN" %}}
-
-```bash
-export ACCESS_TOKEN="<replace_with_O11y-Workshop-ACCESS_TOKEN>"
-```
-
-{{% /tab %}}
-{{< /tabs >}}
-
-{{< tabs >}}
-{{% tab title="Export REALM" %}}
-
-```bash
-export REALM="<replace_with_REALM>"
-```
-
-{{% /tab %}}
-{{< /tabs >}}
-
-Install the OpenTelemetry Collector using the Splunk Helm chart. First, add the Splunk Helm chart repository to Helm and update.
+Install the OpenTelemetry Collector using the Splunk Helm chart. First, add the Splunk Helm chart repository to Helm and update:
 
 {{< tabs >}}
 {{% tab title="Helm Repo Add" %}}

content/en/imt/monitoring-as-code/_index.md

@@ -18,9 +18,9 @@ weight: 5
 
 Monitoring as code adopts the same approach as infrastructure as code. You can manage monitoring the same way you do applications, servers, or other infrastructure components.
 
-You can use monitoring as code to build out your visualisations, what to monitor, and when to alert, among other things. This means your monitoring setup, processes, and rules can be versioned, shared, and reused.
+You can use monitoring as code to build out your visualizations, what to monitor, and when to alert, among other things. This means your monitoring setup, processes, and rules can be versioned, shared, and reused.
 
-Full documentation for the Splunk Terraform Provider is available [here](https://registry.terraform.io/providers/splunk-terraform/signalfx/latest/docs).
+Full documentation for the Splunk Terraform Provider is available [**here**](https://registry.terraform.io/providers/splunk-terraform/signalfx/latest/docs).
 
 Remaining in your AWS/EC2 instance, change into the `o11y-cloud-jumpstart` directory
 
@@ -32,25 +32,7 @@ cd ~/observability-content-contrib/integration-examples/terraform-jumpstart
 
 {{% /tab %}}
 
-The environment variables needed should already be set from [Installation using Helm](../gdi/#2-installation-using-helm). If not, create the following environment variables to use in the Terraform steps below
-
-{{% tab title="Export API TOKEN" %}}
-
-``` bash
-export API_TOKEN="<replace_with_O11y-Workshop-API_TOKEN>"
-```
-
-{{% /tab %}}
-
-{{% tab title="Export REALM" %}}
-
-``` bash
-export REALM="<replace_with_REALM>"
-```
-
-{{% /tab %}}
-
-Initialize Terraform and upgrade to the latest version of the Splunk Terraform Provider
+Initialize Terraform and upgrade to the latest version of the Splunk Terraform Provider.
 
 {{% notice title="Note: Upgrading the SignalFx Terraform Provider" style="info" %}}
 You will need to run the command below each time a new version of the Splunk Terraform Provider is released. You can track the releases on [GitHub.](https://github.com/splunk-terraform/terraform-provider-signalfx/releases)