removed "blade" from what's new

markingmyname · markingmyname · commit 33a412aa4238 · 2022-09-15T06:38:48.000-05:00
diff --git a/articles/mysql/flexible-server/whats-new.md b/articles/mysql/flexible-server/whats-new.md
@@ -8,7 +8,7 @@ author: SudheeshGH
 ms.author: sunaray
 ms.reviewer: maghan
 ms.custom: mvc, references_regions, event-tier1-build-2022
-ms.date: 08/16/2022
+ms.date: 09/16/2022
 ---
 
 # What's new in Azure Database for MySQL - Flexible Server?
@@ -54,15 +54,12 @@ Learn more about [Boost Azure MySQL Business Critical flexible server performanc
     - [performance_schema_max_digest_length](https://dev.mysql.com/doc/refman/8.0/en/performance-schema-system-variables.html#sysvar_performance_schema_max_digest_length)
     - [performance_schema_max_sql_text_length](https://dev.mysql.com/doc/refman/8.0/en/performance-schema-system-variables.html#sysvar_performance_schema_max_sql_text_length) 
  
-
 - **Known Issues**
 
-  - When you try to connect to the server, you'll receive error "ERROR 9107 (HY000): Only Azure Active Directory accounts are allowed to connect to server".
+  - When you try to connect to the server, you receive error "ERROR 9107 (HY000): Only Azure Active Directory accounts are allowed to connect to server".
 
     Server parameter aad_auth_only was exposed in this month's deployment. Enabling server parameter aad_auth_only will block all non Azure Active Directory MySQL connections to your Azure Database for MySQL Flexible server. We're currently working on additional configurations required for Azure Active Directory (AAD) authentication to be fully functional, and the feature will be available in the upcoming deployments. Don't enable the aad_auth_only parameter until then.
 
-
-
 ## June 2022
 
 - **Known Issues**
@@ -101,7 +98,7 @@ Learn more about [Boost Azure MySQL Business Critical flexible server performanc
 This release of Azure Database for MySQL - Flexible Server includes the following updates.
 
 - **Migrate from locally redundant backup storage to geo-redundant backup storage for existing flexible server**
-    Azure Database for MySQL - Flexible Server now provides the added flexibility to migrate to geo-redundant backup storage from locally redundant backup storage post server-create to provide higher data resiliency. Enabling geo-redundancy via the server's Compute + Storage blade empowers customers to recover their existing flexible servers from a geographic disaster or regional failure when they can’t access the server in the primary region. With this feature enabled for their existing servers, customers can perform geo-restore and deploy a new server to the geo-paired Azure region using the original server’s latest available geo-redundant backup. [Learn more](concepts-backup-restore.md)
+    Azure Database for MySQL - Flexible Server now provides the added flexibility to migrate to geo-redundant backup storage from locally redundant backup storage post server-create to provide higher data resiliency. Enabling geo-redundancy via the server's Compute + Storage page empowers customers to recover their existing flexible servers from a geographic disaster or regional failure when they can’t access the server in the primary region. With this feature enabled for their existing servers, customers can perform geo-restore and deploy a new server to the geo-paired Azure region using the original server’s latest available geo-redundant backup. [Learn more](concepts-backup-restore.md)
 
 - **Simulate disaster recovery drills for your stopped servers**
     Azure Database for MySQL - Flexible Server now provides the ability to perform geo-restore on stopped servers helping users simulate disaster recovery drills for their workloads to estimate impact and recovery time.This will help users plan better to meet their disaster recovery and business continuity objectives by using geo-redundancy feature offered by Azure Database for MySQL Flexible Server. [Learn more](how-to-restore-server-cli.md)
@@ -131,7 +128,7 @@ This release of Azure Database for MySQL - Flexible Server includes the followin
 
   - When you're using ARM templates for provisioning or configuration changes for HA enabled servers, if a single deployment is made to enable/disable HA and along with other server properties like backup redundancy, storage etc., then deployment would fail. You can mitigate it by submitting the deployment request separately to enable\disable and configuration changes. You wouldn’t have an issue with Portal or Azure CLI, as these requests are already separated.
 
-  - When you're viewing automated backups for a HA enabled server in Backup and Restore blade, if at some point in time a forced or automatic failover is performed, you may lose viewing rights to the server's backups on the Backup and Restore blade. Despite the invisibility of information regarding backups on the portal, the flexible server is successfully taking daily automated backups for the server in the backend. The server can be restored to any point within the retention period.  
+  - When you're viewing automated backups for a HA enabled server on the Backup and Restore page, if at some point in time a forced or automatic failover is performed, you may lose viewing rights to the server's backups on the Backup and Restore page. Despite the invisibility of information regarding backups on the portal, the flexible server is successfully taking daily automated backups for the server in the backend. The server can be restored to any point within the retention period.  
 
 ## November 2021
 
@@ -141,17 +138,17 @@ This release of Azure Database for MySQL - Flexible Server includes the followin
 
 - **View available full backups in Azure portal**
   
-  A dedicated Backup and Restore blade is now available in the Azure portal. This blade lists the backups available within the server’s retention period, effectively providing you with single pane view for managing a server’s backups and consequent restores. You can use this blade to
+  A dedicated Backup and Restore option is now available in the Azure portal. This page lists the backups available within the server’s retention period, effectively providing you with single pane view for managing a server’s backups and consequent restores. You can use this option to:
      1) View the completion timestamps for all available full backups within the server’s retention period
      2) Perform restore operations using these full backups
   
 - **Fastest restore points**
   
   With the fastest restore point option, you can restore a Flexible Server instance in the fastest time possible on a given day within the server’s retention period. This restore operation restores the full snapshot backup without requiring restore or recovery of logs. With fastest restore point, customers will see three options while performing point in time restores from Azure portal viz latest restore point, custom restore point and fastest restore point. [Learn more](concepts-backup-restore.md#point-in-time-restore)
   
-- **FAQ blade in Azure portal**
+- **FAQ in the Azure portal**
 
-  The Backup and Restore blade will also include section dedicated to listing your most frequently asked questions, together with answers. This should provide you with answers to most questions about backup directly within the Azure portal. In addition, selecting the question mark icon for FAQs on the top menu provides access to even more related detail.
+  The Backup and Restore page includes section dedicated to listing your most frequently asked questions, together with answers. This should provide you with answers to most questions about backup directly within the Azure portal. In addition, selecting the question mark icon for FAQs on the top menu provides access to even more related detail.
 
 - **Restore a deleted Flexible server**
 
@@ -177,8 +174,6 @@ This release of Azure Database for MySQL - Flexible Server includes the followin
 
 - **Read replicas in Azure Database for MySQL - Flexible servers will no longer be available on Burstable SKUs**
 
-    You won’t be able to create new or maintain existing read replicas on the Burstable tier server. In the interest of providing a good query and development experience for Burstable SKU tiers, the support for creating and maintaining read replica for servers in the Burstable pricing tier will be discontinued.
-
     If you have an existing Azure Database for MySQL - Flexible Server with read replica enabled, you’ll have to scale up your server to either General Purpose or Business Critical pricing tiers or delete the read replica within 60 days. After the 60-day period, while you can continue to use the primary server for your read-write operations, replication to read replica servers will be stopped. For newly created servers, read replica option will be available only for the General Purpose and Business Critical pricing tiers.  
 
 - **Monitoring Azure Database for MySQL - Flexible Server with Azure Monitor Workbooks**
@@ -277,8 +272,8 @@ This release of Azure Database for MySQL - Flexible Server includes the followin
 
   - Right after Zone-Redundant high availability server failover, clients fail to connect to the server if using SSL with ssl_mode VERIFY_IDENTITY. This issue can be mitigated by using ssl_mode as VERIFY_CA.
   - Unable to create Same-Zone High availability server in the following regions: Central India, East Asia, Korea Central, South Africa North, Switzerland North.
-  - In a rare scenario and after HA failover, the primary server will be in read_only mode. Resolve the issue by updating “read_only” value from the server parameters blade to OFF.
-  - After successfully scaling Compute in the Compute+Storage blade, IOPS are reset to the SKU default. Customers can work around the issue by rescaling IOPs in the Compute+Storage blade to desired value (previously set) post the compute deployment and consequent IOPS reset.
+  - In a rare scenario and after HA failover, the primary server is in read_only mode. Resolve the issue by updating “read_only” value from the server parameters page to OFF.
+  - After successfully scaling Compute on the Compute + Storage page, IOPS are reset to the SKU default. Customers can work around the issue by rescaling IOPs on the Compute + Storage page to desired value (previously set) post the compute deployment and consequent IOPS reset.
 
 ## July 2021
 
