Skip to content

Commit 78f8568

Browse files
authored
Update 15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md
1 parent 378634e commit 78f8568

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The segments are created by the "Url Segment provider"
2626

2727
The DI container of an Umbraco implementation contains a collection of `UrlSegmentProviders`. This collection is populated during Umbraco start up. Umbraco ships with a `DefaultUrlSegmentProvider` and custom implementations can be added to the collection.
2828

29-
When the segments are requested for a document and culture combination, each registered `IUrlSegmentProvider` in the collection is executed in 'collection order'. Each provider can provide a segment for the document and culture, or return null.
29+
When the segments are requested for a document and culture combination, each registered `IUrlSegmentProvider` in the collection is executed in _collection order_. Each provider can provide a segment for the document and culture or return `null`.
3030

3131
Each URL segment provider is configured to either terminate after providing a segment or to allow other segments providers to be executed. When a terminating provider return a segment value for the document and culture, no further `UrlSegmentProviders` in the collection will be executed.
3232

0 commit comments

Comments
 (0)