Merge pull request #232278 from markingmyname/mysqlrename

[SCOPED] [MySQL] Renamed Single Server to its right Proper name format (Bulk edit)

Author: denrea

articles/mysql/flexible-server/connect-java.md

@@ -15,7 +15,7 @@ ms.date: 10/20/2022
 
 [[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-This topic demonstrates creating a sample application that uses Java and [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity) to store and retrieve information in [Azure Database for MySQL - Flexible Server](./index.yml).
+This topic demonstrates creating a sample application that uses Java and [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity) to store and retrieve information in [Azure Database for MySQL - Flexible Server](../index.yml).
 
 JDBC is the standard Java API to connect to traditional relational databases.
 

articles/mysql/single-server/azure-pipelines-mysql-deploy.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Pipelines task for Azure Database for MySQL Single Server 
+title: Azure Pipelines task for Azure Database for MySQL single server 
 description: Enable Azure Database for MySQL Flexible Server CLI  task for using with Azure Pipelines
 ms.topic: how-to
 ms.service: mysql
@@ -10,11 +10,11 @@ author: juliakm
 ms.date: 09/14/2022
 ---
 
-# Azure Pipelines for Azure Database for MySQL Single Server
+# Azure Pipelines for Azure Database for MySQL single server
 
 Get started with Azure Database for MySQL by deploying a database update with Azure Pipelines. Azure Pipelines lets you build, test, and deploy with continuous integration (CI) and continuous delivery (CD) using [Azure DevOps](/azure/devops/). 
 
-You'll use the [Azure Database for MySQL Deployment task](/azure/devops/pipelines/tasks/deploy/azure-mysql-deployment). The Azure Database for MySQL Deployment task only works with Azure Database for MySQL Single Server.
+You'll use the [Azure Database for MySQL Deployment task](/azure/devops/pipelines/tasks/deploy/azure-mysql-deployment). The Azure Database for MySQL Deployment task only works with Azure Database for MySQL single server.
 
 ## Prerequisites
 

articles/mysql/single-server/concept-operation-excellence-best-practices.md

@@ -9,7 +9,7 @@ ms.author: sumuth
 ms.date: 06/20/2022
 ---
 
-# Best practices for server operations on Azure Database for MySQL - Single server
+# Best practices for server operations on Azure Database for MySQL - Single Server
 
 [!INCLUDE[applies-to-mysql-single-flexible-server](../includes/applies-to-mysql-single-flexible-server.md)]
 

articles/mysql/single-server/concepts-audit-logs.md

@@ -49,7 +49,7 @@ Other parameters you can adjust include:
 
 Audit logs are integrated with Azure Monitor Diagnostic Logs. Once you've enabled audit logs on your MySQL server, you can emit them to Azure Monitor logs, Event Hubs, or Azure Storage. To learn more about how to enable diagnostic logs in the Azure portal, see the [audit log portal article](how-to-configure-audit-logs-portal.md#set-up-diagnostic-logs).
 
->[!Note]
+>[!NOTE]
 >Premium Storage accounts are not supported if you sending the logs to Azure storage via diagnostics and settings 
 
 ## Diagnostic Logs Schemas

articles/mysql/single-server/concepts-backup.md

@@ -122,7 +122,7 @@ You may need to wait for the next transaction log backup to be taken before you
 ### Geo-restore
 
 You can restore a server to another Azure region where the service is available if you have configured your server for geo-redundant backups. 
-- General purpose storage v1 servers (supporting up to 4-TB storage) can be restored to the geo-paired region, or to any Azure region that supports Azure Database for MySQL Single Server service.
+- General purpose storage v1 servers (supporting up to 4-TB storage) can be restored to the geo-paired region, or to any Azure region that supports Azure Database for MySQL - Single Server service.
 - General purpose storage v2 servers (supporting up to 16-TB storage) can only be restored to Azure regions that support General purpose storage v2 servers infrastructure. 
 Review [Azure Database for MySQL pricing tiers](./concepts-pricing-tiers.md#storage) for the list of supported regions.
 

articles/mysql/single-server/concepts-business-continuity.md

@@ -21,7 +21,7 @@ This article describes the capabilities that Azure Database for MySQL provides f
 
 As you develop your business continuity plan, you need to understand the maximum acceptable time before the application fully recovers after the disruptive event - this is your Recovery Time Objective (RTO). You also need to understand the maximum amount of recent data updates (time interval) the application can tolerate losing when recovering after the disruptive event - this is your Recovery Point Objective (RPO).
 
-Azure Database for MySQL Single Server provides business continuity and disaster recovery features that include geo-redundant backups with the ability to initiate geo-restore, and deploying read replicas in a different region. Each has different characteristics for the recovery time and the potential data loss. With [Geo-restore](concepts-backup.md) feature, a new server is created using the backup data that is replicated from another region. The overall time it takes to restore and recover depends on the size of the database and the amount of logs to recover. The overall time to establish the server varies from few minutes to few hours. With [read replicas](concepts-read-replicas.md), transaction logs from the primary are asynchronously streamed to the replica. In the event of a primary database outage due to a zone-level or a region-level fault, failing over to the replica provides a shorter RTO and reduced data loss.
+Azure Database for MySQL single server provides business continuity and disaster recovery features that include geo-redundant backups with the ability to initiate geo-restore, and deploying read replicas in a different region. Each has different characteristics for the recovery time and the potential data loss. With [Geo-restore](concepts-backup.md) feature, a new server is created using the backup data that is replicated from another region. The overall time it takes to restore and recover depends on the size of the database and the amount of logs to recover. The overall time to establish the server varies from few minutes to few hours. With [read replicas](concepts-read-replicas.md), transaction logs from the primary are asynchronously streamed to the replica. In the event of a primary database outage due to a zone-level or a region-level fault, failing over to the replica provides a shorter RTO and reduced data loss.
 
 > [!NOTE]
 > The lag between the primary and the replica depends on the latency between the sites, the amount of data to be transmitted and most importantly on the write workload of the primary server. Heavy write workloads can generate significant lag. 

articles/mysql/single-server/concepts-certificate-rotation.md

@@ -9,13 +9,13 @@ ms.author: sumuth
 ms.date: 06/20/2022
 ---
 
-# Understanding the changes in the Root CA change for Azure Database for MySQL Single Server
+# Understanding the changes in the Root CA change for Azure Database for MySQL single server
 
 [!INCLUDE[applies-to-mysql-single-server](../includes/applies-to-mysql-single-server.md)]
 
 [!INCLUDE[azure-database-for-mysql-single-server-deprecation](../includes/azure-database-for-mysql-single-server-deprecation.md)]
 
-Azure Database for MySQL Single Server as part of standard maintenance and security best practices will complete the root certificate change starting October 2022. This article gives you more details about the changes, the resources affected, and the steps needed to ensure that your application maintains connectivity to your database server.
+Azure Database for MySQL single server as part of standard maintenance and security best practices will complete the root certificate change starting October 2022. This article gives you more details about the changes, the resources affected, and the steps needed to ensure that your application maintains connectivity to your database server.
 
 > [!NOTE]
 > This article applies to [Azure Database for MySQL - Single Server](single-server-overview.md) ONLY. For [Azure Database for MySQL - Flexible Server](../flexible-server/overview.md), the certificate needed to communicate over SSL is [DigiCert Global Root CA](https://dl.cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem)
@@ -181,7 +181,7 @@ To verify if you're using SSL connection to connect to the server refer [SSL ver
 No. There's no action needed if your certificate file already has the **DigiCertGlobalRootG2**.
 
 #### Why do I need to update my root certificate if I am using PHP driver with [enableRedirect](./how-to-redirection.md) ?
-To address compliance requirements, the CA certificates of the host server were changed from BaltimoreCyberTrustRoot to DigiCertGlobalRootG2. With this update, database connections using the PHP Client driver with enableRedirect can no longer connect to the server, as the client devices are unaware of the certificate change and the new root CA details. Client devices that use PHP redirection drivers connect directly to the host server, bypassing the gateway. Refer this [link](single-server-overview.md#high-availability) for more on architecture of Azure Database for MySQL Single Server.
+To address compliance requirements, the CA certificates of the host server were changed from BaltimoreCyberTrustRoot to DigiCertGlobalRootG2. With this update, database connections using the PHP Client driver with enableRedirect can no longer connect to the server, as the client devices are unaware of the certificate change and the new root CA details. Client devices that use PHP redirection drivers connect directly to the host server, bypassing the gateway. Refer this [link](single-server-overview.md#high-availability) for more on architecture of Azure Database for MySQL single server.
 
 #### What if I have further questions?
 

articles/mysql/single-server/concepts-compatibility.md

@@ -15,10 +15,10 @@ ms.date: 06/20/2022
 
 [!INCLUDE[azure-database-for-mysql-single-server-deprecation](../includes/azure-database-for-mysql-single-server-deprecation.md)]
 
-This article describes the drivers and management tools that are compatible with Azure Database for MySQL Single Server.
+This article describes the drivers and management tools that are compatible with Azure Database for MySQL single server.
 
 > [!NOTE]
-> This article is only applicable to Azure Database for MySQL Single Server to ensure drivers are compatible with [connectivity architecture](concepts-connectivity-architecture.md) of Single Server service. [Azure Database for MySQL Flexible Server](../flexible-server/overview.md) is compatible with all the drivers and tools supported and compatible with MySQL community edition.
+> This article is only applicable to Azure Database for MySQL single server to ensure drivers are compatible with [connectivity architecture](concepts-connectivity-architecture.md) of Single Server service. [Azure Database for MySQL Flexible Server](../flexible-server/overview.md) is compatible with all the drivers and tools supported and compatible with MySQL community edition.
 
 ## MySQL Drivers
 Azure Database for MySQL uses the world's most popular community edition of MySQL database. As such, it's compatible with a wide variety of programming languages and drivers. The goal is to support the three most recent versions MySQL drivers, and efforts with authors from the open-source community to constantly improve the functionality and usability of MySQL drivers continue. A list of drivers that have been tested and found to be compatible with Azure Database for MySQL 5.6 and 5.7 is provided in the following table:

articles/mysql/single-server/concepts-data-access-security-private-link.md

@@ -117,8 +117,8 @@ If you want to rely only on private endpoints for accessing their Azure Database
 
 When this setting is set to *YES*, only connections via private endpoints are allowed to your Azure Database for MySQL. When this setting is set to *NO*, clients can connect to your Azure Database for MySQL based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, customers cannot add and/or update existing 'Firewall rules' and 'VNet service endpoint rules'.
 
-> [!Note]
-> This feature is available in all Azure regions where Azure Database for MySQL - Single server supports General Purpose and Memory Optimized pricing tiers.
+> [!NOTE]
+> This feature is available in all Azure regions where Azure Database for MySQL - Single Server supports General Purpose and Memory Optimized pricing tiers.
 >
 > This setting does not have any impact on the SSL and TLS configurations for your Azure Database for MySQL.
 

articles/mysql/single-server/concepts-data-in-replication.md

@@ -46,7 +46,7 @@ Data-in Replication is only supported in General Purpose and Memory Optimized pr
 
 The private link for Azure database for MySQL support only inbound connections. As data-in replication requires outbound connection from service private link is not supported for the data-in traffic.
 
->[!Note]
+>[!NOTE]
 >GTID is supported on versions 5.7 and 8.0 and only on servers that support storage up to 16 TB (General purpose storage v2).
 
 ### Requirements