From 26d8092f038fb674a2cea39a0636dbe2941dfdcc Mon Sep 17 00:00:00 2001 From: Chris Griggs Date: Tue, 28 Jan 2020 10:51:40 -0800 Subject: [PATCH] [Website] Verified module update --- website/docs/registry/modules/verified.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/registry/modules/verified.html.md b/website/docs/registry/modules/verified.html.md index d7ff853ac..90dacdf8c 100644 --- a/website/docs/registry/modules/verified.html.md +++ b/website/docs/registry/modules/verified.html.md @@ -16,8 +16,8 @@ The blue verification badge appears next to modules that are verified. ![Verified module listing](/assets/images/docs/registry-verified.png) -If a module is verified, it is promised to be actively maintained and of -high quality. It isn't indicative of flexibility or feature support; very +Verified modules are expected to be actively maintained by the Cloud providers. +The verified badge isn’t indicative of flexibility or feature support; very simple modules can be verified just because they're great examples of modules. Likewise, an unverified module could be extremely high quality and actively maintained. An unverified module shouldn't be assumed to be poor quality, it