Complete options refactoring

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

@@ -7,7 +7,7 @@ weight: 13
 The Defender Plan policy is enabled by default. If you want to turn off individual Defender plans, you can follow these steps:
 
 1. Update the `management_group_settings.policy_assignments_to_modify` section.
-1. Find the `Deploy-MDFC-Config-H224` key and set the enforcement mode of the individual Defender plans to `DoNotEnforce`. See the following example to turn off a subset the Defender plans:
+1. Find the `Deploy-MDFC-Config-H224` block setting and set the enforcement mode of the individual Defender plan line settings to `DoNotEnforce`. See the following example to turn off a subset the Defender plans:
 
     {{< highlight terraform "linenos=table" >}}
     management_group_settings = {

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

@@ -6,6 +6,6 @@ weight: 8
 
 The example configuration files that include connectivity include an out of the box set of ip address ranges. These ranges have been chosen to support a real world scenario with optimal use to avoid ip exhaustion as you scale. However you may not want to use these ranges if they may overlap with their existing ranges or they are planning to scale beyond the /16 per region we cater for.
 
-In order to update the IP ranges, you can update the `custom_replacements.names` section that includes the IP ranges. For example if you prefer to use `172.16` or `192.168`, they could update the ranges as follows:
+In order to update the IP ranges, you can update the `custom_replacements` > `names` block setting that includes the IP ranges. For example if you prefer to use `172.16` or `192.168`, they could update the ranges as follows:
 
 {{< include file="/static/examples/tf/accelerator/config/custom_replacements.names.ip_ranges.tfvars" language="terraform" >}}