[MySQL] August Release notes

Author: markingmyname

articles/mysql/concepts-version-policy.md

@@ -35,7 +35,7 @@ To check your engine version, run `SELECT VERSION();` command at the MySQL promp
 
 - Expose old_alter_table for 8.0.x.
 
-## Known issues fix(es)
+## Known issues fixes
 
 - Fixed the issue where `GTID RESET` operation's retry interval was excessively long.
 - Fixed the issue that data-in HA failover stuck because of system table corrupt

articles/mysql/flexible-server/release-notes/april-2024.md

@@ -30,7 +30,7 @@ No new features are being introduced in this maintenance update.
 
 - Many security improvements have been made to the service during this maintenance.
 
-## Known issues fix(es)
+## Known issues fixes
 
 - Fix the issue that for some servers migrated from single server to flexible server, execute table partition leads to table corrupted
 - Fix the issue that for some servers with audit/slow log enabled, when a large number of logs are generated, these servers might be missing server metrics, and start operation might be stuck for these servers if they are in a stopped state.

articles/mysql/flexible-server/release-notes/august-2024.md

@@ -32,7 +32,7 @@ There will be no new features in this maintenance update.
 
 There will be no new improvement in this maintenance update.
 
-## Known issues fix(es)
+## Known issues fixes
 
 - Fix HA standby replication dead lock issue caused by slave_preserve_commit_order.
 - Fix promotion stuck issue when source server is unavailable or source region is down. Improve customer experience on replica promotion to better support disaster recovery.

articles/mysql/flexible-server/release-notes/february-2024.md

@@ -32,7 +32,7 @@ There will be no engine version changes in this maintenance update.
 
 - In alignment with our users' expectations for the audit log, we have introduced wildcard support for audit log usernames and added connection status for connection logs.
 
-## Known issues fix(es)
+## Known issues fixes
 
 ### Support Data-in Replication in Major Version Upgrade
 

articles/mysql/flexible-server/release-notes/january-2024.md

@@ -29,7 +29,7 @@ No new features are being introduced in this maintenance update.
 - Allow customers to truncate performance_schema tables by invoking a predefined stored procedure.
 - Improve the startup time for servers with large amount of tablespaces.
 
-## Known issues fix(es)
+## Known issues fixes
 
 - Fixed the issue that MySQL engine might not receive the shutdown signal during scaling and maintenance, which might lead to long recovery time.
 - Fixed the issue that if server with originalPrimaryName is deleted due to HA failover->disable HA action, earlier ATP update operation failed.

articles/mysql/flexible-server/release-notes/june-2024.md

@@ -30,9 +30,9 @@ To check your engine version, run `SELECT VERSION();` command at the MySQL promp
 
 - Improved server restart logic, server restart has a timeout of 2 hours for none burstable servers, 4 hours timeout for burstable servers. After server restart workflow timeout, it would roll back and set the server state to Succeeded.
 - Improved the data-in replication procedures to show the real error message and safe exit when exception happens.
-- Improved the read replica creation workflow to precheck the virtual network setting.
+- Read replica improvement for the creation workflow to precheck the virtual network setting.
 
-## Known issues fix(es)
+## Known issues fixes
 
 - Fixed the issue that the server parameter max_connections and table_open_cache can't be configured correctly
 - Fixed the issue where executing `CREATE AADUSER IF NOT EXISTS 'myuser' IDENTIFIED BY 'CLIENT_ID'` when the user already exists incorrectly set the binlog record, affecting replica and high availability functionalities.