Skip to content

Commit 01e9c13

Browse files
committed
review inputs incorporated
1 parent ec9577c commit 01e9c13

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/update-manager/pre-post-scripts-overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ The following are the scenarios where you can define pre and post events:
2525
|----------|-------------|
2626
|Turn on machines | Turn on the machine to apply updates.|
2727
|Create snapshot | Disk snaps used to recover data.|
28-
|Notification email | Send a notification alert before patching is triggered. |
29-
|Stop services | To stop services like Gateway services, NPExServices, SQL services etc.|
28+
|Notification email | Send a notification alert before triggering a patch. |
29+
|Stop services | Stop services like Gateway services, NPExServices, SQL services etc.|
3030

3131
#### [Post Events](#tab/postevent)
3232

@@ -72,9 +72,9 @@ Azure Update Manager uses [Event Grid](../event-grid/overview.md) to create and
7272
:::image type="content" source="./media/pre-post-scripts-overview/pre-post-schedule-timeline.png" alt-text="Screenshot that shows the timeline of schedules with pre and post." lightbox="./media/pre-post-scripts-overview/pre-post-schedule-timeline.png":::
7373

7474

75-
We recommend you to go through the following table to understand the timeline of the schedule for pre and post events.
75+
We recommend you go through the following table to understand the timeline of the schedule for pre and post events.
7676

77-
For example, if a maintenance schedule is set to start at **3:00 PM**, with the maintenance window of 3 hours and 55 minutes for **Guest** maintenance scope, The schedule has one pre-event and one post-event following are the details:
77+
For example, if a maintenance schedule is set to start at **3:00 PM**, with the maintenance window of 3 hours and 55 minutes for **Guest** maintenance scope. The schedule has one pre-event and one post-event and following are the details:
7878

7979

8080
| **Time**| **Details** |
@@ -87,7 +87,7 @@ For example, if a maintenance schedule is set to start at **3:00 PM**, with the
8787
| 6:55 PM | - At 6:55 PM, the schedule completes installing the updates during the 3 hours 55-mins maintenance window. </br> The post event triggers at 6:55 PM once the updates are installed. </br> **Note** If you have defined a shorter maintenance window of 2 hours, the post maintenance event will trigger after 2 hours and if the update installation is completed before the stipulated time of 2 hours (i.e) 1 hours 50 mins, the post event will start immediately.
8888

8989
We recommend that you're watchful of the following:
90-
- If you're creating a new schedule or editing an existing schedule with a pre event, you need at least 40 minutes prior to the start of maintenance window (3:00 PM in the above example) for the pre event to run otherwise it will lead to auto-cancellation of the current scheduled run.
90+
- If you're creating a new schedule or editing an existing schedule with a pre-event, you need at least 40 minutes prior to the start of maintenance window (3:00 PM in the above example) for the pre-event to run otherwise it will lead to auto-cancellation of the current scheduled run.
9191
- Invoking a cancellation API from your script or code will cancel the schedule run and not the entire schedule.
9292
- The status of the pre and post event run can be checked in the event handler you chose.
9393

0 commit comments

Comments
 (0)