minor corrections in the doc

Author: VandhanaMehta

articles/mysql/flexible-server/concepts-high-availability.md

@@ -79,7 +79,8 @@ Forced failover triggers a failover that activates the standby replica to become
 
 The overall failover time depends on the current workload and the last checkpoint. In general, it's expected to take between 60 and 120 seconds.
 
-[!Note]Azure Resource Health event is generated in the event of planned failover, representing the failover time during which server was unavailable. The triggered events can be seen when clicked on "Resource Health" in the left pane. User initiated/ Manual failover is represented by status as **"Unavailable"** and tagged as **"Planned"**. Example - "A failover operation was triggered by an authorized user (Planned)". If your resource remains in this state for an extended period of time, please open a [support ticket](https://azure.microsoft.com/support/create-ticket/) and we will assist you.
+>[!Note]
+>Azure Resource Health event is generated in the event of planned failover, representing the failover time during which server was unavailable. The triggered events can be seen when clicked on "Resource Health" in the left pane. User initiated/ Manual failover is represented by status as **"Unavailable"** and tagged as **"Planned"**. Example - "A failover operation was triggered by an authorized user (Planned)". If your resource remains in this state for an extended period of time, please open a [support ticket](https://azure.microsoft.com/support/create-ticket/) and we will assist you.
 
 
 ### Unplanned: Automatic failover 
@@ -88,7 +89,8 @@ Unplanned service downtime can be caused by software bugs or infrastructure faul
 
 The overall failover time is expected to be between 60 and 120 seconds. But, depending on the activity in the primary database server at the time of the failover (like large transactions and recovery time), the failover might take longer.
 
-[!Note]Azure Resource Health event is generated in the event of unplanned failover, representing the failover time during which server was unavailable. The triggered events can be seen when clicked on "Resource Health" in the left pane. Automatic failover is represented by status as **"Unavailable"** and tagged as **"Unplanned"**. Example - "Unavailable : A failover operation was triggered automatically (Unplanned)". If your resource remains in this state for an extended period of time, please open a [support ticket](https://azure.microsoft.com/support/create-ticket/) and we will assist you.
+>[!Note]
+>Azure Resource Health event is generated in the event of unplanned failover, representing the failover time during which server was unavailable. The triggered events can be seen when clicked on "Resource Health" in the left pane. Automatic failover is represented by status as **"Unavailable"** and tagged as **"Unplanned"**. Example - "Unavailable : A failover operation was triggered automatically (Unplanned)". If your resource remains in this state for an extended period of time, please open a [support ticket](https://azure.microsoft.com/support/create-ticket/) and we will assist you.
 
 #### How automatic failover detection works in HA enabled servers
 

articles/mysql/flexible-server/whats-new.md

@@ -26,13 +26,13 @@ This article summarizes new releases and features in Azure Database for MySQL -
 
 ## March 2023
 
-**Azure Resource Health**
+- **Azure Resource Health**
 
-Use Azure Resource Health to monitor the health and availability of the HA enabled server in the event of planned or unplanned failover. [Learn more](concepts-high-availability.md)
+  Use Azure Resource Health to monitor the health and availability of the HA enabled server in the event of planned or unplanned failover. [Learn more](concepts-high-availability.md)
 
-**Enhanced restore experience**
+- **Enhanced restore experience**
 
-Restore experience will now provide additional flexibility to modify the compute and storage setting during the provisioning of the restored server. Restored server can now be configured to have a higher compute tier, compute size and storage than that of the source server at the time of provisioning. Options like "Storage auto-grow", "Backup retention days" and "Geo-redundancy" can be also be edited to have a different value than that of source server.
+  Restore experience will now provide additional flexibility to modify the compute and storage setting during the provisioning of the restored server. Restored server can now be configured to have a higher compute tier, compute size and storage than that of the source server at the time of provisioning. Options like "Storage auto-grow", "Backup retention days" and "Geo-redundancy" can be also be edited to have a different value than that of source server.
 
 
 ## February 2023