Sudheesh's changes

Author: aditiiitb

articles/mysql/flexible-server/concepts-limitations.md

@@ -63,7 +63,6 @@ The following are unsupported:
 - Connectivity method cannot be changed after creating the server. If the server is created with *Private access (VNet Integration)*, it cannot be changed to *Public access (allowed IP addresses)* after create, and vice versa
 
 ### Stop/start operation
-- Not supported with zone redundant HA configurations (both primary and standby).
 - Not supported with read replica configurations (both source and replicas).
 
 ### Scale operations

articles/mysql/flexible-server/concepts-server-parameters.md

@@ -70,7 +70,7 @@ Azure Database for MySQL Flexible Server supports at largest, **4 TB**, in a sin
 
 ### innodb_log_file_size
 
-(innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] is the size in bytes of each (log file)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_file] in a (log group)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_group]. The combined size of log files ((innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] * (innodb_log_files_in_group)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_files_in_group]) cannot exceed a maximum value that is slightly less than 512GB.). A bigger log file size is better for performance, but it has a drawback that the recovery time after a crash will be high. You need to balance recovery time in the rare event of a crash recovery versus maximizing throughput during peak operations. These can also result in longer restart times. You can configure this value up to any of these value 256MB,512MB,1GB or 2GB  in Azure database for MySQL Flexible server. The Parameter is static and requires a restart.
+(innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] is the size in bytes of each (log file)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_file] in a (log group)[https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_log_group]. The combined size of log files ((innodb_log_file_size)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_file_size] * (innodb_log_files_in_group)[https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_log_files_in_group]) cannot exceed a maximum value that is slightly less than 512GB.). A bigger log file size is better for performance, but it has a drawback that the recovery time after a crash will be high. You need to balance recovery time in the rare event of a crash recovery versus maximizing throughput during peak operations. These can also result in longer restart times. You can configure innodb_log_size to any of these values - 256MB, 512MB, 1GB or 2GB for Azure database for MySQL Flexible server. The parameter is static and requires a restart.
 
 > [!NOTE]
 > If you have changed the parameter innodb_log_file_size from default, please check if the value of "show global status like 'innodb_buffer_pool_pages_dirty'", stays at 0 for 30 sec ” to avoid restart delay.