fixes addressing review feedback

Author: MikeT-gh

landscape/how-to/install-landscape-server-on-microsoft-azure.md

@@ -1,8 +1,8 @@
 # How to install Landscape Server on Microsoft Azure
 
-This guide provides an example of how to install and set up your Landscape server on Microsoft Azure with [cloud-init](https://cloudinit.readthedocs.io/en/latest/). The instructions here can be used for both FIPS-hardened or non-hardened systems.
+This guide provides an example of how to install and set up your Landscape server on Microsoft Azure with [cloud-init](https://cloudinit.readthedocs.io/en/latest/). The instructions here can be used for standard or FIPS-compliant deployments.
 
-> **For the most up-to-date documentation on Microsoft Azure, see [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure).
+> **For the most up-to-date documentation on Microsoft Azure, see [Microsoft's Azure documentation](https://learn.microsoft.com/en-us/azure).
 
 **Contents:**
 
@@ -21,16 +21,14 @@ To install `Azure CLI`, refer to the [Install Azure CLI on Ubuntu](https://docum
 
 ### Connect `Azure` with your Microsoft Azure account
 
-The Azure CLI's default authentication method for logins uses a web browser and access token to sign in.
-
-Run the `az login` command:
+The Azure CLI's default authentication method for logins uses a web browser and access token to sign in. To login, run:
 ```
 az login
 ```
 
-If the Azure CLI can open your default browser, it initiates authorisation code flow and opens the default browser to load an Azure sign-in page.
+If the Azure CLI can open your default browser, it will open the default browser and load an Azure sign-in page for you to sign in with your Azure account. Otherwise, it will instruct you to open a browser page and enter the code displayed in your terminal.
 
-Sign in with your account credentials in the browser.
+Sign in with your account credentials in the browser. For more information on signing in with the Azure CLI, see [Microsoft's documentation on signing in interactively with the Azure CLI](https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli-interactively).
 
 
 ## Provision Azure resources and deploy
@@ -59,7 +57,7 @@ Output will be displayed in JSON format:
 
 ### Create public-ip address resource
 
-Create static IP address in the `Landscape-rg` resource group:
+Create a static IP address in the `Landscape-rg` resource group:
 ```
 az network public-ip create \
 	--resource-group Landscape-rg \
@@ -68,9 +66,9 @@ az network public-ip create \
     --allocation-method Static
 ```
 
-Output will be displayed in JSON format and will show static IP address (extract below):
+Output will be displayed in JSON format and will show a static IP address:
 ```
-"ipAddress": "34.139.255.120",
+"ipAddress": "34.XXX.XXX.XXX",
 "ipTags": [],
 "location": "eastus",
 "name": "LandscapePublicIP",
@@ -95,7 +93,7 @@ Address:	127.0.0.53#53
    
 Non-authoritative answer:
 Name:	landscape.domain.com
-Address: 34.139.255.120
+Address: 34.XXX.XXX.XXX
 ```
 
 If the address value in the `nslookup` output matches the value of the `LandscapePublicIP` static IP address, the LetsEncrypt SSL provisioning step defined in the cloud-init configuration automation template will succeed.
@@ -105,7 +103,7 @@ If the address value in the `nslookup` output matches the value of the `Landscap
 
 Before beginning the deployment process with cloud-init, you must choose which of the two cloud-init configuration automation templates you want to use. In the [Landscape Scripts](https://github.com/canonical/landscape-scripts) Github repository, there are two Landscape Quickstart cloud-init configuration templates: [`cloud-init-quickstart.yaml`](https://github.com/canonical/landscape-scripts/blob/main/provisioning/cloud-init-quickstart.yaml) and [`cloud-init-quickstart-fips.yaml`](https://github.com/canonical/landscape-scripts/blob/main/provisioning/cloud-init-quickstart-fips.yaml).
 
-The `cloud-init-quickstart.yaml` template is designed for anyone, and the `cloud-init-quickstart-fips.yaml` is designed for FIPS compliant deployments of Landscape Server. For more information, see [how to install FIPS hardened Landscape Server](https://ubuntu.com/landscape/docs/install-fips-hardened-landscape-server).
+The `cloud-init-quickstart.yaml` template is designed for anyone, and the `cloud-init-quickstart-fips.yaml` is designed for FIPS compliant deployments of Landscape Server. For more information, see [how to install FIPS-compliant Landscape Server](https://ubuntu.com/landscape/docs/install-fips-hardened-landscape-server).
 
 Once you’ve chosen your configuration template, complete the following steps.
 
@@ -138,7 +136,6 @@ az vm create \
     --image $IMAGE_FAMILY \
     --size Standard_D2s_v3 \
     --admin-username azureuser \
-    --assign-identity \
     --generate-ssh-keys \
     --public-ip-address LandscapePublicIP \
     --custom-data cloud-init.yaml
@@ -149,17 +146,17 @@ az vm open-port \
 	--priority 100
 ```
 
-It takes a few minutes to create the VM and supporting resources.
+It usually takes a few minutes to create the VM and supporting resources.
 
 > [!NOTE]
-When creating the VM an error may occur with the code `MarketplacePurchaseEligibilityFailed`. This error indicates that before the subscription can use this image, you need to accept the legal terms of the image. Viewing and accepting the terms can be done via the Azure CLI. Refer to Microsoft Azure documentation [az vm image terms](https://learn.microsoft.com/en-us/cli/azure/vm/image/terms).
+When creating the VM an error may occur with the code `MarketplacePurchaseEligibilityFailed`. This error indicates that before the subscription can use this image, you need to accept the legal terms of the image. You can view and accept the terms via the Azure CLI. Refer to [Microsoft's documentation on VM image terms](https://learn.microsoft.com/en-us/cli/azure/vm/image/terms).
 
 Observe the process by tailing the `cloud-init-output.log` file. Replace `{landscape.domain.com}` with your FQDN or static IP address:
 ```
 ssh azureuser@{landscape.domain.com} 'tail -f /var/log/cloud-init-output.log'
 ```
 
-A reboot may be required during the cloud-init process. If a reboot is required, you’ll receive the following output:
+A reboot may be required during the cloud-init process. If a reboot is required, you’ll receive output similar to:
 ```
 2023-08-20 17:30:04,721 - cc_package_update_upgrade_install.py[WARNING]: Rebooting after upgrade or install per /var/run/reboot-required
 ```
@@ -171,7 +168,7 @@ Repeat the following code if a reboot was necessary to continue observing the lo
 ssh azureuser@{landscape.domain.com} 'tail -f /var/log/cloud-init-output.log'
 ```
 
-Wait until the cloud-init process is complete. When it’s complete, you’ll receive the following line similar to this:
+Wait until the cloud-init process is complete. When it’s complete, you’ll receive output similar to:
 ```
 cloud-init v. 23.2.2-0ubuntu0~22.04.1 finished at Sun, 20 Aug 2023 17:30:56 +0000. Datasource DataSourceAzure [seed=/dev/sr0].  Up 37.35 seconds
 ```
@@ -181,7 +178,7 @@ Press `CTRL + C` to terminate the tail process in your terminal window.
 
 ## Configure Landscape
 
-1. Navigate to the Landscape dashboard by entering the FQDN of the Landscape VM into a browser window
+1. Navigate to the Landscape web portal by entering the FQDN of the Landscape VM into a browser window
 
 2. Provide a name, email address, and password for the first global administrator on the machine.