Skip to content

Commit c9a41a4

Browse files
RoseHJMntrogh
andauthored
Apply suggestions from code review
Co-authored-by: Nick Trogh <[email protected]>
1 parent 7ae310d commit c9a41a4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/devtest-labs/how-to-move-schedule-to-new-region.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ There are two ways to move a schedule:
3333
- Manually recreate the schedules on the moved VMs. This process can be time consuming and error prone. This approach is most useful when you have a few schedules and VMs.
3434
- Export and redeploy the schedules by using ARM templates.
3535

36-
Move your existing schedule by using the following steps:
36+
Use the following steps to export and redeploy your schedule in another Azure region by using an ARM template:
3737

3838
1. Sign in to the [Azure portal](https://portal.azure.com).
3939

@@ -65,8 +65,8 @@ Move your existing schedule by using the following steps:
6565

6666
:::image type="content" source="./media/how-to-move-schedule-to-new-region/move-schedule-custom-deployment.png" alt-text="Screenshot that shows the custom deployment page, with new location values for the relevant settings.":::
6767

68-
>[!IMPORTANT]
69-
>Each schedule must have a globally unique name; you will need to change the schedule name for the new location.
68+
>[!IMPORTANT]
69+
>Each schedule must have a globally unique name; you will need to change the schedule name for the new location.
7070
7171
10. Select **Review and create** to create the deployment.
7272

0 commit comments

Comments
 (0)