Link fixes

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>

Author: djw-m

product_docs/docs/pgd/6/concepts/connection-management.mdx

@@ -7,5 +7,5 @@ To ensure that clients can connect to the right nodes in the distributed cluster
 This system is designed to ensure that clients can access the data they need while maintaining the performance and availability of the cluster. 
 Unlike Proxy systems, this connection management system is built into the database instance itself, allowing for more efficient and reliable connections.
 
-Read more about the [Connection Management feature in PGD](/pgd/latest/reference/connection-management/) for full details.
+Read more about the [Connection Management feature in PGD](/pgd/latest/reference/connection-manager/) for full details of the implementation.
 

product_docs/docs/pgd/6/concepts/geo-distributed-clusters renamed to product_docs/docs/pgd/6/concepts/geo-distributed-clusters.mdx

@@ -6,6 +6,7 @@ navigation:
 - essential-standard
 - essential-near-far
 - first-cluster
+- first-steps
 - expanded-examples
 ---
 

product_docs/docs/pgd/6/get-started/index.mdx

@@ -31,7 +31,7 @@ In the future, one node will be elected as the main replicator to other groups,
 
 PGD is compatible with [PostgreSQL](https://www.postgresql.org/), [EDB Postgres Extended Server](/pge/latest), and [EDB Postgres Advanced Server](/epas/latest) and is deployed as a standard Postgres extension named BDR. See [Compatibility](/pgd/latest/compatibility) for details about supported version combinations.
 
-Some key PGD features depend on certain core capabilities being available in the target Postgres database server. Therefore, PGD users must also adopt the Postgres database server distribution that's best suited to their business needs. For example, if having the PGD feature Commit At Most Once (CAMO) is mission critical to your use case, don't adopt the community PostgreSQL distribution. It doesn't have the core capability required to handle CAMO. See the full feature matrix compatibility in [Choosing a Postgres distribution](../planning/choosing_server/).
+Some key PGD features depend on certain core capabilities being available in the target Postgres database server. Therefore, PGD users must also adopt the Postgres database server distribution that's best suited to their business needs. For example, if having the PGD feature Commit At Most Once (CAMO) is mission critical to your use case, don't adopt the community PostgreSQL distribution. It doesn't have the core capability required to handle CAMO. 
 
 PGD offers close-to-native Postgres compatibility. However, some access patterns don't necessarily work as well in multi-node setup as they do on a single instance. There are also some limitations in what you can safely replicate in a multi-node setting. [Application usage](../appusage) goes into detail about how PGD behaves from an application development perspective.
 

product_docs/docs/pgd/6/reference/overview/architecture-and-performance.mdx

@@ -66,7 +66,7 @@ function. This function takes a standard PostgreSQL sequence and marks it as
 a PGD global sequence. It can also convert the sequence back to the standard
 PostgreSQL sequence.
 
-PGD also provides the configuration variable [`bdr.default_sequence_kind`](/pgd/latest/reference/table-views-functions/pgd-settings/#bdrdefault_sequence_kind). This variable
+PGD also provides the configuration variable [`bdr.default_sequence_kind`](/pgd/latest/reference/tables-views-functions/pgd-settings/#bdrdefault_sequence_kind). This variable
 determines the kind of sequence to create when the `CREATE SEQUENCE`
 command is executed or when a `serial`, `bigserial`, or
 `GENERATED BY DEFAULT AS IDENTITY` column is created. Valid settings are:
@@ -90,7 +90,7 @@ The `currval()` and `lastval()` functions work correctly for all types of global
 
 ## Automatic sequence conversion
 
-In PGD 6.0 and later, the act of joining a node to a PGD group or creating a new grou also triggers a conversion of any local sequences into global sequences. Set [`bdr.default_sequence_kind`](/pgd/latest/reference/pgd-settings/#bdrdefault_sequence_kind) to `distributed`. This setting then selects the best kind of sequence to convert the local sequences into. If `bdr.default_sequence_kind` is set to `local`, the sequences are left as local sequences. Conversions to `galloc` are performed in a way that ensures that the sequence doesn't conflict with any other sequences in the group.
+In PGD 6.0 and later, the act of joining a node to a PGD group or creating a new grou also triggers a conversion of any local sequences into global sequences. Set [`bdr.default_sequence_kind`](/pgd/latest/reference/tables-views-functions/pgd-settings/#bdrdefault_sequence_kind) to `distributed`. This setting then selects the best kind of sequence to convert the local sequences into. If `bdr.default_sequence_kind` is set to `local`, the sequences are left as local sequences. Conversions to `galloc` are performed in a way that ensures that the sequence doesn't conflict with any other sequences in the group.
 
 If you decide to start with local sequences and later switch to galloc sequences, you can do so by setting `bdr.default_sequence_kind` to `galloc` and then running the `bdr.alter_sequence_set_kind()` function on each sequence you want to convert. Be aware, though, that you need to manually set the starting values of the sequences to ensure that they don't conflict with any existing values in the table. See [Converting a local sequence to a galloc sequence](#converting-a-local-sequence-to-a-galloc-sequence) for more information about this in general and specifically [How to set a new start value for a sequence](#2-set-a-new-start-value-for-the-sequence).