Merge pull request #6546 from EnterpriseDB/fix-dha-in-cs-typo

Fix quoting

Author: djw-m

advocacy_docs/edb-postgres-ai/cloud-service/references/distributed_high_availability/pgd_cli_ba.mdx

@@ -69,7 +69,8 @@ Connections       Ok     All BDR nodes are accessible
 Raft              Ok     Raft Consensus is working correctly
 Replication Slots Ok     All PGD replication slots are working correctly
 Clock Skew        Ok     Clock drift is within permissible limit
-Versions          Ok     All nodes are running the same PGD version```
+Versions          Ok     All nodes are running the same PGD version
+```
 
 ### `pgd nodes list`
 

product_docs/docs/pgd/5/cli/command_ref/replication/index.mdx

@@ -3,7 +3,7 @@ title: pgd replication
 navTitle: Replication
 ---
 
-The `pgd replicaiton` commands are used to display the various aspects of replication status in the EDB Postgres Distributed cluster.
+The `pgd replication` commands are used to display the various aspects of replication status in the EDB Postgres Distributed cluster.
 
 
 ## Subcommands

product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx

@@ -38,7 +38,7 @@ so it is something we have chosen not to support.
 TPA does not yet provide an automated mechanism for performing major
 version upgrades of Postgres. Therefore if you need to perform an
 in-place upgrade on an existing cluster this must be performed using
-other tools such as pg_upgrade or [bdr_pg_upgrade](https://www.enterprisedb.com/docs/pgd/latest/upgrades/bdr_pg_upgrade/#bdr_pg_upgrade-command-line).
+other tools such as pg_upgrade or [bdr_pg_upgrade](https://www.enterprisedb.com/docs/pgd/latest/upgrades/bdr_pg_upgrade/#pgd-node-upgrade-command-line).
 
 ## What can happen if changes are not reconciled?