make more link edits

Author: markingmyname

articles/mysql/app-development-best-practices.md

@@ -25,13 +25,13 @@ Make sure all your dependencies are in the same region when deploying your appli
 
 ### Keep your MySQL server secure
 
-Configure your MySQL server to be [secure](./concepts-security.md) and not accessible publicly. Use one of these options to secure your server:
+Configure your MySQL server to be [secure](single-server/concepts-security.md) and not accessible publicly. Use one of these options to secure your server:
 
-- [Firewall rules](./concepts-firewall-rules.md)
-- [Virtual networks](./concepts-data-access-and-security-vnet.md)
-- [Azure Private Link](./concepts-data-access-security-private-link.md)
+- [Firewall rules](single-server/concepts-firewall-rules.md)
+- [Virtual networks](single-server/concepts-data-access-and-security-vnet.md)
+- [Azure Private Link](single-server/concepts-data-access-security-private-link.md)
 
-For security, you must always connect to your MySQL server over SSL and configure your MySQL server and your application to use TLS 1.2. See [How to configure SSL/TLS](./concepts-ssl-connection-security.md).
+For security, you must always connect to your MySQL server over SSL and configure your MySQL server and your application to use TLS 1.2. See [How to configure SSL/TLS](single-server/concepts-ssl-connection-security.md).
 
 ### Use advanced networking with AKS
 
