Fix/docs hyperlinks (#4054)

* Fix broken hyperlinks in sub vending

* fix a typo

* readd accidentally removed text

---------

Co-authored-by: Berdiguly Yaylymov <byaylymov@microsoft.com>

Author: yaylymov

docs/content/sub-vending/tf/_index.md

@@ -24,4 +24,4 @@ Then to get started, look at one of the [examples](examples).
 
 [alz_reference_arch]: https://docs.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/#azure-landing-zone-architecture
 [alz_tf_module]: https://aka.ms/alz/tf
-[readme]: https://github.com/Azure/terraform-azurerm-avm-ptn-alz-sub-vending#readme
+[readme]: https://github.com/Azure/terraform-azure-avm-ptn-alz-sub-vending#readme

docs/content/sub-vending/tf/examples/_index.md

@@ -10,8 +10,8 @@ Here are some example configurations that demonstrate the module usage and integ
 
 | Example | Description |
 | - | - |
-| [Hub & Spoke](example-1-hub-and-spoke) | Example of how to create a landing zone with hub & spoke peering |
-| [Virtual WAN](example-2-virtual-wan) | Example of how to create a landing zone with Virtual WAN connection |
-| [Use with existing subscriptions](example-5-use-with-existing-subscriptions) | Example of how to use this module with existing landing zone subscriptions |
+| [Hub & Spoke]({{< relref "example-1-hub-and-spoke" >}}) | Example of how to create a landing zone with hub & spoke peering |
+| [Virtual WAN]({{< relref "example-2-virtual-wan" >}}) | Example of how to create a landing zone with Virtual WAN connection |
+| [Use with existing subscriptions]({{< relref "example-3-use-with-existing-subscriptions" >}}) | Example of how to use this module with existing landing zone subscriptions |
 
 [alz_tf_module]: https://aka.ms/alz/tf

docs/content/sub-vending/tf/permissions.md

@@ -13,7 +13,7 @@ Follow the examples in the function itself [here.](https://github.com/Azure/ALZ-
 ## Permissions required
 
 This module now uses a single provider - `AzAPI`.
-See [provider configuration](Provider-configuration) for more information.
+See [provider configuration]({{< relref "provider-configuration" >}}) for more information.
 
 ### Subscription sub-module
 

docs/content/sub-vending/tf/provider-configuration.md

@@ -11,7 +11,7 @@ This was done because of the design of the AzureRM v4.0 provider and its mandato
 This does not make sense for a module that is designed to create subscriptions!
 Also, this has the benefit of simplifying the module design.
 
-Also see [required permissions](Permissions) for more information.
+Also see [required permissions]({{< relref "permissions" >}}) for more information.
 
 ## AzureRM provider
 

docs/content/whats-new/_index.md

@@ -16,7 +16,7 @@ Azure landing zone IaC accelerator release notes are [HERE]({{% ref "accelerator
 
 #### Policy
 
-- **Breaking change:** we accidentally introduced a breaking change to the initiative [Enforce-Guardrails-KeyVault](https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Enforce-Guardrails-KeyVault.html) in the last policy refresh where we fixed a typo is several parameter names, changing "Hms" to "Hsm". This change has been reverted in this release to avoid breaking existing assignments and a new version of the initiative has been created [Enforce-Guardrails-KeyVault_20260203](https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Enforce-Guardrails-KeyVault_20260203.html) with the corrected parameter names.
+- **Breaking change:** we accidentally introduced a breaking change to the initiative [Enforce-Guardrails-KeyVault](https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Enforce-Guardrails-KeyVault.html) in the last policy refresh where we fixed a typo in several parameter names, changing "Hms" to "Hsm". This change has been reverted in this release to avoid breaking existing assignments and a new version of the initiative has been created [Enforce-Guardrails-KeyVault_20260203](https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Enforce-Guardrails-KeyVault_20260203.html) with the corrected parameter names.
   - **Action Required:** If you have previously assigned this initiative, please delete the existing assignment prior to deploying the updated initiative to avoid deployment failures.
 - Add `RouteServerSubnet` to default parameter values in `Deny-Subnet-Without-Nsg`, `Deny-Subnet-Without-Udr`, and `Deny-Subnet-Without-Penp` policies as Azure Route Server doesn't support these on it's subnet.