Skip to content

Commit fcbc473

Browse files
authored
Update src/handbook/development/ops/maintenance.md
1 parent 59b4c57 commit fcbc473

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/handbook/development/ops/maintenance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Once the maintenance date is set, customers should be informed about the upcomin
3535

3636
E-mail template for maintenance communication can be found in the [FlowFuse Cloud Maintenance Communication document](https://docs.google.com/document/d/1Pkd0qifjgs7xv96hfQ5OHnvX5n_WPHyA0AvPd9UUPL0). Adjust the template accordingly.
3737

38-
The notification message should be sent to all FlowFuse Cloud Team Owners who have active instances in the FlowFuse Cloud and who are affected by the maintenance. To get the contact list, please refere to the [internal documentation](https://docs.google.com/document/d/1s0mXpuuPKl-1U-YVzoTEGBhllUd-UPJjFXTqa0O481c/#heading=h.hing87m0bsmu).
38+
The notification message should be sent to all FlowFuse Cloud Team Owners who have active instances in the FlowFuse Cloud and who are affected by the maintenance. To get the contact list, please refer to the [internal documentation](https://docs.google.com/document/d/1s0mXpuuPKl-1U-YVzoTEGBhllUd-UPJjFXTqa0O481c/#heading=h.hing87m0bsmu).
3939

4040
We should sent notification at least twice - 45 days before the maintenance and a reminder one week before the maintenance day.
4141

0 commit comments

Comments
 (0)