From 8f2ba0665293464da569ef37cd0854372fe0de84 Mon Sep 17 00:00:00 2001 From: Esha Noronha Date: Tue, 23 Sep 2025 15:02:16 +0200 Subject: [PATCH] Fixed broken links --- .../reference/routing/request-pipeline/outbound-pipeline.md | 6 +++--- .../reference/routing/request-pipeline/outbound-pipeline.md | 6 +++--- .../reference/routing/request-pipeline/outbound-pipeline.md | 6 +++--- .../rich-text-editor/blocks.md | 2 +- .../reference/routing/request-pipeline/outbound-pipeline.md | 6 +++--- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md index abc88d6472a..4295940d4a1 100644 --- 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 index daa5821cd3e..0f3c7030225 100644 --- 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 index d256a0f42c0..3f41a3f2979 100644 --- 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 index 1835d3c3e6c..c32644a7b6f 100644 --- 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 index 90250cef436..083c6d7d045 100644 --- 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: