From a62fa224fc9a65bd6efad9a8befb32c23e53d862 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Alex=C3=A1nder=20Polanco=20Valdez?= Date: Tue, 4 Feb 2025 18:03:53 +0100 Subject: [PATCH] Fix typo version-constraints.mdx I detected a typo while reading the page. --- website/docs/language/expressions/version-constraints.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/language/expressions/version-constraints.mdx b/website/docs/language/expressions/version-constraints.mdx index a54c6f088b..9297f95b87 100644 --- a/website/docs/language/expressions/version-constraints.mdx +++ b/website/docs/language/expressions/version-constraints.mdx @@ -81,7 +81,7 @@ We recommend implementing the following best practices when configuration versio ### Module versions -- Require specific versions to ensure that updates only happen when convenient to you when your infrastructure depencds on third-party modules. +- Require specific versions to ensure that updates only happen when convenient to you when your infrastructure depends on third-party modules. - Specify version ranges when your organization consistently uses semantic versioning for modules it maintains. @@ -95,4 +95,4 @@ We recommend implementing the following best practices when configuration versio upgrade to newer versions of Terraform without altering the module. - Root modules should use a `~>` constraint to set both a lower and upper bound - on versions for each provider they depend on. \ No newline at end of file + on versions for each provider they depend on.