From 23d2d389b72ab4a36e7dfbaca2ad8fd5e579bcdc Mon Sep 17 00:00:00 2001 From: kirici <74684021+kirici@users.noreply.github.com> Date: Mon, 10 Nov 2025 19:57:50 +0100 Subject: [PATCH] docs: fix typo --- .../v1.13.x/docs/language/meta-arguments/lifecycle.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx b/content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx index 2b96af2b0..04b8849e1 100644 --- a/content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx +++ b/content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx @@ -49,7 +49,7 @@ You can use `create_before_destroy` in [`resource`](/terraform/language/block/re When `prevent_destroy` is set to `true`, Terraform rejects plans that would destroy the infrastructure object associated with the resource and returns an error. The argument must be present in the configuration. This rule doesn't prevent Terraform from destroying a resource if you remove its configuration. Refer to [Remove a resource from state](/terraform/language/state/remove) for instructions on how to remove a resource from state without destroying the actual resource. -Use this rule as protection against accidentally replacing objects that may be costly to reproduce, such as database instances. Enabling `prevent_destory`, however, makes certain configuration changes impossible to apply +Use this rule as protection against accidentally replacing objects that may be costly to reproduce, such as database instances. Enabling `prevent_destroy`, however, makes certain configuration changes impossible to apply and prevents the `terraform destroy` command from operating once such objects are created. Use `prevent_destroy` sparingly. You can use `prevent_destroy` in in [`resource`](/terraform/language/block/resource) blocks. @@ -326,4 +326,4 @@ ephemeral "aws_ssm_parameter" "database_password" { } ``` - \ No newline at end of file +