fix terragrunt links

docs/vendors/terraform/terragrunt.md

@@ -25,7 +25,7 @@ On our runner image, we install a version of Terragrunt that will work with the
 
 ## Scope of support
 
-We're currently using Terragrunt the same way we're using Terraform, running `init`, `plan`, and `apply` commands. This means we're not supporting [executing Terraform commands on multiple modules at once](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-modules-at-once/){: rel="nofollow"} (`run-all`). This functionality was designed to operate in a very different mode and environment, and is strictly outside our scope. However, run-all is supported in our new Terragrunt native platform in Spacelift which is currently in **beta**. You can find documentation on this [here](../terragrunt/README.md).
+We're currently using Terragrunt the same way we're using Terraform, running `init`, `plan`, and `apply` commands. This means we're not supporting [executing Terraform commands on multiple modules at once](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-units-at-once/){: rel="nofollow"} (`run-all`). This functionality was designed to operate in a very different mode and environment, and is strictly outside our scope. However, run-all is supported in our new Terragrunt native platform in Spacelift which is currently in **beta**. You can find documentation on this [here](../terragrunt/README.md).
 
 We also support authentication with [Spacelift modules](./module-registry.md) by automatically filling the `TG_TF_REGISTRY_TOKEN` environment variable for each run. Terragrunt [uses this variable](https://terragrunt.gruntwork.io/docs/reference/config-blocks-and-attributes/){: rel="nofollow"} to authenticate with private module registries.
 

docs/vendors/terragrunt/reference.md

@@ -6,7 +6,7 @@ description: Details about all available Terragrunt-specific configuration optio
 
 ## Stack Settings
 
-- **Use Run All** - If Spacelift should use Terragrunt's [run-all](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-modules-at-once/){: rel="nofollow"} functionality in this stack.
+- **Use Run All** - If Spacelift should use Terragrunt's [run-all](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-units-at-once/#the-run-all-command){: rel="nofollow"} functionality in this stack.
 - **Smart Sanitization** - If Spacelift should use [Smart Sanitization](../terraform/resource-sanitization.md#smart-sanitization) for the resources and outputs generated by this stack.
 - **Terragrunt Version** - Which version or range of versions of Terragrunt should be used
 - **Tool** - Whether to use OpenTofu, an open source version of Terraform, or a manually provisioned tool.

docs/vendors/terragrunt/run-all.md

@@ -6,7 +6,7 @@ description: Details about using run-all based Terragrunt stacks in spacelift.
 
 ## Introduction
 
-Terragrunt's [run-all](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-modules-at-once/){: rel="nofollow"} feature allows you to deploy multiple modules at the same time. This very powerful feature allows you to develop large amounts of infrastructure as code with dependencies, mocked values, and while keeping things [DRY](https://terragrunt.gruntwork.io/docs/features/keep-your-terraform-code-dry/){: rel="nofollow"}.
+Terragrunt's [run-all](https://terragrunt.gruntwork.io/docs/features/execute-terraform-commands-on-multiple-units-at-once/#the-run-all-command){: rel="nofollow"} feature allows you to deploy multiple modules at the same time. This very powerful feature allows you to develop large amounts of infrastructure as code with dependencies, mocked values, and while keeping things [DRY](https://terragrunt.gruntwork.io/docs/features/keep-your-terraform-code-dry/){: rel="nofollow"}.
 
 ## How to use run-all