Merge pull request #7 from markingmyname/markingmyname-mysql-may-release-notes-review

Additional editorial improvements for MySQL May 2026 release notes

Author: markingmyname

articles/mysql/flexible-server/release-notes/may-2026.md

@@ -4,15 +4,15 @@ description: Learn about the release notes for Azure Database for MySQL Flexible
 author: hariramt
 ms.author: hariramt
 ms.reviewer: maghan
-ms.date: 05/14/2026
+ms.date: 05/15/2026
 ms.service: azure-database-mysql
 ms.topic: release-notes
 ai-usage: ai-assisted
 ---
 
 # Azure Database for MySQL May 2026 version release notes
 
-The May 2026 version of Azure Database for MySQL Flexible Server is now available. Starting May 19, 2026, all new servers will automatically use this version. Existing servers upgrade during their next scheduled maintenance. To upgrade your servers earlier, enroll in the [Virtual Canary Program](https://aka.ms/mysql/virtual-canary).
+The May 2026 version of Azure Database for MySQL Flexible Server is available. Beginning May 19, 2026, all new servers automatically use this version. Existing servers upgrade during their next scheduled maintenance. To upgrade your servers earlier, enroll in the [Virtual Canary Program](https://aka.ms/mysql/virtual-canary).
 
 This version introduces enhancements, resolves known problems, and includes important security patches to ensure optimal performance and security.
 
@@ -35,11 +35,11 @@ This version doesn't include any engine version changes.
 
 - TLS certificates are now automatically renewed earlier in their lifecycle (at 84% of validity) and all certificates follow the same renewal schedule, reducing the chance of connection issues caused by certificate expiry.
 
-- During this scheduled maintenance window, a small number of servers will migrate from the current architecture to a dedicated Standard Load Balancer (SLB) - based architecture. The candidate servers will be communicated through the usual maintenance notifications. This enhancement adds a dedicated SLB to HA configurations for servers created with public access or private endpoints. By managing the MySQL data traffic path, the SLB eliminates the need for DNS changes during failovers, significantly reducing failover time. There will be a brief extra downtime (of around 30 seconds) while this migration is performed. This feature isn't supported by servers using private access with VNet integration.
+- During this scheduled maintenance window, a few servers migrate from the current architecture to a dedicated Standard Load Balancer (SLB) - based architecture. The candidate servers are communicated through the usual maintenance notifications. This enhancement adds a dedicated SLB to HA configurations for servers created with public access or private endpoints. By managing the MySQL data traffic path, the SLB eliminates the need for DNS changes during failovers, significantly reducing failover time. There's a brief extra downtime (of around 30 seconds) while this migration is performed. This feature isn't supported by servers using private access with a virtual network integration.
 
 ## Known issues fixes
 
-- Resolved an intermittent connectivity issue that could affect servers configured with private access (VNet integration), by reverting a recent change to the underlying networking stack.
+- Resolved an intermittent connectivity issue that could affect servers configured with private access (virtual network integration), by reverting a recent change to the underlying networking stack.
 - Resolved an issue where binlog copy operations could fail when an expected binlog file was missing. The service now handles this case gracefully without interrupting the operation.
 
 ## Related content