From 07ffafe1a25eacce2212421926997cf9f7231c09 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Wed, 6 Mar 2024 15:50:49 +0100 Subject: [PATCH 01/10] Change i.e. to that is --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 559b27cd07c..06d1dd8d2af 100644 --- a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -24,7 +24,7 @@ public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object i.e. a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". It contains the content to render: From e5ce2b4c616e64746dde35fa17abe72cc4e0eded Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Wed, 6 Mar 2024 15:51:22 +0100 Subject: [PATCH 02/10] Change e.g. to for example --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 06d1dd8d2af..ab8ba7fefd1 100644 --- a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -45,7 +45,7 @@ public ITemplate Template {get; } The published request is created using the `PublishedRequestBuilder` which implements `IPublishedRequestBuilder`, it's only in this builder that it's possible to set values, such as domain, culture, published content, redirects and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! e.g. content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: ```csharp using Umbraco.Cms.Core.Events; From af0fc356b9cc126dcdd9ce685517ba61e51196d2 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Wed, 6 Mar 2024 15:52:57 +0100 Subject: [PATCH 03/10] Write shorter sentences --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index ab8ba7fefd1..2f9853cb07b 100644 --- a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -43,7 +43,7 @@ public string GetTemplateAlias { get; } public ITemplate Template {get; } ``` -The published request is created using the `PublishedRequestBuilder` which implements `IPublishedRequestBuilder`, it's only in this builder that it's possible to set values, such as domain, culture, published content, redirects and so on. +The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: From 847fba8cca1b507f16d94e705ed959368796e4a7 Mon Sep 17 00:00:00 2001 From: Erik-Jan Westendorp Date: Wed, 6 Mar 2024 15:57:00 +0100 Subject: [PATCH 04/10] Update v10 & 12 --- .../reference/routing/request-pipeline/inbound-pipeline.md | 6 +++--- .../reference/routing/request-pipeline/inbound-pipeline.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 17e13f8fd59..b3bafc806a4 100644 --- a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -26,7 +26,7 @@ public bool HasDomain { get; } public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object i.e. a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". It contains the content to render: @@ -45,9 +45,9 @@ public string GetTemplateAlias { get; } public ITemplate Template {get; } ``` -The published request is created using the `PublishedRequestBuilder` which implements `IPublishedRequestBuilder`, it's only in this builder that it's possible to set values, such as domain, culture, published content, redirects and so on. +The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! e.g. content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: ```C# using Umbraco.Cms.Core.Events; diff --git a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 559b27cd07c..2f9853cb07b 100644 --- a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -24,7 +24,7 @@ public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object i.e. a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". It contains the content to render: @@ -43,9 +43,9 @@ public string GetTemplateAlias { get; } public ITemplate Template {get; } ``` -The published request is created using the `PublishedRequestBuilder` which implements `IPublishedRequestBuilder`, it's only in this builder that it's possible to set values, such as domain, culture, published content, redirects and so on. +The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! e.g. content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: ```csharp using Umbraco.Cms.Core.Events; From 55c5e5dc141f5128c794cc3ed4174c16debb1663 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:40:41 +0100 Subject: [PATCH 05/10] Update 10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index b3bafc806a4..ae0b7ec428c 100644 --- a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -26,7 +26,7 @@ public bool HasDomain { get; } public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified for example "https://example.com/". It contains the content to render: From 44b1788ba544bc17532de9678116351afe202702 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:40:46 +0100 Subject: [PATCH 06/10] Update 10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index ae0b7ec428c..27aea8e1a7b 100644 --- a/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/10/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -47,7 +47,7 @@ public ITemplate Template {get; } The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! For example content, template, etc: ```C# using Umbraco.Cms.Core.Events; From e38465d72ab8c9950310adf529fd02fa62fbee62 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:40:51 +0100 Subject: [PATCH 07/10] Update 12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 2f9853cb07b..37cc75865ce 100644 --- a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -24,7 +24,7 @@ public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified for example "https://example.com/". It contains the content to render: From 1c11fb46b8a4f476d2027ef960dab81cca0a56d5 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:40:55 +0100 Subject: [PATCH 08/10] Update 13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 2f9853cb07b..37cc75865ce 100644 --- a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -24,7 +24,7 @@ public DomainAndUri Domain { get; } public CultureInfo Culture { get; } ``` -Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified e.g. "https://example.com/". +Domain is a DomainAndUri object that is a standard Domain plus the fully qualified uri. For example, the Domain may contain "example.com" whereas the Uri will be fully qualified for example "https://example.com/". It contains the content to render: From fc03c8370fa6bb49c322e9451a72d5e6b9716a67 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:40:59 +0100 Subject: [PATCH 09/10] Update 12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 37cc75865ce..f98da3d49bd 100644 --- a/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/12/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -45,7 +45,7 @@ public ITemplate Template {get; } The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! For example content, template, etc: ```csharp using Umbraco.Cms.Core.Events; From aa49a9d985a63d1c0f6e6212700ab5826133a888 Mon Sep 17 00:00:00 2001 From: Alina-Magdalena Tincas <83591955+alina-tincas@users.noreply.github.com> Date: Thu, 7 Mar 2024 13:41:03 +0100 Subject: [PATCH 10/10] Update 13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md --- .../reference/routing/request-pipeline/inbound-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md index 37cc75865ce..f98da3d49bd 100644 --- a/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md +++ b/13/umbraco-cms/reference/routing/request-pipeline/inbound-pipeline.md @@ -45,7 +45,7 @@ public ITemplate Template {get; } The published request is created using the `PublishedRequestBuilder`, which implements `IPublishedRequestBuilder`. It's only in this builder that it's possible to set values, such as domain, culture, published content, redirects, and so on. -You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! for example content, template, etc: +You can subscribe to the 'routing request' notification, which is published right after the `PublishedRequestBuilder` has been prepared, but before the request is built, and processed. Here you can modify anything in the request before it is built and processed! For example content, template, etc: ```csharp using Umbraco.Cms.Core.Events;