Correct two more PGD links

EnterpriseDB · Apr 17, 2024 · 67d888e · 67d888e · github-actions · Apr 17, 2024
1 parent 17f1d19
commit 67d888e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx b/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx
@@ -36,7 +36,7 @@ Column-level conflict resolution requires the table to have `REPLICA IDENTITY FU
 ## Enabling and disabling column-level conflict resolution
 
 !!! Note Permissions Required
-Column level conflict detection uses the `column_timestamps` type. This requires the user to have have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) role assigned to them.
+Column level conflict detection uses the `column_timestamps` type. This requires the user to have have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned to them.
 !!!
 
 The [bdr.alter_table_conflict_detection()](conflicts#bdralter_table_conflict_detection) function manages column-level conflict resolution.

diff --git a/product_docs/docs/pgd/5/consistency/crdt.mdx b/product_docs/docs/pgd/5/consistency/crdt.mdx
@@ -8,7 +8,7 @@ redirects:
 Conflict-free replicated data types (CRDT) support merging values from concurrently modified rows instead of discarding one of the rows as traditional resolution does.
 
 !!! Note Permissions Required
-PGD CRDT require usage access to CRDT types, therefore a user must have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) role assigned to them.
+PGD CRDT require usage access to CRDT types, therefore a user must have at least the [bdr_application](../security/pgd-predefined-roles/#bdr_application) role assigned to them.
 !!!
 
 Each CRDT type is implemented as a separate PostgreSQL data type with an extra callback added to the `bdr.crdt_handlers` catalog. The merge process happens inside the PGD writer on the apply side without any user