Apply suggestions from code review

Author: KarlErickson

articles/virtual-machines/workloads/oracle/weblogic-server-azure-virtual-machine.md

@@ -1,5 +1,5 @@
 ---
-title: "Quickstart: Deploy WebLogic Server on Azure virtual machine (VM)"
+title: "Quickstart: Deploy WebLogic Server on Azure Virtual Machines (VMs)"
 description: Shows how to quickly stand up WebLogic Server on Azure Virtual Machine.
 author: KarlErickson
 ms.author: haiche
@@ -9,7 +9,7 @@ ms.service: oracle-on-azure
 ms.custom: devx-track-java, devx-track-javaee, devx-track-javaee-wls, devx-track-javaee-wls-vm, devx-track-extended-java
 ---
 
-# Quickstart: Deploy WebLogic Server on Azure virtual machine (VM)
+# Quickstart: Deploy WebLogic Server on Azure Virtual Machines (VMs)
 
 This article shows you how to quickly deploy WebLogic Application Server (WLS) on Azure Virtual Machines (VM) with the simplest possible set of configuration choices using the Azure portal. For a more full featured tutorial, including the use of Azure Application Gateway to make WLS cluster on VM securely visible on the public internet, see [Tutorial: Migrate a WebLogic Server cluster to Azure with Azure Application Gateway as a load balancer](/azure/developer/java/migration/migrate-weblogic-with-app-gateway?toc=/azure/virtual-machines/workloads/oracle/toc.json&bc=/azure/virtual-machines/workloads/oracle/breadcrumb/toc.json).
 
@@ -82,8 +82,8 @@ If you navigated away from the **Deployment is in progress** page, the following
    :::image type="content" source="media/weblogic-server-azure-virtual-machine/resource-group-deployments.png" alt-text="Screenshot of the Azure portal that shows the resource group deployments list." lightbox="media/weblogic-server-azure-virtual-machine/resource-group-deployments.png":::
 
 1. In the left panel, select **Outputs**. This list shows the output values from the deployment. Useful information is included in the outputs.
-1. The **sshCommand** value is the fully qualified, SSH command to connect the VM that runs WLS. Select the copy icon next to the field value and copy the link to your clipboard. Save this value aside for later.
-1. The **adminConsoleURL** value is the fully qualified, public internet visible link to the WLS admin console. Select the copy icon next to the field value and copy the link to your clipboard. Save this value aside for later.
+1. The **sshCommand** value is the fully qualified, SSH command to connect the VM that runs WLS. Select the copy icon next to the field value to copy the link to your clipboard. Save this value aside for later.
+1. The **adminConsoleURL** value is the fully qualified, public internet visible link to the WLS admin console. Select the copy icon next to the field value to copy the link to your clipboard. Save this value aside for later.
 
 ## Deploy a Java EE application from Administration Console portal
 
@@ -111,7 +111,7 @@ Use the following steps to run a sample application in the WLS:
 
 1. Under **Change Center** on the top left corner, select **Activate Changes**. You can see the message **All changes have been activated. No restarts are necessary**.
 
-1. Under **Summary of Deployments**, select **Control**. Select the checkbox near the application name and select the application. Select **Start** and then select **Servicing all requests**.
+1. Under **Summary of Deployments**, select **Control**. Select the checkbox near the application name to select the application. Select **Start** and then select **Servicing all requests**.
 
 1. Under **Start Application Assistant**, select **Yes**. If no error happens, you can see the message **Start requests have been sent to the selected deployments.**
 
@@ -125,7 +125,7 @@ Use the following steps to run a sample application in the WLS:
 
 If you want to manage the VM, you can connect to it with SSH command. Before accessing the machine, make sure you enabled port 22 for the SSH agent.
 
-The following steps enable port 22:
+Use the following steps to enable port 22:
 
 1. Navigate back to your working resource group. In the overview page, you can find a network security group named **wls-nsg**. Select **wls-nsg**.
 1. In the left panel, select **Settings**, then **Inbound security rules**. If there's a rule to allow port `22`, then you can jump to step 4.