PXB-3291 Remove offensive terminology from 8.4 docs (#357)

alina-derkach-oaza · web-flow · commit b1875a134e20 · 2024-08-22T15:28:40.000+03:00
dquote&gt;         modified:   docs/binlogging-replication-improvements.md
        modified:   docs/innodb-show-status.md
        modified:   docs/percona-server-system-variables.md
        modified:   docs/quickstart-overview.md
        modified:   docs/start-transaction-with-consistent-snapshot.md
diff --git a/docs/binlogging-replication-improvements.md b/docs/binlogging-replication-improvements.md
@@ -40,18 +40,6 @@ only on log file rotation did not experience the expected reduction in load.
 *MySQL* was additionally updating this information in case of multi-source
 replication when replica had to skip the already executed GTID event.
 
-### Source and connection status details
-
-The configuration with `master_info_repository=TABLE` and
-`sync_master_info=0` makes replica to update source status and connection
-information in this table on log file rotation and not after each
-sync_master_info event, but it didn’t work on multi-source replication setups.
-Heartbeats sent to the replica to skip GTID events which it had already executed
-previously, were evaluated as relay log rotation events and reacted with
-`mysql.slave_master_info` table sync. This inaccuracy could produce huge (up
-to 5 times on some setups) increase in write load on the replica, before this
-problem was fixed in *Percona Server for MySQL*. Bug fixed [#1812](https://jira.percona.com/browse/PS-1812) (upstream [#85158](https://bugs.mysql.com/bug.php?id=85158)).
-
 ## Write `FLUSH` commands to the binary log
 
 `FLUSH` commands, such as `FLUSH SLOW LOGS`, are not written to the
diff --git a/docs/innodb-show-status.md b/docs/innodb-show-status.md
@@ -99,26 +99,6 @@ the redo log if needed due to the checkpoint age; performs change buffer merge
 at full I/O capacity; evicts tables from the dictionary cache if
 needed; and makes a checkpoint.
 
-### `Innodb_master_thread_active_loops`
-
-| Option    | Description |
-|-----------|-------------|
-| Scope     | Global      |
-| Data type | Numeric     |
-
-This variable shows the number of times the above one-second loop was executed
-for active server states.
-
-### `Innodb_master_thread_idle_loops`
-
-| Option    | Description |
-|-----------|-------------|
-| Scope     | Global      |
-| Data type | Numeric     |
-
-This variable shows the number of times the above one-second loop was executed
-for idle server states.
-
 ### `Innodb_background_log_sync`
 
 | Option    | Description |
diff --git a/docs/percona-server-system-variables.md b/docs/percona-server-system-variables.md
@@ -77,8 +77,6 @@
 | Innodb_lsn_current | Numeric | Global |
 | Innodb_lsn_flushed | Numeric | Global |
 | Innodb_lsn_last_checkpoint | Numeric | Global |
-| Innodb_master_thread_active_loops | Numeric | Global |
-| Innodb_master_thread_idle_loops | Numeric | Global |
 | Innodb_max_trx_id | Numeric | Global |
 | Innodb_mem_adaptive_hash | Numeric | Global |
 | Innodb_mem_dictionary | Numeric | Global |
diff --git a/docs/quickstart-overview.md b/docs/quickstart-overview.md
@@ -27,7 +27,7 @@ Percona Monitoring and Management (PMM )monitors and provides actionable perform
 
 ## For high availability
 
-Percona XtraDB Cluster (PXC) is a 100% open source, enterprise-grade, highly available clustering solution for MySQL multi-master setups based on Galera. PXC helps enterprises minimize unexpected downtime and data loss, reduce costs, and improve performance and scalability of your database environments supporting your critical business applications in the most demanding public, private, and hybrid cloud environments.
+Percona XtraDB Cluster (PXC) is a 100% open source, enterprise-grade, highly available clustering solution for MySQL multi-source setups based on Galera. PXC helps enterprises minimize unexpected downtime and data loss, reduce costs, and improve performance and scalability of your database environments supporting your critical business applications in the most demanding public, private, and hybrid cloud environments.
 
 [Percona XtraDB Cluster Quick start guide](https://docs.percona.com/percona-xtradb-cluster/8.0/quickstart-overview.html)
 
diff --git a/docs/start-transaction-with-consistent-snapshot.md b/docs/start-transaction-with-consistent-snapshot.md
@@ -20,7 +20,7 @@ For XtraDB, a transaction with a cloned snapshot will only see data visible or c
 
 ## mysqldump
 
-`mysqldump` has been updated to use new status variables automatically when they are supported by the server and both –single-transaction and –master-data are specified on the command line. Along with the `mysqldump` improvements introduced in [Backup Locks](backup-locks.md#backup-locks) there is now a way to generate `mysqldump` backups that are guaranteed to be consistent without using `FLUSH TABLES WITH READ LOCK` even if `--master-data` is requested.
+`mysqldump` has been updated to use new status variables automatically when they are supported by the server and both –single-transaction and –source-data are specified on the command line. Along with the `mysqldump` improvements introduced in [Backup Locks](backup-locks.md#backup-locks) there is now a way to generate `mysqldump` backups that are guaranteed to be consistent without using `FLUSH TABLES WITH READ LOCK` even if `--source-data` is requested.
 
 ## System variables
 
