diff --git a/website/docs/usage/rule-based-matching.md b/website/docs/usage/rule-based-matching.md
index 2354092f0..46cb1dacb 100644
--- a/website/docs/usage/rule-based-matching.md
+++ b/website/docs/usage/rule-based-matching.md
@@ -169,7 +169,7 @@ rule-based matching are:
 |  `LIKE_NUM`, `LIKE_URL`, `LIKE_EMAIL`  | bool    | Token text resembles a number, URL, email.                                                       |
 |  `POS`, `TAG`, `DEP`, `LEMMA`, `SHAPE` | unicode | The token's simple and extended part-of-speech tag, dependency label, lemma, shape.              |
 | `ENT_TYPE`                             | unicode | The token's entity label.                                                                        |
-| `_` <Tag variant="new">2.1</Tag>       | dict    | Properties in [custom extension attributes](/processing-pipelines#custom-components-attributes). |
+| `_` <Tag variant="new">2.1</Tag>       | dict    | Properties in [custom extension attributes](/usage/processing-pipelines#custom-components-attributes). |
 
 <Infobox title="Tip: Try the interactive matcher explorer">
 
@@ -1140,7 +1140,7 @@ To apply this logic automatically when we process a text, we can add it to the
 above logic also expects that entities are merged into single tokens. spaCy
 ships with a handy built-in `merge_entities` that takes care of that. Instead of
 just printing the result, you could also write it to
-[custom attributes](/processing-pipelines#custom-components-attributes) on the
+[custom attributes](/usage/processing-pipelines#custom-components-attributes) on the
 entity `Span` – for example `._.orgs` or `._.prev_orgs` and `._.current_orgs`.
 
 > #### Merging entities