diff --git a/content/client-server-api/modules/push.md b/content/client-server-api/modules/push.md
index 930a8bad..d3832661 100644
--- a/content/client-server-api/modules/push.md
+++ b/content/client-server-api/modules/push.md
@@ -214,7 +214,7 @@ The following conditions are defined:
 
 This is a glob pattern match on a property of the event. Parameters:
 
--   `key`: The [dot-separated path of the property](/appendices#dot-separated property paths)
+-   `key`: The [dot-separated path of the property](/appendices#dot-separated-property-paths)
     of the event to match, e.g. `content.body`.
 
 -   `pattern`: The [glob-style pattern](/appendices#glob-style-matching) to match against.
@@ -297,7 +297,7 @@ For an example of this, see the default rule
 
 This is an exact value match on a property of the event. Parameters:
 
--   `key`: The [dot-separated path of the property](/appendices#dot-separated property paths)
+-   `key`: The [dot-separated path of the property](/appendices#dot-separated-property-paths)
     of the event to match, e.g. `content.body`.
 
 -   `value`: The value to match against.
@@ -341,7 +341,7 @@ The following `m.federate` values will NOT match:
 
 This matches if an array property of an event exactly contains a value. Parameters:
 
--   `key`: The [dot-separated path of the property](/appendices#dot-separated property paths)
+-   `key`: The [dot-separated path of the property](/appendices#dot-separated-property-paths)
     of the event to match, e.g. `content.body`.
 
 -   `value`: The value to match against.
diff --git a/data/api/client-server/definitions/sync_filter.yaml b/data/api/client-server/definitions/sync_filter.yaml
index d38029e5..1b98db1f 100644
--- a/data/api/client-server/definitions/sync_filter.yaml
+++ b/data/api/client-server/definitions/sync_filter.yaml
@@ -16,7 +16,7 @@ title: Filter
 properties:
   event_fields:
     description: List of event fields to include. If this list is absent then all
-      fields are included. The entries are [dot-separated paths for each property](/appendices#dot-separated property paths)
+      fields are included. The entries are [dot-separated paths for each property](/appendices#dot-separated-property-paths)
       to include. So ['content.body'] will include the 'body' field of the 'content' object.
       A server may include more fields than were requested.
     items: