Line edits

Author: lootle1

learn-pr/azure/create-windows-virtual-machine-in-azure/includes/2-create-a-windows-virtual-machine.md

@@ -16,12 +16,12 @@ The Azure Marketplace also provides preconfigured images that include both an OS
 
 When creating a Windows VM in Azure, you also create resources to host the VM. These resources work together to virtualize a computer and run the Windows operating system. These must either exist (and be selected during VM creation), or they'll be created with the VM.
 
-- A virtual machine that provides CPU and memory resources
-- An Azure Storage account to hold the virtual hard disks
-- Virtual disks to hold the OS, applications, and data
-- A virtual network (VNet) to connect the VM to other Azure services or your own on-premises hardware
-- A network interface to communicate with the VNet
-- A public IP address so you can access the VM (this is optional)
+- A virtual machine that provides CPU and memory resources.
+- An Azure Storage account to hold the virtual hard disks.
+- Virtual disks to hold the OS, applications, and data.
+- A virtual network (VNet) to connect the VM to other Azure services or your own on-premises hardware.
+- A network interface to communicate with the VNet.
+- A public IP address so you can access the VM (this is optional).
 
 Like other Azure services, you'll need a **resource group** to contain the VM (and optionally group these resources together for administration). When you create a new VM, you can either use an existing resource group or create a new one.
 
@@ -41,18 +41,18 @@ Just as a physical machine has a certain amount of memory and CPU power, so does
 > [!WARNING]
 > There are quota limits on each subscription that can impact VM creation. In the classic deployment model, you can't have more than 20 virtual *cores* across all VMs within a region. You can either split up VMs across regions or file an [online request](/azure/azure-supportability/resource-manager-core-quotas-request) to increase your limits.
 
-VM sizes are grouped into categories, starting with the B-series for basic testing, and running up to the H-series for massive computing tasks. You should select the VM's size based on the workload you want to perform. It's possible to change a VM's size after it's been created, but the VM must be stopped first, so it's best to size it appropriately from the start if possible.
+VM sizes are grouped into categories, starting with the B-series for basic testing, and running up to the H-series for massive computing tasks. You should select the VM's size based on the workload you want to perform. It's possible to change a VM's size after it's been created, but the VM must be stopped first. So it's best to size it appropriately from the start if possible.
 
-### Here are some guidelines based on the scenario you're targeting:
+### Here are some guidelines based on the scenario you're targeting
 
 | What are you doing? | Consider these sizes |
 |-------|------------------|
-| **General use computing/web**: Testing and development, small to medium databases, or low to medium traffic web servers | B, Dsv3, Dv3, DSv2, Dv2 |
-| **Heavy computational tasks**: Medium traffic web servers, network appliances, batch processes, and application servers | Fsv2, Fs, F |
+| **General use computing/web**: Testing and development, small to medium databases, or low to medium traffic web servers. | B, Dsv3, Dv3, DSv2, Dv2 |
+| **Heavy computational tasks**: Medium traffic web servers, network appliances, batch processes, and application servers. | Fsv2, Fs, F |
 | **Large memory usage**: Relational database servers, medium to large caches, and in-memory analytics. | Esv3, Ev3, M, GS, G, DSv2, Dv2 |
-| **Data storage and processing**: Big Data, SQL, and NoSQL databases, which need high disk throughput and IO | Ls |
-| **Heavy graphics rendering** or video editing, as well as model training and inferencing (ND) with deep learning | NV, NC, NCv2, NCv3, ND |
-| **High-performance computing (HPC)**: If you need the fastest and most powerful CPU virtual machines with optional high-throughput network interfaces | H |
+| **Data storage and processing**: Big Data, SQL, and NoSQL databases, which need high disk throughput and IO. | Ls |
+| **Heavy graphics rendering** or video editing, as well as model training and inferencing (ND) with deep learning. | NV, NC, NCv2, NCv3, ND |
+| **High-performance computing (HPC)**: If you need the fastest and most powerful CPU virtual machines with optional high-throughput network interfaces. | H |
 
 ## Choose storage options
 
