Misc updates

Author: KimForss

articles/virtual-machines/workloads/sap/automation-configure-control-plane.md

@@ -19,7 +19,7 @@ The control plane for the [SAP deployment automation framework on Azure](automat
 
 ## Deployer
 
-The [deployer](automation-deployment-framework.md#deployment-components) is the execution engine of the [SAP automation framework](automation-deployment-framework.md). It is a pre-configured virtual machine (VM) that is used for executing Terraform and Ansible commands. 
+The [deployer](automation-deployment-framework.md#deployment-components) is the execution engine of the [SAP automation framework](automation-deployment-framework.md). It's a pre-configured virtual machine (VM) that is used for executing Terraform and Ansible commands. 
 
 The configuration of the deployer is performed in a Terraform tfvars variable file.
 
@@ -159,21 +159,29 @@ The table below defines the parameters used for defining the Key Vault informati
 
 ### Example parameters file for deployer (required parameters only)
 
-```bash
+```terraform
 # The environment value is a mandatory field, it is used for partitioning the environments, for example (PROD and NP)
 environment="MGMT"
+
 # The location/region value is a mandatory field, it is used to control where the resources are deployed
 location="westeurope"
 
 # management_network_address_space is the address space for management virtual network
 management_network_address_space="10.10.20.0/25"
+
 # management_subnet_address_prefix is the address prefix for the management subnet
 management_subnet_address_prefix="10.10.20.64/28"
+
 # management_firewall_subnet_address_prefix is the address prefix for the firewall subnet
 management_firewall_subnet_address_prefix="10.10.20.0/26"
 
+# management_bastion_subnet_address_prefix is a mandatory parameter if bastion is deployed and if the subnets are not defined in the workload or if existing subnets are not used
+management_bastion_subnet_address_prefix = "10.10.20.128/26"
+
 deployer_enable_public_ip=false
+
 firewall_deployment=true
+
 bastion_deployment=true
 ```
 
@@ -253,15 +261,19 @@ The table below contains the parameters that define the resource group and the r
 
 ### Example parameters file for sap library (required parameters only)
 
-```bash
+```terraform
 # The environment value is a mandatory field, it is used for partitioning the environments, for example (PROD and NP)
 environment="MGMT"
+
 # The location/region value is a mandatory field, it is used to control where the resources are deployed
 location="westeurope"
+
 # The deployer_environment value is a mandatory field, it is used for identifying the deployer
 deployer_environment="MGMT"
+
 # The deployer_location value is a mandatory field, it is used for identifying the deployer
 deployer_location="westeurope"
+
 # The deployer_vnet value is a mandatory field, it is used for identifying the deployer
 deployer_vnet="DEP00"
 

articles/virtual-machines/workloads/sap/automation-configure-system.md

@@ -29,7 +29,8 @@ The automation framework can be used to deploy the following SAP architectures:
 
 ### Standalone
 
-In the Standalone architecture all the SAP roles are installed on a single server. 
+In the Standalone architecture, all the SAP roles are installed on a single server. 
+
 
 To configure this topology, define the database tier values and set `enable_app_tier_deployment` to false.
 
@@ -40,7 +41,7 @@ To configure this topology, define the database tier values and define `scs_serv
 
 ### High Availability
 
-The Distributed (Highly Available) deployment is similar to the Distributed architecture but either the database or SAP Central Services are both highly available using two virtual machines each with Pacemaker clusters.
+The Distributed (Highly Available) deployment is similar to the Distributed architecture. In this deployment, the database and/or SAP Central Services can both be configured using a highly available configuration using two virtual machines each with Pacemaker clusters.
 
 To configure this topology, define the database tier values and set `database_high_availability` to true. Set `scs_server_count = 1` and `scs_high_availability` = true and 
 `application_server_count` >= 1
@@ -192,7 +193,7 @@ The application tier defines the infrastructure for the application tier, which
 
 ## Network parameters
 
-If the subnets are not deployed using the workload zone deployment, they can be added in the system's tfvars file.
+If the subnets aren't deployed using the workload zone deployment, they can be added in the system's tfvars file.
 
 The automation framework can either deploy the virtual network and the subnets (green field deployment) or using an existing virtual network and existing subnets (brown field deployments).
  - For the green field scenario, the virtual network address space and the subnet address prefixes must be specified
@@ -335,7 +336,9 @@ By default the SAP System deployment uses the credentials from the SAP Workload
 
 ## Oracle parameters
 
-When deploying Oracle based systems these parameters need to be updated in the sap-parameters.yaml file.
+> [!NOTE]
+> These parameters need to be updated in the sap-parameters.yaml file when deploying Oracle based systems.
+
 
 > [!div class="mx-tdCol2BreakAll "]
 > | Variable                           | Description                                                            | Type         | Notes  |

articles/virtual-machines/workloads/sap/automation-configure-workload-zone.md

@@ -54,7 +54,7 @@ The table below contains the parameters that define the resource group.
 
 ## Network Parameters
 
-The automation framework supports both creating the virtual network and the subnets For green field deployments. (Green field) or using an existing virtual network and existing subnets For brown field deployments. (Brown field) or a combination of For green field deployments.  and For brown field deployments..
+The automation framework supports both creating the virtual network and the subnets For green field deployments. (Green field) or using an existing virtual network and existing subnets For brown field deployments. (Brown field) or a combination of For green field deployments.  and For brown field deployments.
  - For the green field scenario, the virtual network address space and the subnet address prefixes must be specified 
  - For the brown field scenario, the Azure resource identifier for the virtual network and the subnets must be specified
 
@@ -143,7 +143,6 @@ automation_username = "azureadm"
 
 ## Key Vault Parameters
 
-
 The table below defines the parameters used for defining the Key Vault information
 
 > [!div class="mx-tdCol2BreakAll "]
@@ -153,7 +152,7 @@ The table below defines the parameters used for defining the Key Vault informati
 > | `spn_keyvault_id`                  | Azure resource identifier for the deployment credentials (SPNs) key vault | Optional	   | 
 
 
-## DNS
+## Private DNS
 
 
 > [!div class="mx-tdCol2BreakAll "]

articles/virtual-machines/workloads/sap/automation-deployment-framework.md

@@ -141,3 +141,8 @@ The following diagram shows the relationships between SAP systems, workload zone
 
 > [!div class="nextstepaction"]
 > [Get started with the deployment automation framework](automation-get-started.md)
+> [Configuring Azure DevOps for the automation framwework](automation-configure-devops.md)
+> [Configuring the control plane](automation-configure-control-plane.md)
+> [Configuring the workload zone](automation-configure-workload-zone.md)
+> [Configuring the SAP System](automation-configure-system.md)
+