PXC-5194 [DOCS] - clean up expected outcomes 8.4

	modified:   docs/configure-cluster-rhel.md
	modified:   docs/data-at-rest-encryption.md
	modified:   docs/faq.md
	modified:   docs/garbd-howto.md
	modified:   docs/load-balance-proxysql.md
	modified:   docs/virtual-sandbox.md
	modified:   docs/wsrep-provider-index.md
	modified:   docs/wsrep-system-index.md

Author: patrickbirch

docs/configure-cluster-rhel.md

@@ -32,9 +32,9 @@ to ports 3306, 4444, 4567 and 4568.
 
 * SELinux on all nodes is disabled.
 
-!!! admonition "Different from previous versions"
+Percona XtraDB Cluster {{vers}} creates the internal MySQL account [`mysql.pxc.internal.session`](glossary.md#mysqlpxcinternalsession), which the SST process uses to run the SQL needed for node synchronization.
 
-   The variable `wsrep_sst_auth` has been removed. Percona XtraDB Cluster {{vers}} automatically creates the system user [`mysql.pxc.internal.session`](glossary.md#mysqlpxcinternalsession). During [SST](glossary.md#sst), the user `mysql.pxc.sst.user` and the role [`mysql.pxc.sst.role`](glossary.md#mysqlpxcsstrole) are created on the donor node.
+During [SST](glossary.md#sst), that account creates the user `mysql.pxc.sst.user` on the donor node and assigns it the role [`mysql.pxc.sst.role`](glossary.md#mysqlpxcsstrole).
 
 ## Step 1. Install 
 

docs/data-at-rest-encryption.md

@@ -231,11 +231,9 @@ Run the migration server:
 --component_keyring_vault_config=/dev/shm/pxc80/vault/component_keyring_vault.cnf &
 ```
 
-??? example "Expected output"
+??? example "Expected log output"
 
     ```{.text .no-copy}
-    ... [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use
-        --explicit_defaults_for_timestamp server option (see documentation for more details).
     ... [Note] --secure-file-priv is set to NULL. Operations related to importing and
         exporting data are disabled
     ... [Warning] WSREP: Node is not a cluster node. Disabling pxc_strict_mode

docs/faq.md

@@ -159,7 +159,7 @@ To be precise, the commits are “virtually” synchronous, which means that the
 
 ## Does Percona XtraDB Cluster work with regular MySQL replication?
 
-Yes. On the node you are going to use as source, enable binary logging and replica updates: set `log_bin` and `log_replica_updates` (or the deprecated `log_slave_updates`) in your configuration.
+Yes. On the node you are going to use as source, set a unique non-zero `server_id`, enable binary logging (`log_bin`), and enable `log_replica_updates` (or the deprecated `log_slave_updates`) so cluster-applied writes are recorded in the binary log for downstream replicas.
 
 ## Why the MySQL init script does not start?
 

docs/garbd-howto.md

@@ -55,22 +55,26 @@ socket.ssl_cipher=AES128-SHA256"
 
 To avoid entering the options each time you start `garbd`, edit the options in the configuration file. To configure *Galera Arbitrator* on *Ubuntu/Debian*, edit the `/etc/default/garb` file. On RedHat or derivative distributions, the configuration can be found in `/etc/sysconfig/garb` file.
 
-The configuration file should look like this after the installation and before you have added your parameters:
+After installation, before you add your cluster settings, **`/etc/default/garb`** (Debian/Ubuntu) from **Percona XtraDB Cluster** {{vers}} packages matches the following template:
 
 ```{.text .no-copy}
-Copyright (C) 2013-2015 Codership Oy
-This config file is to be sourced by garb service script.
-REMOVE THIS AFTER CONFIGURATION
-A comma-separated list of node addresses (address[:port]) in the cluster
-GALERA_NODES=""
-Galera cluster name, should be the same as on the rest of the nodes.
-GALERA_GROUP=""
-Optional Galera internal options string (e.g. SSL settings)
-see http://galeracluster.com/documentation-webpages/galeraparameters.html
-GALERA_OPTIONS=""
-Log file for garbd. Optional, by default logs to syslog
-Deprecated for CentOS7, use journalctl to query the log for garbd
-LOG_FILE=""
+# Copyright (C) 2012 Codership Oy
+# This config file is to be sourced by garb service script.
+
+# REMOVE THIS AFTER CONFIGURATION
+
+# A comma-separated list of node addresses (address[:port]) in the cluster
+# GALERA_NODES=""
+
+# Galera cluster name, should be the same as on the rest of the nodes.
+# GALERA_GROUP=""
+
+# Optional Galera internal options string (e.g. SSL settings)
+# see http://galeracluster.com/documentation-webpages/galeraparameters.html
+# GALERA_OPTIONS=""
+
+# Log file for garbd. Optional, by default logs to syslog
+# LOG_FILE=""
 ```
 
 Add the parameter information about the cluster. For this document, we use the cluster information from [Configuring Percona XtraDB Cluster on Ubuntu](configure-cluster-ubuntu.md#configure-a-cluster-on-debian-or-ubuntu).
@@ -90,7 +94,6 @@ Optional Galera internal options string (e.g. SSL settings)
 see http://galeracluster.com/documentation-webpages/galeraparameters.html
 GALERA_OPTIONS="socket.ssl_key=/etc/ssl/mysql/server-key.pem;socket.ssl_cert=/etc/ssl/mysql/server-cert.pem;socket.ssl_ca=/etc/ssl/mysql/ca.pem;socket.ssl_cipher=AES128-SHA256"
 Log file for garbd. Optional, by default logs to syslog
-Deprecated for CentOS7, use journalctl to query the log for garbd
 LOG_FILE="/var/log/garbd.log"
 ```
 
@@ -99,57 +102,49 @@ You can now start the *Galera Arbitrator* daemon (`garbd`). Run the following co
 === "On Debian or Ubuntu"
 
     ```shell
-    service garbd start
+    systemctl start garb
     ```
 
     ??? example "Expected output"
 
         ```{.text .no-copy}
-        [ ok ] Starting /usr/bin/garbd: :.
-        ```
-
-    !!! note 
-
-        On systems that run `systemd` as the default system and service manager, use `systemctl` instead of `service` to invoke the command. Currently, both are supported.
-
-        ```shell
-        systemctl start garb
+        # No output on success
         ```
 
-=== "On Red Hat Enterprise Linux or CentOS"
+=== "On Red Hat Enterprise Linux"
 
     ```shell
-    service garb start
+    systemctl start garb
     ```
 
     ??? example "Expected output"
 
         ```{.text .no-copy}
-        [ ok ] Starting /usr/bin/garbd: :.
+        # No output on success
         ```
 
 Additionally, you can check the `arbitrator` status by running:
 
 === "On Debian or Ubuntu"
 
     ```shell
-    service garbd status
+    systemctl is-active garb
     ```
 
     ??? example "Expected output"
 
         ```{.text .no-copy}
-        [ ok ] garb is running.
+        active
         ```
 
-=== "On Red Hat Enterprise Linux or CentOS"
+=== "On Red Hat Enterprise Linux"
 
     ```shell
-    service garb status
+    systemctl is-active garb
     ```
 
     ??? example "Expected output"
 
         ```{.text .no-copy}
-        [ ok ] garb is running.
+        active
         ```