diff --git a/src/SUMMARY.md b/src/SUMMARY.md
index a57e656..5f604c7 100644
--- a/src/SUMMARY.md
+++ b/src/SUMMARY.md
@@ -15,7 +15,6 @@
     - [Installation](./install/local/install.md)
       - [Semi-automated Install](./install/local/semiautomated-install.md)
       - [Automated Install](./install/local/automated-install.md)
-    - [Configure](./install/local/configure.md)
     - [Verify](./install/local/verify.md)
     - [Validate Data Flow](./install/local/validate.md)
     - [Life Cycle Management](./install/local/lifecycle/overview.md)
diff --git a/src/install/local/automated-install.md b/src/install/local/automated-install.md
index bb45ba1..ee7136a 100644
--- a/src/install/local/automated-install.md
+++ b/src/install/local/automated-install.md
@@ -29,4 +29,4 @@ make -f ./make/Makefile-local-recipes create-mdai
 ----
 
 <span class="left"><a href="./semiautomated-install.md">⏪ Back to Semi-Automated Install</a></span>
-<span class="right"><a href="./configure.md">Next Step: Configure ⏩</a></span>
+<span class="right"><a href="./verify.md">Next Step: Verify ⏩</a></span>
diff --git a/src/install/local/configure.md b/src/install/local/configure.md
deleted file mode 100644
index fb1319d..0000000
--- a/src/install/local/configure.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# ⏲️ Time to Configure OpenTelemetry! 📈
-
-Let's update your MDAI Cluster's OTel configuration file.
-
-🤔 You've got a couple options...
-
-## Option 1 - 👢 Bootstrap our built-in Collector Configuration
-
-We have provided a default configuration for a simplified version of the OpenTelemetry collector at `values/otelcol-config.yaml`. Using our boilerplate can accelerate your deployment and configuration using OpenTelemetry.
-
-*MOARRR CHOICES!*
-
-You can...
-1. Use the config as is to accelerate through configuration
-2. Making modifications right now that better fit your pipeline needs
-
-Learn more about the specifications for the [OTEL Collector](https://opentelemetry.io/docs/collector/) to make the best decisions for your telemetry pipelines configuration needs.
-
-
-## Option 2 - 🧳 Bring Your Own Configuration
-Want to use a custom or tried-and-true OTel configuration file that already works for you?
-
-Simply update the configuration file at `values/otel-config.yaml`.
-
-
-## Apply change
-
-After you've configured you OTel pipelines to your heart's desire, you can apply your changes by running
-
-```shell
-# Update config file within the cluster directory, it will get applied to your cluster instance automatically via a k8s operator.
-kubectl apply -f values/otel-config.yaml
-```
-
-----
-<span class="left"><a href="./install.md">⏪ Back to Install</a></span>
-<span class="right"><a href="./verify.md">Next Step: Verify ⏩</a></span>
-
diff --git a/src/install/local/semiautomated-install.md b/src/install/local/semiautomated-install.md
index e6e57ba..ed149ac 100644
--- a/src/install/local/semiautomated-install.md
+++ b/src/install/local/semiautomated-install.md
@@ -35,4 +35,4 @@ make -f ./make/Makefile-local-recipes create-mdai-semi-auto
 ----
 
   <span class="left"><a href="./install.md">⏪ Back to Install</a></span>
-  <span class="right"><a href="../testing.md">Next Step: Automated Install ⏩</a></span>
+  <span class="right"><a href="./verify.md">Next Step: Verify ⏩</a></span>
diff --git a/src/install/local/verify.md b/src/install/local/verify.md
index 97ee396..c421f4b 100644
--- a/src/install/local/verify.md
+++ b/src/install/local/verify.md
@@ -29,6 +29,6 @@ You should now be able to view the MDAI Console at your newly configured port, i
 
 
 ----
-<span class="left"><a href="./configure.md">⏪ Back to Configure</a></span>
-<span class="right"><a href="../testing.md">Next Step: Generate & Collect Telemetry ⏩</a></span>
+<span class="left"><a href="./install.md">⏪ Install</a></span>
+<span class="right"><a href="../validate.md">Next Step: Validate ⏩</a></span>