Update for Acrolinx

ntrogh · ntrogh · commit dbde7758231d · 2023-03-13T22:40:10.000+01:00
diff --git a/articles/lab-services/classroom-labs-concepts.md b/articles/lab-services/classroom-labs-concepts.md
@@ -31,7 +31,7 @@ You can further configure the lab behavior by creating [lab schedules](#schedule
 
 When you publish a lab, Azure Lab Services provisions the lab VMs. All lab VMs for a lab share the same configuration and are identical.
 
-To create labs in Azure Lab Services, your Azure account needs to have the Lab Creator Azure AD role or you need to be the owner of the corresponding lab plan. Learn more about [Azure Lab Services built-in roles](./administrator-guide.md#rbac-roles).
+To create labs in Azure Lab Services, your Azure account needs to have the Lab Creator Azure AD role, or you need to be the owner of the corresponding lab plan. Learn more about [Azure Lab Services built-in roles](./administrator-guide.md#rbac-roles).
 
 You use the Azure Lab Services website (https://labs.azure.com) to create labs for a lab plan. Alternately, you can also [configure Microsoft Teams integration](./how-to-configure-teams-for-lab-plans.md) or [Canvas integration](./how-to-configure-canvas-for-lab-plans.md) with Azure Lab Services to create labs directly in Microsoft Teams or Canvas.
 
@@ -41,17 +41,17 @@ Get started by [creating a lab using the Azure portal](quick-create-connect-lab.
 
 ## Azure Compute Gallery
 
-When you create a lab, you select the base VM image for the lab VMs. You can use an [Azure compute gallery](/azure/virtual-machines/azure-compute-gallery) to store and share custom VM images. By using a compute gallery, you avoid having to repeatedly apply the same customizations when you create a new lab. If you have customized a lab with a template VM, you can [export the template VM to your compute gallery](./approaches-for-custom-image-creation.md).
+When you create a lab, you select the base VM image for the lab VMs. You can use an [Azure compute gallery](/azure/virtual-machines/azure-compute-gallery) to store and share custom VM images. By using a compute gallery, you avoid having to repeatedly apply the same customizations when you create a new lab. If you've customized a lab with a template VM, you can [export the template VM to your compute gallery](./approaches-for-custom-image-creation.md).
 
 To use VM images from a compute gallery, you attach the Azure compute gallery to your lab plan. You can attach zero or more Azure compute galleries to a lab plan. After attaching a compute gallery, you can further enable or disable specific images.
 
 Learn how to [attach or detach an Azure compute gallery](./how-to-attach-detach-shared-image-gallery.md).
 
 ## Template virtual machine
 
-You can choose to create a customizable lab, which enables you to modify the base image for the [lab VMs](#lab-virtual-machine). For example, to install additional software components are modify operating system settings. In this case, Azure Lab Services creates a lab template VM, which you can connect to and customize.
+You can choose to create a customizable lab, which enables you to modify the base image for the [lab VMs](#lab-virtual-machine). For example, to install extra software components or modify operating system settings. In this case, Azure Lab Services creates a lab template VM, which you can connect to and customize.
 
-When you [publish the lab](./tutorial-setup-lab.md#publish-lab), Azure Lab Services creates the lab VMs, based on the the template VM image. If you modify the template VM at a later stage, when you republish the template VM, all lab VMs are updated to match the new template. When your republish a template VM, Azure Lab Services reimages the lab VMs and removes all changes and data on the VM.
+When you [publish the lab](./tutorial-setup-lab.md#publish-lab), Azure Lab Services creates the lab VMs, based on the template VM image. If you modify the template VM at a later stage, when you republish the template VM, all lab VMs are updated to match the new template. When you republish a template VM, Azure Lab Services reimages the lab VMs and removes all changes and data on the VM.
 
 With the [introduction of lab plans](lab-services-whats-new.md), you can also create a templateless lab. In a templateless lab, you select the base image for the lab VMs from the Azure Marketplace or an Azure compute gallery, and you can't further customize the image of a templateless lab. You might use templateless labs because you manage  your *golden* VM images in an Azure compute gallery. The advantage of templateless labs is that all labs use your *golden images* without changes. Another benefit is that lab creation is faster because there's no need to create a template VM.
 
@@ -61,13 +61,13 @@ Learn how to [create and manage a template in Azure Lab Services](./how-to-creat
 
 In Azure Lab Services, lab VMs are managed virtual machines that get their configuration from the [lab](#lab). All VMs for a lab are identical. Azure Lab Services provisions the lab VMs when you publish the lab.
 
-After provisioning the lab VMs, lab users can connect to their VM through remote desktop (RDP) or secure shell (SSH). Before they can connect to the lab VM, lab users have to first [register for the lab](./how-to-use-lab.md) by using a registration link. Azure Lab Services then assigns the user to a specific lab VM.
+After you publish the lab VMs, lab users can connect to their VM through remote desktop (RDP) or secure shell (SSH). Before they can connect to the lab VM, lab users have to first [register for the lab](./how-to-use-lab.md) by using a registration link. Azure Lab Services then assigns the user to a specific lab VM.
 
 In the lab settings, you can optionally configure one or more [schedules](#schedule) and assign [user quota](#quota).
 
 ## Schedule
 
-Schedules are the time slots that a lab creator defines so the lab VMs are available for class time, and to avoid that lab users need to wait for their VM to start up. Schedules can be one-time or recurring.
+Schedules are the time slots that define when the lab VMs are available for class time. With schedules, you can avoid that lab users need to wait for their VM to start up. Schedules can be one-time or recurring. The lab creator can define schedules for a lab.
 
 The use of schedules for a lab is optional and you might [specify user quota](#quota) instead, or use a combination of both. User quota is the time that lab users can run their lab VM outside of scheduled time. For example, to complete assignments or homework. Any scheduled time doesn't count against extra time that lab users have. A lab can use [quota](#quota) time, scheduled time, or a combination of both.
 
@@ -78,8 +78,8 @@ Example scenarios for using schedules are:
 
 There are two types of schedules.
 
-- **Standard**. This schedule starts all lab VMs, except VMs that are not assigned yet, at the specified start time and shuts down all lab VMs at the specified stop time.
-- **Stop only**. This schedule stops all lab VMs at the specified time, even if the VM was manually started by the lab creator or the lab user.
+- **Standard**. This schedule starts all lab VMs, except VMs that aren't assigned yet, at the specified start time and shuts down all lab VMs at the specified stop time.
+- **Stop only**. This schedule stops all lab VMs at the specified time, even if the lab creator or lab user started the VM manually.
 
 Azure Lab Services starts a lab VM, regardless if the user signs into the VM or not. To help reduce the cost of running VMs that are unused, see how you can [configure automatic shutdown of lab VMs](how-to-enable-shutdown-disconnect.md).
 
