From 75e676f2f2cd1d0229b289d487c08c50cec9683a Mon Sep 17 00:00:00 2001 From: Kristin Laemmert Date: Tue, 25 Aug 2020 17:03:24 -0400 Subject: [PATCH] website/docs: remove unclear provider version constraint description (#25998) --- .../docs/configuration/provider-requirements.html.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/configuration/provider-requirements.html.md b/website/docs/configuration/provider-requirements.html.md index 22d1d5eb8..0aa4aa501 100644 --- a/website/docs/configuration/provider-requirements.html.md +++ b/website/docs/configuration/provider-requirements.html.md @@ -242,11 +242,11 @@ avoiding typing. ## Version Constraints -A [source address](#source-addresses) uniquely identifies a particular -provider, but each provider can have one or more distinct _versions_, allowing -the functionality of the provider to evolve over time. Each provider dependency -you declare should have a [version constraint](./version-constraints.html) -given in the `version` argument. +Each provider plugin has its own set of available versions, allowing the +functionality of the provider to evolve over time. Each provider dependency you +declare should have a [version constraint](./version-constraints.html) given in +the `version` argument so Terraform can select a single version per provider +that all modules are compatible with. The `version` argument is optional; if omitted, Terraform will accept any version of the provider as compatible. However, we strongly recommend specifying