DEV-671 - retitle the tg env var page to be more usecase focused

Author: ZachGoldberg

docs/2.0/docs/pipelines/guides/terragrunt-env-vars.md

@@ -1,8 +1,8 @@
-# Passing Additional Environment Variables to Terragrunt
+# Leveraging advanced Terragrunt Features
 
 ## Introduction
 
-When Pipelines detects changes to IaC in your infrastructure repositories it will invoke `terragrunt` with a specific set of command line arguments for the detected change. For example for a change to a single unit in a pull request pipelines will chdir into the unit directory and invoke `terragrunt plan --terragrunt-non-interactive`.
+When Pipelines detects changes to IaC in your infrastructure repositories it will invoke `terragrunt` with a specific set of command line arguments for the detected change. For example for a change to a single unit in a pull request pipelines will `chdir` into the unit directory and invoke `terragrunt plan --terragrunt-non-interactive`.
 
 You can inspect the specific command in different scenarios by viewing the logs for a Pipelines workflow run.
 

sidebars/docs.js

@@ -300,7 +300,7 @@ const sidebar = [
         id: "2.0/docs/pipelines/guides/running-drift-detection",
       },
       {
-        label: "Passing Additional Environment Variables to Terragrunt",
+        label: "Leveraging advanced Terragrunt Features",
         type: "doc",
         id: "2.0/docs/pipelines/guides/terragrunt-env-vars",
       },