Skip to content

Commit 41b8912

Browse files
committed
removed unneeded periods
1 parent ffe3444 commit 41b8912

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/lab-services/classroom-labs/administrator-guide.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -51,19 +51,19 @@ A lab account serves as a container for one or more classroom labs. When getting
5151

5252
The following list highlights scenarios where more than one lab account may be beneficial:
5353

54-
- **Manage different policy requirements across classroom labs.**
54+
- **Manage different policy requirements across classroom labs**
5555

5656
When you set up a lab account, you set policies that apply to *all* classroom labs under the lab account, such as:
5757
- The Azure virtual network with shared resources that the classroom lab can access. For example, you may have a set of classroom labs that need access to a shared data set within a virtual network.
5858
- The virtual machine (VM) images that the classroom labs can use to create VMs. For example, you may have a set of classroom labs that need access to the [Data Science VM for Linux](https://azuremarketplace.microsoft.com/marketplace/apps/microsoft-dsvm.linux-data-science-vm-ubuntu) Marketplace image.
5959

6060
If you have classroom labs that have unique policy requirements from one another, it may be beneficial to create separate lab accounts to manage these classroom labs separately.
6161

62-
- **Separate budget by lab account.**
62+
- **Separate budget by lab account**
6363

6464
Instead of reporting all classroom lab costs through a single lab account, you may need a more clearly separated budget. For example, you can create lab accounts for your university's Math department, Computer Science department, and so forth, to separate the budget across departments. You can then view the cost for each individual lab account using [Azure Cost Management](https://docs.microsoft.com/azure/cost-management-billing/cost-management-billing-overview).
6565

66-
- **Isolate pilot labs from active\production labs.**
66+
- **Isolate pilot labs from active\production labs**
6767

6868
You may have cases where you want to pilot policy changes for a lab account without potentially impacting active\production labs. In this type of scenario, creating a separate lab account for piloting purposes allows you to isolate changes.
6969

@@ -75,15 +75,15 @@ A classroom lab contains virtual machines (VMs) that are each assigned to a sing
7575

7676
Consider the following points when determining how to structure your classroom labs:
7777

78-
- **All VMs within a classroom lab are deployed with the same image that's published**.
78+
- **All VMs within a classroom lab are deployed with the same image that's published**
7979

8080
As a result, if you have a class that requires different lab images be published at the same time, separate classroom labs must be created for each one.
8181

82-
- **Usage quota is set at the lab level and applies to all users within the lab**.
82+
- **Usage quota is set at the lab level and applies to all users within the lab**
8383

8484
To set different quotas for users, you must create separate classroom labs. However, it's possible to add more hours to a specific user after you have set the quota.
8585

86-
- **The startup or shutdown schedule is set at the lab level and applies to all VMs within the lab**.
86+
- **The startup or shutdown schedule is set at the lab level and applies to all VMs within the lab**
8787

8888
Similar to the previous point, if you need to set different schedules for users, you need to create separate classroom labs.
8989

0 commit comments

Comments
 (0)