Update services-mysql.md

Fix #9244

Author: hguthrie

src/cloud/project/services-mysql.md

@@ -8,13 +8,13 @@ redirect_from:
   - /cloud/project/project-conf-files_services-mysql.html  
 ---
 
-The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2-10.4, supporting the [XtraDB](https://www.percona.com/software/mysql-database/percona-server/xtradb) storage engine and reimplemented features from MySQL 5.6 and 5.7.
+The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2 to 10.4, supporting the [XtraDB](https://www.percona.com/software/mysql-database/percona-server/xtradb) storage engine and reimplemented features from MySQL 5.6 and 5.7.
 
 {% include install/maria-db.md %}
 
 {:.bs-callout-warning}
 Be careful when upgrading MariaDB from version 10.1 to 10.2.
-MariaDB 10.1 is the last version that support XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
+MariaDB 10.1 is the last version that supports XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
 
 {% include cloud/service-config-integration-starter.md %}
 
@@ -50,12 +50,12 @@ MariaDB 10.1 is the last version that support XtraDB as the storage engine. Vers
 
 ## Set up multiple database users
 
-Optionally, you can set up multiple databases as well as multiple users with different permissions.
+Optionally, you can set up multiple databases and multiple users with different permissions.
 
-An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the .magento.app.yaml file.
+An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the `.magento.app.yaml` file. For Pro Staging and Production environments, submit a Support ticket to request the additional user.
 
 {:.bs-callout-warning}
-You cannot use multiple _databases_ with {{site.data.var.ee}} at this time, but you **can** create multiple endpoints to restrict access to the `main` database.
+You cannot use multiple _databases_ with {{site.data.var.ee}}, but you **can** create multiple endpoints to restrict access to the `main` database.
 
 Use a nested array to define the endpoints for specific user access. Each endpoint can designate access to one or more schemas (databases) and different levels of permission on each.
 
@@ -87,13 +87,13 @@ mysql:
                     main: rw
 ```
 
-In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access. This means that:
+In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access, which means:
 
 -  The `admin` user has full control of the database.
 -  The `reporter` user has SELECT privileges only.
 -  The `importer` user has SELECT, INSERT, UPDATE, and DELETE privileges.
 
-You must add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
+Add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
 
 ```yaml
 relationships:
@@ -103,13 +103,13 @@ relationships:
 ```
 
 {:.bs-callout-info}
-If you configure one MySQL user, you cannot use the [`DEFINER`](http://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
+If you configure one MySQL user, you cannot use the [`DEFINER`](https://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
 
 ## Connect to the database
 
 Accessing the MariaDB database directly requires you to use a SSH to log in to the remote server, and connect to the database.
 
-1. Log in to the remote server using SSH.
+1. Log in to the remote server using a SSH.
 
 1. Retrieve the MySQL login credentials from the `database` and `type` properties in the [$MAGENTO_CLOUD_RELATIONSHIPS]({{ site.baseurl }}/cloud/project/magento-app-properties.html#relationships) variable.
 
@@ -163,11 +163,11 @@ Accessing the MariaDB database directly requires you to use a SSH to log in to t
 
 ## Connect to secondary database
 
-In some cases, you might need to connect to the secondary database, for example to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
+Sometimes, you have to connect to the secondary database to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
 
 ## Troubleshooting
 
-See the following {{site.data.var.ee}} Support articles for help troubleshooting MySQL problems:
+See the following {{site.data.var.ee}} Support articles for help with troubleshooting MySQL problems:
 
 -  [Checking slow queries and processes MySQL](https://support.magento.com/hc/en-us/articles/360030903091-Checking-slow-queries-and-processes-MySQL-)
 -  [Create database dump on Cloud](https://support.magento.com/hc/en-us/articles/360003254334-Create-database-dump-on-Cloud)