From 659fb09fc1fb5cc07f9518a106d25e46aacd0a83 Mon Sep 17 00:00:00 2001 From: GoodmanBen Date: Tue, 15 Mar 2022 16:36:04 -0400 Subject: [PATCH] fix: cleaner syntax --- website/docs/language/files/override.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/docs/language/files/override.mdx b/website/docs/language/files/override.mdx index f1388df3a..3595cd5ed 100644 --- a/website/docs/language/files/override.mdx +++ b/website/docs/language/files/override.mdx @@ -154,7 +154,7 @@ original block. If both the base block and the override block both set The presence of a block defining a backend (either `cloud` or `backend`) in an override file always takes precedence over a block defining a backend in the original configuration. That is, if a `cloud` block is set within the original configuration and a `backend` block is -set in the override file, Terraform will use the `backend` block specified in the override file as the -configuration's backend upon merging. Similarly, if a `backend` block is set within the original -configuration and a `cloud` block is set in the override file, Terraform will use the `cloud` -block specified in the override file as the configuration's backend upon merging. +set in the override file, Terraform will use the `backend` block specified in the override file upon merging. +Similarly, if a `backend` block is set within the original configuration and a `cloud` block +is set in the override file, Terraform will use the `cloud` block specified in the override +file upon merging.