Update content

umn/source/conf.py

@@ -35,6 +35,9 @@ sys.path.insert(0, os.path.abspath('../'))
 sys.path.insert(0, os.path.abspath('./'))
 
 # -- General configuration ----------------------------------------------------
+# https://docutils.sourceforge.io/docs/user/smartquotes.html - it does not
+# what it is expected
+smartquotes = False
 
 # Add any Sphinx extension module names here, as strings. They can be
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom ones.

umn/source/faqs/how_can_i_import_the_root_certificate_to_a_windows_or_linux_os.rst

@@ -17,12 +17,12 @@ Importing the Root Certificate to the Windows OS
 #. On the console, double-click **Certificates**.
 #. Right-click **Trusted Root Certification Authorities** and choose **All Tasks** > **Import**.
 #. In the displayed **Certificate Import Wizard** dialog box, click **Next**.
-#. Click **Browse** to change the file type to **All Files (``*``.\ ``*``)**.
+#. Click **Browse** to change the file type to **All Files (*.*)**.
 #. Locate the downloaded root certificate ca.pem file and click **Open**. Then, click **Next**.
 
    .. important::
 
-      You must change the file type to **All Files (``*``.\ ``*``)** because **.pem** is not a standard certificate extension name.
+      You must change the file type to **All Files (*.*)** because **.pem** is not a standard certificate extension name.
 
 #. Click **Next**.
 #. Click **Finish**.

umn/source/faqs/how_can_i_install_the_mysql_client.rst

@@ -18,7 +18,6 @@ Procedure
    .. figure:: /_static/images/en-us_image_0291554181.png
       :alt: **Figure 1** Download
 
-
       **Figure 1** Download
 
    .. note::

umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/overview.rst

@@ -22,7 +22,6 @@ Process
 .. figure:: /_static/images/en-us_image_0291554398.png
    :alt: **Figure 1** Connecting to a DB instance over a private network
 
-
    **Figure 1** Connecting to a DB instance over a private network
 
 -  :ref:`Step 1: Create a DB instance. <gaussdb_02_0004>` Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.

umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_private_network/step_3_connect_to_a_db_instance_over_a_private_network.rst

@@ -52,7 +52,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554383.png
       :alt: **Figure 1** Connection management
 
-
       **Figure 1** Connection management
 
 #. Enter the information of the DB instance to be connected and click **Ok**, as shown in :ref:`Figure 2 <gaussdb_02_0009__en-us_topic_0171122303_fig4664143131112>`.
@@ -62,7 +61,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554184.png
       :alt: **Figure 2** Adding an account
 
-
       **Figure 2** Adding an account
 
    .. table:: **Table 1** Parameter description
@@ -92,7 +90,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554292.png
       :alt: **Figure 3** Opening a session
 
-
       **Figure 3** Opening a session
 
 SSL Connection

umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/overview.rst

@@ -22,7 +22,6 @@ Process
 .. figure:: /_static/images/en-us_image_0291554226.png
    :alt: **Figure 1** Connecting to a DB instance over a public network
 
-
    **Figure 1** Connecting to a DB instance over a public network
 
 -  :ref:`Step 1: Create a DB instance. <gaussdb_02_0012>` Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.

umn/source/getting_started_with_gaussdbfor_mysql/connecting_to_a_db_instance_over_a_public_network/step_4_connect_to_a_db_instance_over_a_public_network.rst

@@ -55,7 +55,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554155.png
       :alt: **Figure 1** Connection management
 
-
       **Figure 1** Connection management
 
 #. Enter the information of the DB instance to be connected and click **Ok**, as shown in :ref:`Figure 2 <gaussdb_02_0014__en-us_topic_0172523144_en-us_topic_0154555358_fig4664143131112>`.
@@ -65,7 +64,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554325.png
       :alt: **Figure 2** Adding an account
 
-
       **Figure 2** Adding an account
 
    .. table:: **Table 1** Parameter description
@@ -93,7 +91,6 @@ Using MySQL-Front to Connect to a DB Instance
    .. figure:: /_static/images/en-us_image_0291554160.png
       :alt: **Figure 3** Opening a session
 
-
       **Figure 3** Opening a session
 
    .. note::

umn/source/working_with_gaussdbfor_mysql/data_migration/migrating_data_to_gaussdbfor_mysql_using_mysqldump.rst

@@ -49,7 +49,7 @@ Before migrating data to GaussDB(for MySQL), you need to export data first.
 
       MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify **--all-database**. Otherwise, the databases will be unavailable.
 
-   **mysqldump** **--databases** <*DB_NAME*> **--single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF** -u <*DB_USER*> **-p -h** <*DB_ADDRESS*> **-P** <*DB_PORT*> **\|sed -e 's/DEFINER[ ]*=[ ``]*[^*]*\*/\*/'`` -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' >** *<BACKUP_FILE>*
+   **mysqldump** **--databases** <*DB_NAME*> **--single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF** -u <*DB_USER*> **-p -h** <*DB_ADDRESS*> **-P** <*DB_PORT*> **\|sed -e 's/DEFINER[ ]*=[ ]*[^*]*\\*/\\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' >** *<BACKUP_FILE>*
 
    -  **DB_NAME** indicates the name of the database to be migrated.
    -  **DB_USER** indicates the database username.
@@ -61,7 +61,7 @@ Before migrating data to GaussDB(for MySQL), you need to export data first.
 
    Example:
 
-   **mysqldump --databases gaussdb --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u root -p -h 192.168.151.18 -P 3306 \|sed -e 's/DEFINER[ ]*=[ ``]*[^*]*\*/\*/'`` -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > dump-defs.sql**
+   **mysqldump --databases gaussdb --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u root -p -h 192.168.151.18 -P 3306 \|sed -e 's/DEFINER[ ]*=[ ]*[^*]*\\*/\\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > dump-defs.sql**
 
    **Enter password:**
 

umn/source/working_with_gaussdbfor_mysql/database_connections/changing_a_database_port.rst

@@ -30,7 +30,7 @@ Procedure
       -  In the dialog box, click **Yes**.
 
          a. If you change the database port of a DB instance, the ports of the primary node and read replicas are also changed accordingly and all of them are rebooted.
-         b. This process takes about 1–5 minutes.
+         b. This process takes about 1-5 minutes.
 
    -  To cancel the change, click |image4|.
 

umn/source/working_with_gaussdbfor_mysql/db_instance_management/changing_a_db_instance_class.rst

@@ -46,7 +46,7 @@ Procedure
 
 #. View the DB instance class change result.
 
-   Changing the instance class takes 5–15 minutes. During this period, the status of the DB instance on the **Instance Management** page is **Changing instance class**. After a few minutes, click the instance and view the instance class on the displayed **Basic Information** page to check that the change is successful.
+   Changing the instance class takes 5-15 minutes. During this period, the status of the DB instance on the **Instance Management** page is **Changing instance class**. After a few minutes, click the instance and view the instance class on the displayed **Basic Information** page to check that the change is successful.
 
    .. important::