From 9928441800c7efa9705c7968b45aa2ff1ade1641 Mon Sep 17 00:00:00 2001
From: Lee Van Ginkel <65776483+lvangink@users.noreply.github.com>
Date: Mon, 11 Sep 2023 16:17:43 -0700
Subject: [PATCH] Update pipeline.md

---
 docs/pipeline.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/pipeline.md b/docs/pipeline.md
index 3573b5a..b7f5620 100644
--- a/docs/pipeline.md
+++ b/docs/pipeline.md
@@ -4,9 +4,9 @@
 * [Topology Creation](topology.md)
 * [Data Harvest](dataharvest.md)
 * [Pipeline Deployment](pipeline.md)
-   * [Environment Variables]
+   * [Environment Variables](#environment-variables)
    * [Pipeline File (Optional)]
-   * [Pipeline Creation]
+   * [Pipeline Creation](#pipeline-creation)
 * [Data Validation](validation.md)
 * [Stateful Checks](check.md)
 * [Telemetry Collection](telemetry.md)
@@ -17,7 +17,7 @@ Now that we have deployed our production network and created our source-of-truth
 
 Note: In the instructor led class, the repository will already be created for you and we will be working with GitLab from the start. If you are doing this outside of the instructure led class, cloneing from GitHub and pushing to GitLab, you will need to do the following:
 
-### Modify Environment Variables
+### Environment Variables
 
 Before commiting your data to git, login and verify your environment variables are set. Much like our environment variables we set for our endpoint, GitLab needs to know how to access CML since it will be making changes on your behalf when the pipeline runs.