From adcc2e8cc991c12a13c50849ac19ba790e0d375d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javier=20Ruiz=20Jim=C3=A9nez?= Date: Thu, 7 Mar 2024 16:34:51 +0800 Subject: [PATCH] Fix typo in what-why-how.md (#721) --- docs/content/concepts/what-why-how.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/concepts/what-why-how.md b/docs/content/concepts/what-why-how.md index d29e4ace7..519c63017 100644 --- a/docs/content/concepts/what-why-how.md +++ b/docs/content/concepts/what-why-how.md @@ -51,8 +51,8 @@ We also know, from our customers, that well defined support statements from Micr Azure Verified Modules will achieve this, and its mission statement, by implementing and enforcing the following; driven by the AVM Core Team: 1. Publishing AVM modules to their respective public registries for consumption - - For Bicep this will the [Bicep Public Module Registry](https://aka.ms/BRM) - - For Terraform this will the [HashiCorp Terraform Registry](https://registry.terraform.io/) + - For Bicep this will be the [Bicep Public Module Registry](https://aka.ms/BRM) + - For Terraform this will be the [HashiCorp Terraform Registry](https://registry.terraform.io/) 2. Creating, publishing and maintaining the Azure Verified Modules specifications (this site) - Including IaC language specific specifications (today Bicep and Terraform) 3. Creating easy to follow AVM module contribution and publishing guidance for each IaC language (today Bicep and Terraform)