mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
Docs: Update fleet-in-your-calendar-introducing-maintenance-windows.md (#20880)
## Issue Cerra #20416 ## Description - Update incorrect text copies to match current functionality (confirmed via [slack thread](https://fleetdm.slack.com/archives/C01EZVBHFHU/p1722439175927049?thread_ts=1722439142.748039&cid=C01EZVBHFHU)) I reviewed the announcement (nowhere is it called a guide thankfully) that was published April 30, it looks like only one line is incorrect. This is to correct this line. There is a related ticket #20860 for Mike to update the images Editor: @RachelElysia Technical Reviewer: @getvictor
This commit is contained in:
parent
305989b996
commit
80e6043348
1 changed files with 1 additions and 1 deletions
|
|
@ -21,7 +21,7 @@ Fleet provides AI-generated explanations directly in the calendar events, detail
|
|||
## _Maintenance windows_ include:
|
||||
|
||||
* **Personalized scheduling:** Updates are timed based on individual calendar events, so interventions happen when they are least intrusive.
|
||||
* **Automatic rescheduling:** If a scheduled update becomes impractical—due to changes in your calendar, for example—Fleet automatically finds a new appropriate time.
|
||||
* **Rescheduling flexibility:** If a scheduled update becomes impractical for any reason, users have the option to manually move the maintenance window to a more suitable time. We suggest rescheduling within one week to ensure timely updates.
|
||||
* **Enhanced compliance:** With auto-scheduled maintenance windows, compliance with security protocols is maintained effortlessly, ensuring all devices are up to date without manual intervention.
|
||||
|
||||
_Maintenance windows_ is a direct response to common challenges faced in workplace productivity, particularly unplanned disruptions from essential updates. Fleet aims to support smoother, more efficient work environments by incorporating user feedback and addressing these long-standing issues.
|
||||
|
|
|
|||
Loading…
Reference in a new issue