@@ -46,17 +46,17 @@ To calculate the largest possible size of `tmp_table_size` and `max_heap_table_s
 `(total memory - (base memory + (sum of per-connection memory * # of connections)) / # of connections`
 
 > [!NOTE]
-> Total memory indicates the total amount of memory that the server has across the provisioned vCores.  For example, in a General Purpose two-vCore Azure Database for MySQL server, the total memory will be 5 GB * 2. You can find more details about memory for each tier in the [pricing tier](./concepts-pricing-tiers.md) documentation.
+> Total memory indicates the total amount of memory that the server has across the provisioned vCores.  For example, in a General Purpose two-vCore Azure Database for MySQL server, the total memory will be 5 GB * 2. You can find more details about memory for each tier in the [pricing tier](single-server/concepts-pricing-tiers.md) documentation.
 >
 > Base memory indicates the memory variables, like `query_cache_size` and `innodb_buffer_pool_size`, that MySQL will initialize and allocate at server start. Per-connection memory, like `sort_buffer_size` and `join_buffer_size`, is memory that's allocated only when a query needs it.
 
 ### Create non-admin users
 
-[Create non-admin users](./how-to-create-users.md) for each database. Typically, the user names are identified as the database names.
+[Create non-admin users](how-to-create-users.md) for each database. Typically, the user names are identified as the database names.
 
 ### Reset your password
 
-You can [reset your password](./how-to-create-manage-server-portal.md#update-admin-password) for your MySQL server by using the Azure portal.
+You can [reset your password](single-server/how-to-create-manage-server-portal.md#update-admin-password) for your MySQL server by using the Azure portal.
 
 Resetting your server password for a production database can bring down your application. It's a good practice to reset the password for any production workloads at off-peak hours to minimize the impact on your application's users.
 
@@ -66,25 +66,25 @@ Here are a few tools and practices that you can use to help debug performance is
 
 ### Enable slow query logs to identify performance issues
 
-You can enable [slow query logs](./concepts-server-logs.md) and [audit logs](./concepts-audit-logs.md) on your server. Analyzing slow query logs can help identify performance bottlenecks for troubleshooting.
+You can enable [slow query logs](single-server/concepts-server-logs.md) and [audit logs](single-server/concepts-audit-logs.md) on your server. Analyzing slow query logs can help identify performance bottlenecks for troubleshooting.
 
-Audit logs are also available through Azure Diagnostics logs in Azure Monitor logs, Azure Event Hubs, and storage accounts. See [How to troubleshoot query performance issues](./how-to-troubleshoot-query-performance.md).
+Audit logs are also available through Azure Diagnostics logs in Azure Monitor logs, Azure Event Hubs, and storage accounts. See [How to troubleshoot query performance issues](single-server/how-to-troubleshoot-query-performance.md).
 
 ### Use connection pooling
 
-Managing database connections can have a significant impact on the performance of the application as a whole. To optimize performance, you must reduce the number of times that connections are established and the time for establishing connections in key code paths. Use [connection pooling](./concepts-connectivity.md#access-databases-by-using-connection-pooling-recommended) to connect to Azure Database for MySQL to improve resiliency and performance.
+Managing database connections can have a significant impact on the performance of the application as a whole. To optimize performance, you must reduce the number of times that connections are established and the time for establishing connections in key code paths. Use [connection pooling](single-server/concepts-connectivity.md#access-databases-by-using-connection-pooling-recommended) to connect to Azure Database for MySQL to improve resiliency and performance.
 
 You can use the [ProxySQL](https://proxysql.com/) connection pooler to efficiently manage connections. Using a connection pooler can decrease idle connections and reuse existing connections, which will help avoid problems. See [How to set up ProxySQL](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/connecting-efficiently-to-azure-database-for-mysql-with-proxysql/ba-p/1279842) to learn more.
 
 ### Retry logic to handle transient errors
 
-Your application might experience [transient errors](./concepts-connectivity.md#handling-transient-errors) where connections to the database are dropped or lost intermittently. In such situations, the server is up and running after one to two retries in 5 to 10 seconds.
+Your application might experience [transient errors](single-server/concepts-connectivity.md#handling-transient-errors) where connections to the database are dropped or lost intermittently. In such situations, the server is up and running after one to two retries in 5 to 10 seconds.
 
-A good practice is to wait for 5 seconds before your first retry. Then follow each retry by increasing the wait gradually, up to 60 seconds. Limit the maximum number of retries at which point your application considers the operation failed, so you can then further investigate. See [How to troubleshoot connection errors](./how-to-troubleshoot-common-connection-issues.md) to learn more.
+A good practice is to wait for 5 seconds before your first retry. Then follow each retry by increasing the wait gradually, up to 60 seconds. Limit the maximum number of retries at which point your application considers the operation failed, so you can then further investigate. See [How to troubleshoot connection errors](single-server/how-to-troubleshoot-common-connection-issues.md) to learn more.
 
 ### Enable read replication to mitigate failovers
 
-You can use [Data-in Replication](./how-to-data-in-replication.md) for failover scenarios. When you're using read replicas, no automated failover between source and replica servers occurs.
+You can use [Data-in Replication](single-server/how-to-data-in-replication.md) for failover scenarios. When you're using read replicas, no automated failover between source and replica servers occurs.
 
 You'll notice a lag between the source and the replica because the replication is asynchronous. Network lag can be influenced by many factors, like the size of the workload running on the source server and the latency between datacenters. In most cases, replica lag ranges from a few seconds to a couple of minutes.
 
@@ -141,4 +141,4 @@ To avoid slow queries, you can use indexes. Indexes can help find rows with spec
 
 ### Use EXPLAIN for your SELECT queries
 
-Use the `EXPLAIN` statement to get insights on what MySQL is doing to run your query. It can help you detect bottlenecks or issues with your query. See [How to use EXPLAIN to profile query performance](how-to-troubleshoot-query-performance.md).
+Use the `EXPLAIN` statement to get insights on what MySQL is doing to run your query. It can help you detect bottlenecks or issues with your query. See [How to use EXPLAIN to profile query performance](single-server/how-to-troubleshoot-query-performance.md).

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

@@ -78,7 +78,10 @@ The following are unsupported:
 - With point-in-time restore, new servers are created with the same compute and storage configurations as the source server it is based on. The newly restored server's compute can be scaled down after the server is created.
 
 ## Features available in Single Server but not yet supported in Flexible Server
-Not all features available in Azure Database for MySQL - Single Server is available in Flexible Server yet. For complete list of feature comparison between single server and flexible server, refer [choosing the right MySQL Server option in Azure documentation.](../select-right-deployment-type.md#comparing-the-mysql-deployment-options-in-azure)
+Not all features available in Azure Database for MySQL - Single Server is available in Flexible Server yet. For complete list of feature comparison between single server and flexible server, refer [[choosing the right MySQL Server option in Azure documentation](../select-right-deployment-type.md#compare-the-mysql-deployment-options-in-azure)
+
+
+annot find bookmark '#comparing-the-mysql-deployment-options-in-Azure' in 'articles/mysql/select-right-deployment-type.md', did you mean '#compare-the-mysql-deployment-options-in-Azure'?
 
 ## Next steps