Mop up changes

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

product_docs/docs/pgd/5/overview/index.mdx

@@ -63,13 +63,13 @@ DDL is replicated across nodes by default. DDL execution can be user controlled
 
 ## Architectural options and performance
 
-### Always On architectures
+### Always-on architectures
 
 A number of different architectures can be configured, each of which has different performance and scalability characteristics.
 
 The group is the basic building block consisting of 2+ nodes (servers). In a group, each node is in a different availability zone, with dedicated router and backup, giving immediate switchover and high availability. Each group has a dedicated replication set defined on it. If the group loses a node, you can easily repair or replace it by copying an existing node from the group.
 
-The Always On architectures are built from either one group in a single location or two groups in two separate locations. Each group provides high availability. When two groups are leveraged in remote locations, they together also provide disaster recovery (DR).
+The Always-on architectures are built from either one group in a single location or two groups in two separate locations. Each group provides high availability. When two groups are leveraged in remote locations, they together also provide disaster recovery (DR).
 
 Tables are created across both groups, so any change goes to all nodes, not just to nodes in the local group.
 

product_docs/docs/pgd/5/planning/deployments.mdx

@@ -9,7 +9,7 @@ You can deploy and install EDB Postgres Distributed products using the following
 
 -- [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. TPA's flexibility allows deployments to virtual machines, AWS cloud instances or Linux host hardware. See [Deploying with TPA](../deploy-config/deploy-tpa/deploying/) for more information.
 
-- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information.
+- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always-on clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/distributed_highavailability/) in the [BigAnimal documentation](/biganimal/latest) for more information.
 
 - [EDB Postgres Distributed for Kubernetes](/postgres_distributed_for_kubernetes/latest/) is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift.
 

product_docs/docs/pgd/5/quickstart/next_steps.mdx

@@ -9,7 +9,7 @@ description: >
 
 ### Architecture
 
-In this quick start, we created a single region cluster of high availability Postgres databases. This is the, Always On Single Location architecture, one of a range of available  PGD architectures. Other architectures include Always On Multi-Location, with clusters in multiple data centers working together, and variations of both with witness nodes enhancing resilience. Read more in [architectural options](../planning/architectures/).
+In this quick start, we created a single region cluster of high availability Postgres databases. This is the, Always-on Single Location architecture, one of a range of available  PGD architectures. Other architectures include Always-on Multi-Location, with clusters in multiple data centers working together, and variations of both with witness nodes enhancing resilience. Read more in [architectural options](../planning/architectures/).
 
 ### Postgres versions
 

product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx

@@ -8,7 +8,7 @@ redirects:
 ---
 
 
-This quick start uses TPA to set up PGD with an Always On Single Location architecture using local Docker containers.
+This quick start uses TPA to set up PGD with an Always-on Single Location architecture using local Docker containers.
 
 ## Introducing TPA and PGD
 
@@ -154,7 +154,7 @@ tpaexec configure democluster \
 ```
 
 You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which
-sets up the configuration for [PGD 5's Always On 
+sets up the configuration for [PGD 5's Always-on 
 architectures](../planning/architectures/). As part of the default architecture,
 it configures your cluster with three data nodes, cohosting three [PGD
 Proxy](../routing/proxy/) servers, along with a [Barman](../backup#physical-backup)

product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx

@@ -132,7 +132,7 @@ tpaexec configure democluster \
     --hostnames-unsorted
 ```
 
-You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always On architectures](../planning/architectures/). As part of the default architecture, it configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers and a [Barman](/backup/#physical-backup) node for backup.
+You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), which sets up the configuration for [PGD 5's Always-on architectures](../planning/architectures/). As part of the default architecture, it configures your cluster with three data nodes, cohosting three [PGD Proxy](../routing/proxy/) servers and a [Barman](/backup/#physical-backup) node for backup.
 
 For Linux hosts, specify that you're targeting a "bare" platform (`--platform bare`). TPA will determine the Linux version running on each host during deployment. See [the EDB Postgres Distributed compatibility table](https://www.enterprisedb.com/resources/platform-compatibility) for details about the supported operating systems.
 

product_docs/docs/pgd/5/repsets.mdx

@@ -263,7 +263,7 @@ This configuration looks like this:
 
 ![Multi-Region 3 Nodes Configuration](./images/always-on-2x3-aa-updated.png)
 
-This is the standard Always-On multiregion configuration as discussed in the [Choosing your architecture](planning/architectures) section.
+This is the standard Always-on multiregion configuration as discussed in the [Choosing your architecture](planning/architectures) section.
 
 ### Application Requirements