From dce91cafb4411bd61f9ed5e7ffc070be177adf45 Mon Sep 17 00:00:00 2001 From: Tim Gates Date: Sat, 2 Jul 2022 09:14:05 +1000 Subject: [PATCH] docs: Fix a few typos There are small typos in: - docs/planning-behaviors.md - docs/resource-instance-change-lifecycle.md - website/README.md Fixes: - Should read `exhaustive` rather than `exhastive`. - Should read `representation` rather than `repesentation`. - Should read `preferably` rather than `preferrably`. - Should read `absence` rather than `absense`. --- docs/planning-behaviors.md | 8 ++++---- docs/resource-instance-change-lifecycle.md | 2 +- website/README.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/planning-behaviors.md b/docs/planning-behaviors.md index c91ad41c29..ecb6fb3011 100644 --- a/docs/planning-behaviors.md +++ b/docs/planning-behaviors.md @@ -9,7 +9,7 @@ There are also some historical exceptions to this rule, which we hope to supplement with plan-and-apply-based equivalents over time. This document describes the default planning behavior of Terraform in the -absense of any special instructions, and also describes the three main +absence of any special instructions, and also describes the three main design approaches we can choose from when modelling non-default behaviors that require additional information from outside of Terraform Core. @@ -148,7 +148,7 @@ main sub-categories: top-level block which refers to other resources using the typical address syntax. -The following is a non-exhastive list of existing examples of +The following is a non-exhaustive list of existing examples of configuration-driven behaviors, selected to illustrate some different variations that might be useful inspiration for new designs: @@ -210,7 +210,7 @@ protocol does not talk about the action types explicitly, and instead only implies them via other content of the request and response, with Terraform Core making the final decision about how to react to that information. -The following is a non-exhastive list of existing examples of +The following is a non-exhaustive list of existing examples of provider-driven behaviors, selected to illustrate some different variations that might be useful inspiration for new designs: @@ -258,7 +258,7 @@ most appropriate way to handle a particular use-case, because the need for the behavior originates in some process happening outside of the scope of any particular Terraform module or provider. -The following is a non-exhastive list of existing examples of +The following is a non-exhaustive list of existing examples of single-run behaviors, selected to illustrate some different variations that might be useful inspiration for new designs: diff --git a/docs/resource-instance-change-lifecycle.md b/docs/resource-instance-change-lifecycle.md index 9be7dcdfce..0849bea628 100644 --- a/docs/resource-instance-change-lifecycle.md +++ b/docs/resource-instance-change-lifecycle.md @@ -322,7 +322,7 @@ to bring them under Terraform's management without needing to recreate them first. When using this facility, the user provides the address of the resource -instance they wish to bind the existing object to, and a string repesentation +instance they wish to bind the existing object to, and a string representation of the identifier of the existing object to be imported in a syntax defined by the provider on a per-resource-type basis, which we'll call the **Import ID**. diff --git a/website/README.md b/website/README.md index 03b60f659b..8f4a8c9d7c 100644 --- a/website/README.md +++ b/website/README.md @@ -15,7 +15,7 @@ Click **Edit this page** at the bottom of any Terraform website page to go direc ## Modifying Sidebar Navigation -Updates to the sidebar navigation of Terraform docs need to be made in the [`terraform-website`](https://github.com/hashicorp/terraform-website/) repository (preferrably in a PR also updating the submodule commit). You can read more about how to make modifications to the navigation in the [README for `terraform-website`](https://github.com/hashicorp/terraform-website#editing-navigation-sidebars). +Updates to the sidebar navigation of Terraform docs need to be made in the [`terraform-website`](https://github.com/hashicorp/terraform-website/) repository (preferably in a PR also updating the submodule commit). You can read more about how to make modifications to the navigation in the [README for `terraform-website`](https://github.com/hashicorp/terraform-website#editing-navigation-sidebars). ## Previewing Changes