docs: fix options indentation (#18)

* docs: fix options indentation

docs/content/accelerator/startermodules/terraform-platform-landing-zone/options/ama.md

@@ -7,15 +7,15 @@ weight: 11
 The Azure Monitoring Agent (AMA) is enabled by default. If you want to turn it off, you can follow these steps:
 
 1. To keep the code tidy remove the follow settings from `custom_replacements.names`:
-  1. `ama_user_assigned_managed_identity_name`
-  1. `dcr_change_tracking_name`
-  1. `dcr_defender_sql_name`
-  1. `dcr_vm_insights_name`
+    * `ama_user_assigned_managed_identity_name`
+    * `dcr_change_tracking_name`
+    * `dcr_defender_sql_name`
+    * `dcr_vm_insights_name`
 1. To keep the code tidy remove the follow settings from `custom_replacements.resource_identifiers`:
-  1. `ama_change_tracking_data_collection_rule_id`
-  1. `ama_mdfc_sql_data_collection_rule_id`
-  1. `ama_vm_insights_data_collection_rule_id`
-  1. `ama_user_assigned_managed_identity_id`
+    * `ama_change_tracking_data_collection_rule_id`
+    * `ama_mdfc_sql_data_collection_rule_id`
+    * `ama_vm_insights_data_collection_rule_id`
+    * `ama_user_assigned_managed_identity_id`
 1. Remove the whole `user_assigned_managed_identities` section from `management_resource_settings`
 1. Remove the whole `data_collection_rules` section from `management_resource_settings`
 1. Add the follow section to `management_group_settings.policy_assignments_to_modify`:

docs/content/accelerator/startermodules/terraform-platform-landing-zone/options/bastion.md

@@ -9,7 +9,7 @@ You can choose to not deploy a Bastion Host. In order to do that, they need to r
 The steps to follow are:
 
 1. To keep the code tidy remove the follow settings from `custom_replacements.names`:
-  1. `<region>_bastion_host_name` where `<region>` is for each region
-  1. `<region>_bastion_public_ip_name` where `<region>` is for each region
-  1. `<region>_bastion_subnet_address_prefix` where `<region>` is for each region
+    * `<region>_bastion_host_name` where `<region>` is for each region
+    * `<region>_bastion_public_ip_name` where `<region>` is for each region
+    * `<region>_bastion_subnet_address_prefix` where `<region>` is for each region
 1. Remove the whole `bastion` section from each `hub_and_spoke_vnet_virtual_networks` or `virtual_wan_virtual_hubs` region

docs/content/accelerator/startermodules/terraform-platform-landing-zone/options/ddos.md

@@ -13,14 +13,14 @@ DDOS Protection plan is a critical security protection for public facing service
 The steps to follow are:
 
 1. To keep the code tidy remove the following settings from `custom_replacements.names`:
-  1. `ddos_resource_group_name`
-  1. `ddos_protection_plan_name`
+    * `ddos_resource_group_name`
+    * `ddos_protection_plan_name`
 1. To keep the code tidy remove the following settings from `custom_replacements.resource_group_identifiers`:
-  1. `ddos_protection_plan_resource_group_id`
+    * `ddos_protection_plan_resource_group_id`
 1. To keep the code tidy remove the following settings from `custom_replacements.resource_identifiers`:
-  1. `ddos_protection_plan_id`
+    * `ddos_protection_plan_id`
 1. Remove the following configuration settings from `management_group_settings.policy_default_values`:
-  1. `ddos_protection_plan_id`
+    * `ddos_protection_plan_id`
 1. Add the follow section to `management_group_settings.policy_assignments_to_modify`:
 
     {{< highlight terraform "linenos=table" >}}

docs/content/accelerator/startermodules/terraform-platform-landing-zone/options/dns.md

@@ -9,14 +9,14 @@ You can choose to not deploy any DNS related resources. In order to do that, the
 The steps to follow are:
 
 1. To keep the code tidy remove the follow settings from `custom_replacements.names`:
-  1. `dns_resource_group_name`
-  1. `<region>_private_dns_resolver_name` where `<region>` is for each region
-  1. `<region>_auto_registration_zone_name` where `<region>` is for each region
-  1. `<region>_private_dns_resolver_subnet_address_prefix` where `<region>` is for each region
+    * `dns_resource_group_name`
+    * `<region>_private_dns_resolver_name` where `<region>` is for each region
+    * `<region>_auto_registration_zone_name` where `<region>` is for each region
+    * `<region>_private_dns_resolver_subnet_address_prefix` where `<region>` is for each region
 1. Remove the follow configuration settings from `management_group_settings.policy_default_values`:
-  1. `private_dns_zone_subscription_id`
-  1. `private_dns_zone_region`
-  1. `private_dns_zone_resource_group_name`
+    * `private_dns_zone_subscription_id`
+    * `private_dns_zone_region`
+    * `private_dns_zone_resource_group_name`
 1. Add the follow section to `management_group_settings.policy_assignments_to_modify`:
 
     ```terraform

docs/content/accelerator/startermodules/terraform-platform-landing-zone/options/gateways.md

@@ -6,22 +6,32 @@ weight: 6
 
 You can choose to not deploy any Virtual Network Gateways. In order to do that, you need to remove the Virtual Network Gateway configuration. You can either comment out or remove the configuration entirely.
 
+## For both Virtual Network Gateways
+
 The steps to follow are:
 
 1.  To keep the code tidy remove the following settings from `custom_replacements.names`:
-  1. `<region>_virtual_network_gateway_express_route_name` where `<region>` is for each region
-  1. `<region>_virtual_network_gateway_express_route_public_ip_name` where `<region>` is for each region
-  1. `<region>_virtual_network_gateway_vpn_name` where `<region>` is for each region
-  1. `<region>_virtual_network_gateway_vpn_public_ip_name` where `<region>` is for each region
-  1. `<region>_gateway_subnet_address_prefix` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_express_route_name` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_express_route_public_ip_name` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_vpn_name` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_vpn_public_ip_name` where `<region>` is for each region
+    * `<region>_gateway_subnet_address_prefix` where `<region>` is for each region
 1. Remove the whole `virtual_network_gateways` section from each `hub_and_spoke_vnet_virtual_networks` or `virtual_wan_virtual_hubs` region
 
-You can also just turn off the specific Virtual Network Gateway types you don't want to deploy.
+## For ExpressRoute Virtual Network Gateways only
 
-For ExpressRoute Virtual Network Gateways:
+The steps to follow are:
 
+1.  To keep the code tidy remove the following settings from `custom_replacements.names`:
+    * `<region>_virtual_network_gateway_express_route_name` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_express_route_public_ip_name` where `<region>` is for each region
 1. Remove the whole `express_route` section from the `virtual_network_gateways` section in each `hub_and_spoke_vnet_virtual_networks` or `virtual_wan_virtual_hubs` region
 
-For VPN Virtual Network Gateways:
+## For VPN Virtual Network Gateways only
 
+The steps to follow are:
+
+1.  To keep the code tidy remove the following settings from `custom_replacements.names`:
+    * `<region>_virtual_network_gateway_vpn_name` where `<region>` is for each region
+    * `<region>_virtual_network_gateway_vpn_public_ip_name` where `<region>` is for each region
 1. Remove the whole `vpn` section from the `virtual_network_gateways` section in each `hub_and_spoke_vnet_virtual_networks` or `virtual_wan_virtual_hubs` region