TPA 23.24 updates

Signed-off-by: Dj Walker-Morgan <[email protected]>

product_docs/docs/tpa/23/INSTALL.mdx

@@ -9,7 +9,7 @@ To use TPA, you need to install from packages or source and run the
 `tpaexec setup` command. This document explains how to install TPA
 packages. If you have an EDB subscription plan, and therefore have
 access to the EDB repositories, you should follow these instructions. To
-install TPA from source, please refer to 
+install TPA from source, please refer to
 [Installing TPA from Source](INSTALL-repo/).
 
 See [Distribution support](reference/distributions/) for information
@@ -61,7 +61,7 @@ More detailed explanations of each step are given below.
 ## Where to install TPA
 
 As long as you are using a supported platform, TPA can be installed and
-run from your workstation. This is fine for learning, local testing or 
+run from your workstation. This is fine for learning, local testing or
 demonstration purposes. TPA supports [deploying to Docker containers](platform-docker/)
 should you wish to perform a complete deployment on your own workstation.
 
@@ -216,17 +216,13 @@ this, but others will not work without it.
 
 ## Ansible community support
 
-TPA now supports ansible community, you may choose to use it by
-using `--use-community-ansible` option during `tpaexec setup`, default
-will be to use the legacy 2ndQuadrant/ansible fork. This will change in
-a future release, support for 2ndQuadrant/ansible will be dropped and
-community ansible will become the new default.
+TPA now uses the community distribution of ansible by default; you can
+continue to use the 2ndQuadrant/ansible fork by passing the
+`--use-2q-ansible` option to `tpaexec setup`. In a future TPA release,
+support for the 2ndQuadrant ansible fork will be removed.
 
-notable difference:
-
--   change the `--skip-flags` options to community behavior where a
-    task will be skipped if part of the list given to the `--skip-tags`
-    option even if it is also tagged with special tag `always`.
-    TPA expects all tasks tagged with `always` to be run to ensure
-    a complete deployment, therefor `--skip-tags` should not be used when
-    using community ansible.
+For most users, this makes no difference. However, if you are using
+`--skip-tags` with 2ndQuadrant ansible, be aware that this is not supported
+An alternative means of skipping tasks, compatible with all ansible
+versions, will be provided before support for 2ndQuadrant ansible is
+removed.

product_docs/docs/tpa/23/reference/pem.mdx

@@ -28,13 +28,13 @@ requires a valid subscription.
 
 ## Supported architectures
 
-PEM is supported with M1 and BDR-Always-ON architectures via `--enable-pem`
-configuration command line option. You could optionally edit the generated
+PEM is supported with all architectures via the `--enable-pem`
+configuration command line option, with the exception of the
+BDR-Always-ON architecture when used with EDB Postgres Extended.
+You can optionally edit the generated
 cluster config (config.yml) and assign or remove `pem-agent` role from any
 postgres instance in the cluster in order to enable or disable PEM there.
 
-Note that PEM server does not support pgextended for a backend yet.
-
 ## PEM configuration
 
 TPA will configure pem agents and pem server with the appropriate
@@ -45,17 +45,17 @@ configuration at some point in future.
 PEM server's web interface is configured to run on https and uses 443 port
 for the same. PEM's webserver configuration uses self-signed certificates.
 
-Default login credentials for PEM server web interface use the postgres
-backend database user which is set to `postgres` for postgresql and
-`enterprisedb` for EPAS clusters by default. You could get the login
+The default login credentials for the PEM server web interface use the postgres
+backend database user, which is set to `postgres` for postgresql and
+`enterprisedb` for EPAS clusters by default. You can get the login
 password for the web interface by running
 `tpaexec show-password $clusterdir $user`.
 
 ## Shared PEM server
 
-Some deployments may want to use a single PEM sever for monitoring and
+Some deployments may want to use a single PEM server for monitoring and
 managing multiple clusters in the organization. Shared pem server deployment
-within tpaexec is supported via `pem_shared` variable that you could set via
+within tpaexec is supported via the `pem_shared` variable that you could set via
 `vars:` under the pem server instance for the given cluster config that plans
 to use an existing pem server. `pem_shared` is a boolean variable so possible
 values are true and false(default). When declaring a pemserver instance as