Fixed broken links

eshanrnh · eshanrnh · commit 8f2ba0665293 · 2025-09-23T15:02:16.000+02:00
diff --git a/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md
@@ -6,9 +6,9 @@ meta.Title: Outbound request pipeline
 
 The **outbound pipeline** consists out of the following steps:
 
-1. [Create segments](outbound-pipeline.md#segments)
-2. [Create paths](outbound-pipeline.md#paths)
-3. [Create urls](outbound-pipeline.md#urls)
+1. [Create segments](#1-create-segments)
+2. [Create paths](#2-create-paths)
+3. [Create urls](#3-creating-urls)
 
 To explain things we will use the following content tree:
 
diff --git a/13/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md
@@ -6,9 +6,9 @@ description: How the Umbraco outbound request pipeline works
 
 The **outbound pipeline** consists out of the following steps:
 
-1. [Create segments](outbound-pipeline.md#segments)
-2. [Create paths](outbound-pipeline.md#paths)
-3. [Create urls](outbound-pipeline.md#urls)
+1. [Create segments](#1-create-segments)
+2. [Create paths](#2-create-paths)
+3. [Create urls](#3-creating-urls)
 
 To explain things we will use the following content tree:
 
diff --git a/15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md
@@ -6,9 +6,9 @@ description: How the Umbraco outbound request pipeline works
 
 The **outbound pipeline** consists out of the following steps:
 
-1. [Create segments](outbound-pipeline.md#segments)
-2. [Create paths](outbound-pipeline.md#paths)
-3. [Create urls](outbound-pipeline.md#urls)
+1. [Create segments](#1-create-segments)
+2. [Create paths](#2-create-paths)
+3. [Create urls](#3-creating-urls)
 
 To explain things we will use the following content tree:
 
diff --git a/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/blocks.md b/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/blocks.md
@@ -1,6 +1,6 @@
 # Blocks
 
-Blocks enable editors to insert structured content elements directly into the Rich Text Editor (RTE). Blocks are [Element Types](../../../../../../data/defining-content/default-document-types.md#element-type) and can be configured with custom properties, styling, and behavior.
+Blocks enable editors to insert structured content elements directly into the Rich Text Editor (RTE). Blocks are [Element Types](../../../../data/defining-content/default-document-types.md#element-type) and can be configured with custom properties, styling, and behavior.
 
 Blocks can be added to the Rich Text Editor when:
 
diff --git a/16/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/16/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md
@@ -6,9 +6,9 @@ description: How the Umbraco outbound request pipeline works
 
 The **outbound pipeline** consists out of the following steps:
 
-1. [Create segments](outbound-pipeline.md#segments)
-2. [Create paths](outbound-pipeline.md#paths)
-3. [Create urls](outbound-pipeline.md#urls)
+1. [Create segments](#1-create-segments)
+2. [Create paths](#2-create-paths)
+3. [Create urls](#3-creating-urls)
 
 To explain things we will use the following content tree:
 
