From 17d6b3e97535404ba126444af4becc9589f6b875 Mon Sep 17 00:00:00 2001 From: "Akira Hayashi (rin)" Date: Fri, 13 Dec 2024 01:25:53 +0900 Subject: [PATCH] Add missed close parenthesis (#3651) --- docs/_docs/01_getting-started/terminology.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_docs/01_getting-started/terminology.md b/docs/_docs/01_getting-started/terminology.md index 8306a63347..5d4f298051 100644 --- a/docs/_docs/01_getting-started/terminology.md +++ b/docs/_docs/01_getting-started/terminology.md @@ -53,7 +53,7 @@ Note that units don't technically need to call their configuration files `terrag ### Stack -A stack is a collection of units managed by Terragrunt. There is ([as of writing](https://github.com/gruntwork-io/terragrunt/issues/3313) work underway to provide a top level artifact for interacting with stacks via a `terragrunt.stack.hcl` file, but as of now, stacks are generally defined by a directory with a tree of units. Units within a stack can be dependent on each other, and can be updated in a specific order to ensure that dependencies are resolved in the correct order. +A stack is a collection of units managed by Terragrunt. There is ([as of writing](https://github.com/gruntwork-io/terragrunt/issues/3313)) work underway to provide a top level artifact for interacting with stacks via a `terragrunt.stack.hcl` file, but as of now, stacks are generally defined by a directory with a tree of units. Units within a stack can be dependent on each other, and can be updated in a specific order to ensure that dependencies are resolved in the correct order. Stacks typically represent a collection of units that need to be managed in concert.