Merge pull request #279477 from markingmyname/varun

[PostgreSQL] Add Considerations section

Author: v-dirichards

articles/postgresql/flexible-server/concepts-maintenance.md

@@ -4,10 +4,10 @@ description: This article describes the scheduled maintenance feature in Azure D
 author: varun-dhawan
 ms.author: varundhawan
 ms.reviewer: maghan
-ms.date: 04/27/2024
+ms.date: 06/27/2024
 ms.service: postgresql
 ms.subservice: flexible-server
-ms.topic: conceptual
+ms.topic: concept-article
 ---
 
 # Scheduled maintenance in Azure Database for PostgreSQL - Flexible Server
@@ -16,7 +16,7 @@ ms.topic: conceptual
 
 Azure Database for PostgreSQL flexible server performs periodic maintenance to help keep your managed database secure, stable, and up to date. During maintenance, the server gets new features, updates, and patches.
 
-> [!IMPORTANT]
+> [!IMPORTANT]  
 > Avoid all server operations (modifications, configuration changes, starting/stopping the server) during Azure Database for PostgreSQL flexible server maintenance. Engaging in these activities can lead to unpredictable outcomes and possibly affect server performance and stability. Wait until maintenance concludes before you conduct server operations.
 
 ## Select a maintenance window
@@ -27,11 +27,11 @@ The system sends maintenance notifications 5 days in advance so that you have am
 
 Notifications about upcoming scheduled maintenance can be:
 
-* Emailed to a specific address.
-* Emailed to an Azure Resource Manager role.
-* Sent in a text message to mobile devices.
-* Pushed as a notification to an Azure app.
-* Delivered as a voice message.
+- Emailed to a specific address.
+- Emailed to an Azure Resource Manager role.
+- Sent in a text message to mobile devices.
+- Pushed as a notification to an Azure app.
+- Delivered as a voice message.
 
 When you're specifying preferences for the maintenance schedule, you can choose a day of the week and a time window. If you don't specify a time window, the system chooses times between 11:00 PM and 7:00 AM in your server region's time. You can define different schedules for each Azure Database for PostgreSQL flexible server instance in your Azure subscription.
 
@@ -42,21 +42,28 @@ You can update schedule settings at any time. If maintenance is scheduled for yo
 
 ## System-managed vs. custom maintenance schedules
 
-You can define a system-managed schedule or a custom schedule for each Azure Database for PostgreSQL flexible server instance in your Azure subscription:  
+You can define a system-managed schedule or a custom schedule for each Azure Database for PostgreSQL flexible server instance in your Azure subscription:
 
-* With a system-managed schedule, the system chooses any 1-hour window between 11:00 PM and 7:00 AM in your server region's time.
-* With a custom schedule, you can specify your maintenance window for the server by choosing the day of the week and a 1-hour time window.
+- With a system-managed schedule, the system chooses any one hour window between 11:00 PM and 7:00 AM in your server region's time.
+- With a custom schedule, you can specify your maintenance window for the server by choosing the day of the week and a one hour time window.
 
-Updates are first applied to servers with system-managed schedules, followed by servers with custom schedules after at least 7 days within a region. To receive early updates for development and test servers, use a system-managed schedule. This choice allows early testing and issue resolution before updates reach production servers with custom schedules.
+Updates are first applied to servers with system-managed schedules, followed by servers with custom schedules after at least seven days within a region. To receive early updates for development and test servers, use a system-managed schedule. This choice allows early testing and issue resolution before updates reach production servers with custom schedules.
 
-Updates for custom-schedule servers begin 7 days later, during a defined maintenance window. After you're notified, you can't defer updates. We advise that you use custom schedules for production environments only.
+Updates for custom-schedule servers begin seven days later, during a defined maintenance window. After you're notified, you can't defer updates. We advise that you use custom schedules for production environments only.
 
 In rare cases, maintenance events can be canceled by the system or fail to finish successfully. If an update fails, it's reverted, and the previous version of the binaries is restored. The server might still restart during the maintenance window.
 
-If an update is canceled or failed, the system creates a notification about the canceled or failed maintenance event. The next attempt to perform maintenance is scheduled according to your current schedule settings, and you receive a notification about it 5 days in advance.
+If an update is canceled or failed, the system creates a notification about the canceled or failed maintenance event. The next attempt to perform maintenance is scheduled according to your current schedule settings, and you receive a notification about it five days in advance.
+
+## Consideration and limitations
+
+Some considerations when considering during monthly maintenance.
+
+- Monthly maintenance is impactful and they involve some downtime.
+    - Downtime depends on the transactional load on the server at the time of maintenance.
 
-## Next steps
+## Related content
 
-* Learn how to [change the maintenance schedule](how-to-maintenance-portal.md).
-* Learn how to [get notifications about upcoming maintenance](../../service-health/service-notifications.md) by using Azure Service Health.
-* Learn how to [set up alerts for upcoming scheduled maintenance events](../../service-health/resource-health-alert-monitor-guide.md).
+- [change the maintenance schedule](how-to-maintenance-portal.md)
+- [get notifications about upcoming maintenance](../../service-health/service-notifications.md)
+- [set up alerts for upcoming scheduled maintenance events](../../service-health/resource-health-alert-monitor-guide.md)