From 03df0c4f802240f72cc57115f4d5fe77defdef7a Mon Sep 17 00:00:00 2001
From: rita <8647768+ritsok@users.noreply.github.com>
Date: Mon, 19 May 2025 16:13:11 -0400
Subject: [PATCH] Update website/docs/language/style.mdx

---
 website/docs/language/style.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/language/style.mdx b/website/docs/language/style.mdx
index 05fa9ff69b..c873141d56 100644
--- a/website/docs/language/style.mdx
+++ b/website/docs/language/style.mdx
@@ -460,7 +460,7 @@ This section reviews standards that enable predictable and secure Terraform work
 
 To prevent provider and module upgrades from introducing unintentional changes to your infrastructure, use version pinning. 
 
-Specify provider versions using the [required_providers block](/terraform/language/providers/requirements#requiring-providers). Terraform [version constraints](/terraform/language/providers/requirements#version-constraints) supports a range of accepted versions. 
+Specify provider versions using the [required_providers block](/terraform/language/providers/requirements#requiring-providers). Terraform [version constraints](/terraform/language/providers/requirements#version-constraints) support a range of accepted versions. 
 
 Pin modules to a specific major and minor version as shown in the example below to ensure stability. You can use looser restrictions if you are certain that the module does not introduce breaking changes outside of major version updates.