@@ -102,6 +102,6 @@ Virtual machines communicate with external resources using a virtual network (VN
 
 When you create a new VM, you'll have the option of creating a new virtual network or using an existing VNet in your region.
 
-Having Azure create the network together with the VM is simple, but it's likely not ideal for most scenarios. It's better to plan your network requirements *up front* for all the components in your architecture and create the VNet structure you'll need separately and then create the VMs and place them into the already-created VNets.
+Having Azure create the network together with the VM is simple, but it's likely not ideal for most scenarios. It's better to plan your network requirements *up front* for all the components in your architecture, and create the VNet structure you'll need separately. Then create the VMs, and place them into the already-created VNets.
 
 We'll look more at virtual networks a bit later in this module. Let's apply some of this knowledge and create a VM in Azure.

learn-pr/azure/create-windows-virtual-machine-in-azure/includes/4-connect-to-a-windows-virtual-machine.md

@@ -1,6 +1,6 @@
-Now that you have a Windows VM in Azure, the next thing you’ll do is put your applications and data on those VMs to process our traffic videos. 
+Now that you have a Windows VM in Azure, the next thing you'll do is put your applications and data on those VMs to process our traffic videos. 
 
-However, unless you’ve set up a site-to-site VPN to Azure, your Azure VMs won’t be accessible from your local network. If you’re just getting started with Azure, it’s unlikely that you have a working site-to-site VPN, so how can you transfer files to Azure VMs? One easy way is to use Azure’s Remote Desktop Connections feature to share your local drives with your new Azure VMs.
+However, unless you've set up a site-to-site VPN to Azure, your Azure VMs won't be accessible from your local network. If you're just getting started with Azure, it's unlikely that you have a working site-to-site VPN. So how can you transfer files to Azure VMs? One easy way is to use Azure's Remote Desktop Connections feature to share your local drives with your new Azure VMs.
 
 Now that we have a new Windows virtual machine, we need to install our custom software onto it. There are several options to choose from:
 
@@ -35,7 +35,7 @@ One thing to be aware of with public IP addresses in Azure is they're often dyna
 
 ### How do you connect to a VM in Azure using RDP?
 
-Connecting to a VM in Azure using RDP is a simple process. In the Azure portal, you'll go to your VM's properties, and at the top, select **Connect**. This shows you the IP addresses assigned to the VM and give you the option to download a **preconfigured.rdp** file that Windows then opens in the RDP client. You can choose to connect over the public IP address of the VM in the RDP file. Instead, if you're connecting over VPN or ExpressRoute, you can select the internal IP address. You can also select the port number for the connection.
+Connecting to a VM in Azure using RDP is a simple process. In the Azure portal, you'll go to your VM's properties, and at the top, select **Connect**. This shows you the IP addresses assigned to the VM and gives you the option to download a **preconfigured.rdp** file that Windows then opens in the RDP client. You can choose to connect over the public IP address of the VM in the RDP file. Instead, if you're connecting over VPN or ExpressRoute, you can select the internal IP address. You can also select the port number for the connection.
 
 If you're using a static public IP address for the VM, you can save the **.rdp** file to your desktop. If you're using dynamic IP addressing, the **.rdp** file only remains valid while the VM is running. If you stop and restart the VM, you must download another **.rdp** file.
 
@@ -44,8 +44,8 @@ If you're using a static public IP address for the VM, you can save the **.rdp**
 
 When you connect, you'll typically receive two warnings. These are:
 
-- **Publisher warning**: caused by the **.rdp** file not being publicly signed
-- **Certificate warning**: caused by the machine certificate not being trusted
+- **Publisher warning**: caused by the **.rdp** file not being publicly signed.
+- **Certificate warning**: caused by the machine certificate not being trusted.
 
 In test environments, you can ignore these warnings. In production environments, the **.rdp** file can be signed using **RDPSIGN.EXE** and the machine certificate placed in the client's **Trusted Root Certification Authorities** store.
 

learn-pr/azure/create-windows-virtual-machine-in-azure/includes/5-exercise-connect-to-a-windows-vm-using-rdp.md

@@ -1,12 +1,12 @@
 We have our Windows VM deployed and running, but it's not configured to do any work.
 
-Recall that our scenario is a video-processing system. Our platform receives files through FTP. The traffic cameras upload video clips to a known URL, which is mapped to a folder on the server. The custom software on each Windows VM runs as a service and watches the folder and processes each uploaded clip. It then passes the normalized video to our algorithms running on other Azure services.
+Recall that our scenario is a video-processing system. Our platform receives files through FTP. The traffic cameras upload video clips to a known URL, which is mapped to a folder on the server. The custom software on each Windows VM runs as a service, watches the folder, and processes each uploaded clip. It then passes the normalized video to our algorithms running on other Azure services.
 
 There are a few things we'd need to configure to support this scenario:
 
-- Install FTP and open the ports it needs to communicate
-- Install the proprietary video codec unique to the city's camera system
-- Install our transcoding service that processes uploaded videos
+- Install FTP and open the ports it needs to communicate.
+- Install the proprietary video codec unique to the city's camera system.
+- Install our transcoding service that processes uploaded videos.
 
 Many of these are typical administrative tasks we won't actually cover here, and we don't have software to install. Instead, we'll walk through the steps and show you how you *could* install custom or third-party software using Remote Desktop. Let's start by getting the connection information.