From d6fd12f4f98cd8a25a4b9f33d8544f5c6f5eb3b6 Mon Sep 17 00:00:00 2001 From: "John C. Bland II" Date: Wed, 21 Dec 2022 10:36:26 -0600 Subject: [PATCH] Update catalogs.md (#281) --- website/docs/core-concepts/stacks/catalogs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/core-concepts/stacks/catalogs.md b/website/docs/core-concepts/stacks/catalogs.md index f4c30b511..b299b82c5 100644 --- a/website/docs/core-concepts/stacks/catalogs.md +++ b/website/docs/core-concepts/stacks/catalogs.md @@ -162,4 +162,4 @@ For everything else, we usually have catalog that we just call `catalog/`. We pl ## Refactoring Configurations -One of the amazing things about the Atmos [Stack](/core-concepts/stacks) configurations is that the entire state of configuration is stored in the YAML configurations. The filesystem layout has no bearing on the desired state of the configuratino. This means that configurations can be easily refactored at at time in the future, if you discover there's a better way to organize your Stack configurations. So long as the deep-merged configuration is the same, it will not affect any of the [Components](/core-concepts/components). +One of the amazing things about the Atmos [Stack](/core-concepts/stacks) configurations is that the entire state of configuration is stored in the YAML configurations. The filesystem layout has no bearing on the desired state of the configuration. This means that configurations can be easily refactored at at time in the future, if you discover there's a better way to organize your Stack configurations. So long as the deep-merged configuration is the same, it will not affect any of the [Components](/core-concepts/components).