diff --git a/docs/2.0/docs/pipelines/concepts/overview.md b/docs/2.0/docs/pipelines/concepts/overview.md
index 5fd3227905..bade9d9e20 100644
--- a/docs/2.0/docs/pipelines/concepts/overview.md
+++ b/docs/2.0/docs/pipelines/concepts/overview.md
@@ -17,7 +17,9 @@ Gruntwork is the creator and maintainer of [Terragrunt](https://terragrunt.grunt
 - `terragrunt plan`
 - `terragrunt apply`
 - `terragrunt destroy`
-- `terragrunt run-all`
+- `terragrunt run-all plan`
+- `terragrunt run-all apply`
+- `terragrunt run-all destroy`
 
 Gruntwork actively contributes to Terragrunt, ensuring it supports features critical to Gruntwork Pipelines.
 
@@ -25,7 +27,7 @@ Gruntwork actively contributes to Terragrunt, ensuring it supports features crit
 
 One of the things we've discovered over the years helping customers automate their infrastructure management is that it can be _very_ costly and time-consuming to build and maintain a CI/CD pipeline that can efficiently handle the complexity of infrastructure changes. Customers typically don't want to trigger an update to _all_ of their infrastructure whenever _any_ component changes, and they typically want to have related changes coordinated and rolled out correctly.
 
-A driving design goal of Gruntwork Pipelines is to allow for a minimal setup experience, followed by a very intuitive model for driving infrastructure updates. Most customers can get Pipelines configured in less than an hour, then drive all of their infrastructure changes directly via pull requests to Infrastructure as Code. Most of the time, you do not need to think about how Gruntwork Pipelines works, or how it makes decisions about what to do. You simply update your Infrastructure as Code to reflect the desired state of your infrastructure, have the pull request reviewed and merged, then Gruntwork Pipelines takes care of the rest.
+A driving design goal of Gruntwork Pipelines is to allow for a minimal setup experience, followed by a very intuitive model for driving infrastructure updates. Most customers can get Gruntwork Pipelines configured in less than an hour, then drive all of their infrastructure changes directly via pull requests to Infrastructure as Code. Most of the time, you do not need to think about how Gruntwork Pipelines works, or how it makes decisions about what to do. You simply update your Infrastructure as Code to reflect the desired state of your infrastructure, have the pull request reviewed and merged, then Gruntwork Pipelines takes care of the rest.
 
 ## Runs in GitHub Actions or GitLab CI