From 543734440c36f9a295ef6fc8708249d1c870bb56 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:14:52 +0100 Subject: [PATCH 01/42] myCustomRuleIdentifyer -> myCustomRuleIdentifier --- 16/umbraco-cms/customizing/property-level-ui-permissions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/16/umbraco-cms/customizing/property-level-ui-permissions.md b/16/umbraco-cms/customizing/property-level-ui-permissions.md index 4be2397df66..2c385c1a233 100644 --- a/16/umbraco-cms/customizing/property-level-ui-permissions.md +++ b/16/umbraco-cms/customizing/property-level-ui-permissions.md @@ -78,7 +78,7 @@ export class MyDocumentPropertyPermissionWorkspaceContext extends UmbControllerB // Create a rule: const rule = { - unique: 'myCustomRuleIdentifyer', + unique: 'myCustomRuleIdentifier', permitted: false, message: "None of these properties are writable because of my custom restriction.", } @@ -122,7 +122,7 @@ export class MyDocumentPropertyPermissionWorkspaceContext extends UmbControllerB if(property) { // Create a guard rule: const rule = { - unique: 'myCustomRuleIdentifyer', + unique: 'myCustomRuleIdentifier', permitted: false, message: "The property is not writable because of my custom restriction.", propertyType: { @@ -158,7 +158,7 @@ import type { UmbVariantId } from '@umbraco-cms/backoffice/variant'; // Create a guard rule: const rule = { - unique: 'myCustomRuleIdentifyer', + unique: 'myCustomRuleIdentifier', permitted: false, message: "The property is not writable because of my custom restriction.", propertyType: { From c6952af23e11672a244f8bc212c28d7be42b32b9 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:15:44 +0100 Subject: [PATCH 02/42] Update extension-manifest.md dashboar -> dashboard --- .../extending-overview/extension-registry/extension-manifest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md b/16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md index 3a5bf0f8093..e733d0b77cb 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md @@ -27,7 +27,7 @@ The required fields of any Extension Manifest are: * `type` — The type defines the purpose of the extension. It is used to determine where the extension will be used. * `alias` — This is a unique identifier for this manifest. Prefix it with something that makes your extension unique. Example: `mfc.Dashboard.Overview` . -* `name` — This is a representational name of this manifest; It does not need to be unique, but this can be beneficial when debugging extensions. Example: `My Fictive Company Overview Dashboar` . +* `name` — This is a representational name of this manifest; It does not need to be unique, but this can be beneficial when debugging extensions. Example: `My Fictive Company Overview Dashboard` . ### Additional Manifest features From d163cccc7424f77bc4d339bb492664c858c23f50 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:16:14 +0100 Subject: [PATCH 03/42] Update README.md enourmes -> enormous --- .../customizing/extending-overview/extension-registry/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/extending-overview/extension-registry/README.md b/16/umbraco-cms/customizing/extending-overview/extension-registry/README.md index 60e5dcab6f7..3baa7e8fc05 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-registry/README.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-registry/README.md @@ -1,7 +1,7 @@ --- description: >- Almost any UI in the Backoffice is an extension. All managed by the Extension - Registry on the Client at Runtime. Giving you enourmes flexibility. + Registry on the Client at Runtime. Giving you enormous flexibility. --- # Extension Registry From 8dee01634d3cc45983c890492a8c71d044733d7e Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:18:37 +0100 Subject: [PATCH 04/42] spelling: availabe -> available --- 10/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 13/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- .../extending-overview/extension-types/sections/README.md | 2 +- .../extending-overview/extension-types/sections/README.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/modelsbuildersettings.md b/10/umbraco-cms/reference/configuration/modelsbuildersettings.md index 938eabb1539..9da2bb8a1db 100644 --- a/10/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/10/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -31,7 +31,7 @@ Let's go through them one by one Specifies how the models builder will generate models and when to generate them. The options are: * `Nothing` - The modelsbuilder will not generate any models, this means that all views will use IPublishedContent, instead of strongly typed models. -* `InMemoryAuto` - Models will automatically be generated each time a content type change occurs, and will then be compiled, and loaded into memory dynamically. This means that the models are only availabe in views, however they will be available instantly. +* `InMemoryAuto` - Models will automatically be generated each time a content type change occurs, and will then be compiled, and loaded into memory dynamically. This means that the models are only available in views, however they will be available instantly. * `SourceCodeManual` - Models will be generated as `.cs` files whenever a user clicks the "Generate models" button on the models builder dashboard - however, the models will not be compiled and loaded into memory dynamically. This means that models are available to edit within the project. The project needs to be recompiled and restarted for the new models, or model changes, to take effect. * `SourceCodeAuto` - This mode behaves the same as `SourceCodeManual` with one difference, the generation of models happens automatically every time a content type change occurs. diff --git a/13/umbraco-cms/reference/configuration/modelsbuildersettings.md b/13/umbraco-cms/reference/configuration/modelsbuildersettings.md index 6de288f2375..009cbd0ab0f 100644 --- a/13/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/13/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -29,7 +29,7 @@ Let's go through them one by one Specifies how the models builder will generate models and when to generate them. The options are: * `Nothing` - The modelsbuilder will not generate any models, this means that all views will use IPublishedContent, instead of strongly typed models. -* `InMemoryAuto` - Models will automatically be generated each time a content type change occurs, and will then be compiled, and loaded into memory dynamically. This means that the models are only availabe in views, however they will be available instantly. +* `InMemoryAuto` - Models will automatically be generated each time a content type change occurs, and will then be compiled, and loaded into memory dynamically. This means that the models are only available in views, however they will be available instantly. * `SourceCodeManual` - Models will be generated as `.cs` files whenever a user clicks the "Generate models" button on the models builder dashboard - however, the models will not be compiled and loaded into memory dynamically. This means that models are available to edit within the project. The project needs to be recompiled and restarted for the new models, or model changes, to take effect. * `SourceCodeAuto` - This mode behaves the same as `SourceCodeManual` with one difference, the generation of models happens automatically every time a content type change occurs. diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md b/15/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md index b3c2aa0ce97..49c73872256 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md @@ -1,6 +1,6 @@ --- description: >- - An overview of the availabe extension types related to sections. + An overview of the available extension types related to sections. --- # Extension Types: Sections diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md b/16/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md index b3c2aa0ce97..49c73872256 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/sections/README.md @@ -1,6 +1,6 @@ --- description: >- - An overview of the availabe extension types related to sections. + An overview of the available extension types related to sections. --- # Extension Types: Sections From 9f9b88fac708f9869233a43a57e71eb297191425 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:20:02 +0100 Subject: [PATCH 05/42] spelling: Worspace -> Workspace --- .../extending-overview/extension-types/workspace-views.md | 4 ++-- .../extension-types/workspaces/workspace-views.md | 4 ++-- .../extension-types/workspaces/workspace-views.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/14/umbraco-cms/customizing/extending-overview/extension-types/workspace-views.md b/14/umbraco-cms/customizing/extending-overview/extension-types/workspace-views.md index 6c83bcedff3..ff91020dfb2 100644 --- a/14/umbraco-cms/customizing/extending-overview/extension-types/workspace-views.md +++ b/14/umbraco-cms/customizing/extending-overview/extension-types/workspace-views.md @@ -65,7 +65,7 @@ import { LitElement, html, customElement, css } from "@umbraco-cms/backoffice/ex import { UmbElementMixin } from "@umbraco-cms/backoffice/element-api"; @customElement('my-workspaceview') -export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { +export default class MyWorkspaceViewElement extends UmbElementMixin(LitElement) { render() { return html` @@ -84,7 +84,7 @@ export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { declare global { interface HTMLElementTagNameMap { - 'my-workspaceview': MyWorspaceViewElement + 'my-workspaceview': MyWorkspaceViewElement } } diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md b/15/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md index 7f46a46edf0..9c21aacd57c 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md @@ -65,7 +65,7 @@ import { LitElement, html, customElement, css } from "@umbraco-cms/backoffice/ex import { UmbElementMixin } from "@umbraco-cms/backoffice/element-api"; @customElement('my-workspaceview') -export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { +export default class MyWorkspaceViewElement extends UmbElementMixin(LitElement) { render() { return html` @@ -84,7 +84,7 @@ export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { declare global { interface HTMLElementTagNameMap { - 'my-workspaceview': MyWorspaceViewElement + 'my-workspaceview': MyWorkspaceViewElement } } diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md b/16/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md index 7f46a46edf0..9c21aacd57c 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/workspaces/workspace-views.md @@ -65,7 +65,7 @@ import { LitElement, html, customElement, css } from "@umbraco-cms/backoffice/ex import { UmbElementMixin } from "@umbraco-cms/backoffice/element-api"; @customElement('my-workspaceview') -export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { +export default class MyWorkspaceViewElement extends UmbElementMixin(LitElement) { render() { return html` @@ -84,7 +84,7 @@ export default class MyWorspaceViewElement extends UmbElementMixin(LitElement) { declare global { interface HTMLElementTagNameMap { - 'my-workspaceview': MyWorspaceViewElement + 'my-workspaceview': MyWorkspaceViewElement } } From 9c7cd7d4767698a77e9417cdd5d8673da2d841ea Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:23:21 +0100 Subject: [PATCH 06/42] spelling: instanciated -> instantiated --- .../extending-overview/extension-types/entity-actions.md | 2 +- .../extending-overview/extension-types/entity-actions.md | 2 +- .../extending-overview/extension-types/entity-actions.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/14/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/14/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md index b91de56a43c..2554b0a6cac 100644 --- a/14/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md +++ b/14/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md @@ -79,7 +79,7 @@ interface UmbEntityActionElement {} ### The Entity Action Class -As part of the Extension Manifest you can attach a class that will be instanciated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. +As part of the Extension Manifest you can attach a class that will be instantiated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. The class either provides a getHref method, or an execute method. If the getHref method is provided, the action will use the link. Otherwise the `execute` method will be used. When the action is clicked the `execute` method on the api class will be run. When the action is completed, an event on the host element will be dispatched to notify any surrounding elements. diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md index b91de56a43c..2554b0a6cac 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md @@ -79,7 +79,7 @@ interface UmbEntityActionElement {} ### The Entity Action Class -As part of the Extension Manifest you can attach a class that will be instanciated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. +As part of the Extension Manifest you can attach a class that will be instantiated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. The class either provides a getHref method, or an execute method. If the getHref method is provided, the action will use the link. Otherwise the `execute` method will be used. When the action is clicked the `execute` method on the api class will be run. When the action is completed, an event on the host element will be dispatched to notify any surrounding elements. diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md b/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md index b91de56a43c..2554b0a6cac 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/entity-actions.md @@ -79,7 +79,7 @@ interface UmbEntityActionElement {} ### The Entity Action Class -As part of the Extension Manifest you can attach a class that will be instanciated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. +As part of the Extension Manifest you can attach a class that will be instantiated as part of the action. It will have access to the host element, a repository with the given alias and the unique (key etc) of the entity. The class either provides a getHref method, or an execute method. If the getHref method is provided, the action will use the link. Otherwise the `execute` method will be used. When the action is clicked the `execute` method on the api class will be run. When the action is completed, an event on the host element will be dispatched to notify any surrounding elements. From 573bd27cdb2a897f8ad69b1047e15839b1156b42 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:24:55 +0100 Subject: [PATCH 07/42] metdata -> metadata --- .../extending-overview/extension-types/header-apps.md | 2 +- .../extending-overview/extension-types/header-apps.md | 2 +- .../extending-overview/extension-types/header-apps.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/14/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md b/14/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md index 1faa14da7f3..e8f57621345 100644 --- a/14/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md +++ b/14/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md @@ -51,7 +51,7 @@ Below you can find an example of how to setup a Header App using the manifest fi * First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI. * Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button. -* The button requires some metdata: an icon, label of the button (name of the button) and a link which opens once clicked. +* The button requires some : an icon, label of the button (name of the button) and a link which opens once clicked. 4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**: diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md b/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md index cffe04a2632..7c8b4f94ab8 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md @@ -51,7 +51,7 @@ Below you can find an example of how to setup a Header App using the manifest fi * First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI. * Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button. -* The button requires some metdata: an icon, label of the button (name of the button) and a link which opens once clicked. +* The button requires some : an icon, label of the button (name of the button) and a link which opens once clicked. 4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**: diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md b/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md index cffe04a2632..7c8b4f94ab8 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md @@ -51,7 +51,7 @@ Below you can find an example of how to setup a Header App using the manifest fi * First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI. * Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button. -* The button requires some metdata: an icon, label of the button (name of the button) and a link which opens once clicked. +* The button requires some : an icon, label of the button (name of the button) and a link which opens once clicked. 4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**: From 765fd0181d3350d997745fb212b60a070cfc800e Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:25:13 +0100 Subject: [PATCH 08/42] spelling: prupose -> purpose --- .../customizing/extending-overview/extension-types/README.md | 2 +- .../customizing/extending-overview/extension-types/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md index f28761f0b51..358ea1ccbef 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -12,7 +12,7 @@ The general features of all Extension Types can be read as part of the [Extensio ### General Extension Type -The system provides Extension Types for certain needs and then there is a few that has a general prupose. +The system provides Extension Types for certain needs and then there is a few that has a general purpose. ### [Bundle](bundle.md) diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md index f28761f0b51..358ea1ccbef 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -12,7 +12,7 @@ The general features of all Extension Types can be read as part of the [Extensio ### General Extension Type -The system provides Extension Types for certain needs and then there is a few that has a general prupose. +The system provides Extension Types for certain needs and then there is a few that has a general purpose. ### [Bundle](bundle.md) From a905a79d02138f4493f641755b6d4f4056571c14 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:25:47 +0100 Subject: [PATCH 09/42] spelling: ammending -> amending --- .../customizing/extending-overview/extension-types/README.md | 2 +- .../customizing/extending-overview/extension-types/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md index 358ea1ccbef..df3ab138713 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -28,4 +28,4 @@ Most Extension Types support conditions. Defining conditions enables you to cont ### [Kinds](kind.md) -The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be ammending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. +The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md index 358ea1ccbef..df3ab138713 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -28,4 +28,4 @@ Most Extension Types support conditions. Defining conditions enables you to cont ### [Kinds](kind.md) -The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be ammending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. +The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. From 4287ab3fd956edf8c68a13dd06067139dd661f81 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:26:11 +0100 Subject: [PATCH 10/42] spelling: posible -> possible --- .../customizing/extending-overview/extension-types/README.md | 2 +- .../customizing/extending-overview/extension-types/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md index df3ab138713..58d4360855a 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -28,4 +28,4 @@ Most Extension Types support conditions. Defining conditions enables you to cont ### [Kinds](kind.md) -The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. +The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it possible for you to only configure the Element via properties of the Manifest. diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md index df3ab138713..58d4360855a 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/README.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/README.md @@ -28,4 +28,4 @@ Most Extension Types support conditions. Defining conditions enables you to cont ### [Kinds](kind.md) -The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it posible for you to only configure the Element via properties of the Manifest. +The Kind-type enables you to base your Extension registration on a preset manifest. A kind provides the base manifest that your manifest will be amending. A typical Kind declaration would provide a default Element, making it possible for you to only configure the Element via properties of the Manifest. From 17bc94ed8079bd91b1bd9e07f20625355b1f968b Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:27:06 +0100 Subject: [PATCH 11/42] spelling: disassambles -> disassembles --- .../customizing/foundation/context-api/consume-a-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/foundation/context-api/consume-a-context.md b/16/umbraco-cms/customizing/foundation/context-api/consume-a-context.md index 6e21321d542..aa981dfacc2 100644 --- a/16/umbraco-cms/customizing/foundation/context-api/consume-a-context.md +++ b/16/umbraco-cms/customizing/foundation/context-api/consume-a-context.md @@ -22,7 +22,7 @@ this.consumeContext(UMB_NOTIFICATION_CONTEXT, (context) => { if (context) { console.log("I've got the Notification Context: ", context); } else { - console.log("The Notification Context is gone, I will make sure my code disassamples properly.") + console.log("The Notification Context is gone, I will make sure my code disassembles properly.") } }); ``` From 07b0fb3e08b688a3ff58931d0b6d7930a532a87d Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:28:22 +0100 Subject: [PATCH 12/42] spellling: clearInternval -> clearInterval --- .../customizing/foundation/umbraco-controller/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md b/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md index 910e8cd3487..1790386be71 100644 --- a/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md +++ b/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md @@ -51,7 +51,7 @@ import type { UmbControllerHost } from '@umbraco-cms/backoffice/controller-api'; hostDisconnected() { // It's important to call the super method when overriding a method of the base class. super.hostDisconnected(); - clearInternval(this.#timer); + clearInterval(this.#timer); } #onInterval = () => { From 1bc88eb94ffa1f6d4767734465bfb7db36555e02 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:28:55 +0100 Subject: [PATCH 13/42] spelling: unregistration -> deregistration --- .../customizing/foundation/umbraco-controller/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md b/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md index 1790386be71..9d06e2753d2 100644 --- a/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md +++ b/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md @@ -67,7 +67,7 @@ import type { UmbControllerHost } from '@umbraco-cms/backoffice/controller-api'; } -If you don't like to extend the `UmbControllerBase`, then you can register a class as a controller as shown in the following example. Note that manual unregistration is required in this case. +If you don't like to extend the `UmbControllerBase`, then you can register a class as a controller as shown in the following example. Note that manual deregistration is required in this case. ``` export class MyOwnControllerImplementation { From 3d22e0a4b0c5ee749f7ff50cde847bc757010e92 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:30:17 +0100 Subject: [PATCH 14/42] spelling: UmbElemenMixin -> UmbElementMixin --- 14/umbraco-cms/customizing/foundation/terminology.md | 2 +- 15/umbraco-cms/customizing/foundation/terminology.md | 2 +- 16/umbraco-cms/customizing/foundation/terminology.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/14/umbraco-cms/customizing/foundation/terminology.md b/14/umbraco-cms/customizing/foundation/terminology.md index 9651ea3064f..4a0453d9f50 100644 --- a/14/umbraco-cms/customizing/foundation/terminology.md +++ b/14/umbraco-cms/customizing/foundation/terminology.md @@ -18,6 +18,6 @@ Understanding certain key concepts is essential when customizing the backoffice. * **Umbraco Controller:** Enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Controllers](../../customizing/foundation/umbraco-element/controllers/) article. * **Controller Host:** A class that can host controllers. * **Controller Host Element:** The element that can host controllers. -* **Umbraco Element:** The `UmbLitElement` or `UmbElemenMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](../../customizing/foundation/umbraco-element/) article. +* **Umbraco Element:** The `UmbLitElement` or `UmbElementMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](../../customizing/foundation/umbraco-element/) article. Read more about how to get started with extending the backoffice in the [Backoffice Setup](../../customizing/extending-overview/) article. diff --git a/15/umbraco-cms/customizing/foundation/terminology.md b/15/umbraco-cms/customizing/foundation/terminology.md index 9651ea3064f..4a0453d9f50 100644 --- a/15/umbraco-cms/customizing/foundation/terminology.md +++ b/15/umbraco-cms/customizing/foundation/terminology.md @@ -18,6 +18,6 @@ Understanding certain key concepts is essential when customizing the backoffice. * **Umbraco Controller:** Enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Controllers](../../customizing/foundation/umbraco-element/controllers/) article. * **Controller Host:** A class that can host controllers. * **Controller Host Element:** The element that can host controllers. -* **Umbraco Element:** The `UmbLitElement` or `UmbElemenMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](../../customizing/foundation/umbraco-element/) article. +* **Umbraco Element:** The `UmbLitElement` or `UmbElementMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](../../customizing/foundation/umbraco-element/) article. Read more about how to get started with extending the backoffice in the [Backoffice Setup](../../customizing/extending-overview/) article. diff --git a/16/umbraco-cms/customizing/foundation/terminology.md b/16/umbraco-cms/customizing/foundation/terminology.md index 2a43838a3c7..fa80eaf2626 100644 --- a/16/umbraco-cms/customizing/foundation/terminology.md +++ b/16/umbraco-cms/customizing/foundation/terminology.md @@ -17,6 +17,6 @@ Understanding certain key concepts is essential when customizing the backoffice. * **Umbraco Controller:** Enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Controllers](umbraco-controller/) article. * **Controller Host:** A class that can host controllers. * **Controller Host Element:** The element that can host controllers. -* **Umbraco Element:** The `UmbLitElement` or `UmbElemenMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](umbraco-element/) article. +* **Umbraco Element:** The `UmbLitElement` or `UmbElementMixin` enables hosting controllers. Additionally, it provides a few shortcut methods for initializing core Umbraco Controllers. You can read more about this in the [Umbraco Element](umbraco-element/) article. Read more about how to get started with extending the backoffice in the [Backoffice Setup](../extending-overview/) article. From df2b1e167f5af2f82cdfecb9645b11d9761327ff Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:31:26 +0100 Subject: [PATCH 15/42] spelling: functionaility -> functionality --- 10/umbraco-cms/extending/property-editors/README.md | 2 +- 13/umbraco-cms/extending/property-editors/README.md | 2 +- 14/umbraco-cms/customizing/property-editors/README.md | 2 +- 15/umbraco-cms/customizing/property-editors/README.md | 2 +- 16/umbraco-cms/customizing/property-editors/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/extending/property-editors/README.md b/10/umbraco-cms/extending/property-editors/README.md index 130e064a753..460cc75a115 100644 --- a/10/umbraco-cms/extending/property-editors/README.md +++ b/10/umbraco-cms/extending/property-editors/README.md @@ -23,7 +23,7 @@ Convert the stored property data value to a useful object returned by the Publis ## [Property Actions](property-actions.md) -Use Property Actions to add additional functionaility to your custom property editors. +Use Property Actions to add additional functionality to your custom property editors. ## [Tracking References](tracking.md) diff --git a/13/umbraco-cms/extending/property-editors/README.md b/13/umbraco-cms/extending/property-editors/README.md index 930a1cdfff2..4b732fbdd6a 100644 --- a/13/umbraco-cms/extending/property-editors/README.md +++ b/13/umbraco-cms/extending/property-editors/README.md @@ -23,7 +23,7 @@ Convert the stored property data value to a useful object returned by the Publis ## [Property Actions](property-actions.md) -Use Property Actions to add additional functionaility to your custom property editors. +Use Property Actions to add additional functionality to your custom property editors. ## [Tracking References](tracking.md) diff --git a/14/umbraco-cms/customizing/property-editors/README.md b/14/umbraco-cms/customizing/property-editors/README.md index b38eab37472..44205dfdab1 100644 --- a/14/umbraco-cms/customizing/property-editors/README.md +++ b/14/umbraco-cms/customizing/property-editors/README.md @@ -28,7 +28,7 @@ Convert the stored property data value to a useful object returned by the Publis ## [Property Actions](property-actions.md) -Use Property Actions to add additional functionaility to your custom property editors. +Use Property Actions to add additional functionality to your custom property editors. ## [Tracking References](broken-reference) diff --git a/15/umbraco-cms/customizing/property-editors/README.md b/15/umbraco-cms/customizing/property-editors/README.md index 03463d2d372..9b99b738b0f 100644 --- a/15/umbraco-cms/customizing/property-editors/README.md +++ b/15/umbraco-cms/customizing/property-editors/README.md @@ -28,7 +28,7 @@ Convert the stored property data value to a useful object returned by the Publis ## [Property Actions](property-actions.md) -Use Property Actions to add additional functionaility to your custom property editors. +Use Property Actions to add additional functionality to your custom property editors. ## [Tracking References](tracking.md) diff --git a/16/umbraco-cms/customizing/property-editors/README.md b/16/umbraco-cms/customizing/property-editors/README.md index 03463d2d372..9b99b738b0f 100644 --- a/16/umbraco-cms/customizing/property-editors/README.md +++ b/16/umbraco-cms/customizing/property-editors/README.md @@ -28,7 +28,7 @@ Convert the stored property data value to a useful object returned by the Publis ## [Property Actions](property-actions.md) -Use Property Actions to add additional functionaility to your custom property editors. +Use Property Actions to add additional functionality to your custom property editors. ## [Tracking References](tracking.md) From 38bf1c8ad8029c4f2e05bf3119c2bf36fc6655b6 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:32:57 +0100 Subject: [PATCH 16/42] spelling: YourFileSystemImplementaion -> YourFileSystemImplementation --- 10/umbraco-cms/extending/filesystemproviders/README.md | 2 +- 13/umbraco-cms/extending/filesystemproviders/README.md | 2 +- 14/umbraco-cms/extending/filesystemproviders/README.md | 2 +- 15/umbraco-cms/extending/filesystemproviders/README.md | 2 +- 16/umbraco-cms/extending/filesystemproviders/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/extending/filesystemproviders/README.md b/10/umbraco-cms/extending/filesystemproviders/README.md index cf5613c9854..e1caa4a2d54 100644 --- a/10/umbraco-cms/extending/filesystemproviders/README.md +++ b/10/umbraco-cms/extending/filesystemproviders/README.md @@ -215,7 +215,7 @@ namespace UmbracoExamples.Composition var path = settings.UmbracoCssPath; var rootPath = hostingEnvironment.MapPathWebRoot(path); var rootUrl = hostingEnvironment.ToAbsolute(path); - var fileSystem = new YourFileSystemImplementaion(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); + var fileSystem = new YourFileSystemImplementation(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); systems.SetStylesheetFilesystem(fileSystem); }); diff --git a/13/umbraco-cms/extending/filesystemproviders/README.md b/13/umbraco-cms/extending/filesystemproviders/README.md index 6168a7bbd31..9d91943401a 100644 --- a/13/umbraco-cms/extending/filesystemproviders/README.md +++ b/13/umbraco-cms/extending/filesystemproviders/README.md @@ -214,7 +214,7 @@ public class FileSystemComposer : IComposer var path = settings.UmbracoCssPath; var rootPath = hostingEnvironment.MapPathWebRoot(path); var rootUrl = hostingEnvironment.ToAbsolute(path); - var fileSystem = new YourFileSystemImplementaion(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); + var fileSystem = new YourFileSystemImplementation(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); systems.SetStylesheetFilesystem(fileSystem); }); diff --git a/14/umbraco-cms/extending/filesystemproviders/README.md b/14/umbraco-cms/extending/filesystemproviders/README.md index 18b491480c0..d5dd2789fef 100644 --- a/14/umbraco-cms/extending/filesystemproviders/README.md +++ b/14/umbraco-cms/extending/filesystemproviders/README.md @@ -200,7 +200,7 @@ public class FileSystemComposer : IComposer var path = settings.UmbracoCssPath; var rootPath = hostingEnvironment.MapPathWebRoot(path); var rootUrl = hostingEnvironment.ToAbsolute(path); - var fileSystem = new YourFileSystemImplementaion(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); + var fileSystem = new YourFileSystemImplementation(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); systems.SetStylesheetFilesystem(fileSystem); }); diff --git a/15/umbraco-cms/extending/filesystemproviders/README.md b/15/umbraco-cms/extending/filesystemproviders/README.md index 18b491480c0..d5dd2789fef 100644 --- a/15/umbraco-cms/extending/filesystemproviders/README.md +++ b/15/umbraco-cms/extending/filesystemproviders/README.md @@ -200,7 +200,7 @@ public class FileSystemComposer : IComposer var path = settings.UmbracoCssPath; var rootPath = hostingEnvironment.MapPathWebRoot(path); var rootUrl = hostingEnvironment.ToAbsolute(path); - var fileSystem = new YourFileSystemImplementaion(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); + var fileSystem = new YourFileSystemImplementation(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); systems.SetStylesheetFilesystem(fileSystem); }); diff --git a/16/umbraco-cms/extending/filesystemproviders/README.md b/16/umbraco-cms/extending/filesystemproviders/README.md index 6729158859a..de857d05cef 100644 --- a/16/umbraco-cms/extending/filesystemproviders/README.md +++ b/16/umbraco-cms/extending/filesystemproviders/README.md @@ -206,7 +206,7 @@ public class FileSystemComposer : IComposer var path = settings.UmbracoCssPath; var rootPath = hostingEnvironment.MapPathWebRoot(path); var rootUrl = hostingEnvironment.ToAbsolute(path); - var fileSystem = new YourFileSystemImplementaion(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); + var fileSystem = new YourFileSystemImplementation(ioHelper, hostingEnvironment, logger, rootPath, rootUrl); systems.SetStylesheetFilesystem(fileSystem); }); From 45524413df7e02f531803561c9aea1d96326a51f Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:34:26 +0100 Subject: [PATCH 17/42] spelling: Tranfer -> Transfer --- 10/umbraco-cms/extending/health-check/README.md | 2 +- 13/umbraco-cms/extending/health-check/README.md | 4 ++-- 14/umbraco-cms/extending/health-check/README.md | 4 ++-- 15/umbraco-cms/extending/health-check/README.md | 4 ++-- 16/umbraco-cms/extending/health-check/README.md | 4 ++-- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/10/umbraco-cms/extending/health-check/README.md b/10/umbraco-cms/extending/health-check/README.md index 496349aa031..138cafaacca 100644 --- a/10/umbraco-cms/extending/health-check/README.md +++ b/10/umbraco-cms/extending/health-check/README.md @@ -37,7 +37,7 @@ Umbraco comes with the following checks by default: * **HTTPS Configuration (id: `EB66BB3B-1BCD-4314-9531-9DA2C1D6D9A7`)** - to determine if the current site is running on a secure connection * **UseHttps check** - when the site is running on HTTPS, `Umbraco.Cms.Core.Configuration.Models.GlobalSettings.UseHttps` needs to be enabled to secure the backoffice. The setting can be found under `Umbraco:CMS:Global` in the `appsettings.json` file * Category **Services** - * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Tranfer Protocol (SMTP) server is configured and is accepting requests for sending emails + * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Transfer Protocol (SMTP) server is configured and is accepting requests for sending emails Each check returns a message indicating whether or not the issue in question has been found on the website installation. This could be an error that should be fixed, or a warning you should be aware of. diff --git a/13/umbraco-cms/extending/health-check/README.md b/13/umbraco-cms/extending/health-check/README.md index e59345e5456..e961e261910 100644 --- a/13/umbraco-cms/extending/health-check/README.md +++ b/13/umbraco-cms/extending/health-check/README.md @@ -31,7 +31,7 @@ Umbraco comes with the following checks by default: * **HTTPS Configuration (id: `EB66BB3B-1BCD-4314-9531-9DA2C1D6D9A7`)** - to determine if the current site is running on a secure connection * **UseHttps check** - when the site is running on HTTPS, `Umbraco.Cms.Core.Configuration.Models.GlobalSettings.UseHttps` needs to be enabled to secure the backoffice. The setting can be found under `Umbraco:CMS:Global` in the `appsettings.json` file * Category **Services** - * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Tranfer Protocol (SMTP) server is configured and is accepting requests for sending emails + * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Transfer Protocol (SMTP) server is configured and is accepting requests for sending emails Each check returns a message indicating whether or not the issue in question has been found on the website installation. This could be an error that should be fixed, or a warning you should be aware of. @@ -405,4 +405,4 @@ If a custom configuration is required for a custom notification method, the foll } ``` -If you want to get the notifications by email, Simple Mail Tranfer Protocol (SMTP) settings should also be configured in the same JSON file. +If you want to get the notifications by email, Simple Mail Transfer Protocol (SMTP) settings should also be configured in the same JSON file. diff --git a/14/umbraco-cms/extending/health-check/README.md b/14/umbraco-cms/extending/health-check/README.md index 366d89f3f90..75f784091d4 100644 --- a/14/umbraco-cms/extending/health-check/README.md +++ b/14/umbraco-cms/extending/health-check/README.md @@ -31,7 +31,7 @@ Umbraco comes with the following checks by default: * **HTTPS Configuration (id: `EB66BB3B-1BCD-4314-9531-9DA2C1D6D9A7`)** - to determine if the current site is running on a secure connection * **UseHttps check** - when the site is running on HTTPS, `Umbraco.Cms.Core.Configuration.Models.GlobalSettings.UseHttps` needs to be enabled to secure the backoffice. The setting can be found under `Umbraco:CMS:Global` in the `appsettings.json` file * Category **Services** - * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Tranfer Protocol (SMTP) server is configured and is accepting requests for sending emails + * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Transfer Protocol (SMTP) server is configured and is accepting requests for sending emails Each check returns a message indicating whether or not the issue in question has been found on the website installation. This could be an error that should be fixed, or a warning you should be aware of. @@ -311,4 +311,4 @@ If a custom configuration is required for a custom notification method, the foll } ``` -If you want to get the notifications by email, Simple Mail Tranfer Protocol (SMTP) settings should also be configured in the same JSON file. +If you want to get the notifications by email, Simple Mail Transfer Protocol (SMTP) settings should also be configured in the same JSON file. diff --git a/15/umbraco-cms/extending/health-check/README.md b/15/umbraco-cms/extending/health-check/README.md index 366d89f3f90..75f784091d4 100644 --- a/15/umbraco-cms/extending/health-check/README.md +++ b/15/umbraco-cms/extending/health-check/README.md @@ -31,7 +31,7 @@ Umbraco comes with the following checks by default: * **HTTPS Configuration (id: `EB66BB3B-1BCD-4314-9531-9DA2C1D6D9A7`)** - to determine if the current site is running on a secure connection * **UseHttps check** - when the site is running on HTTPS, `Umbraco.Cms.Core.Configuration.Models.GlobalSettings.UseHttps` needs to be enabled to secure the backoffice. The setting can be found under `Umbraco:CMS:Global` in the `appsettings.json` file * Category **Services** - * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Tranfer Protocol (SMTP) server is configured and is accepting requests for sending emails + * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Transfer Protocol (SMTP) server is configured and is accepting requests for sending emails Each check returns a message indicating whether or not the issue in question has been found on the website installation. This could be an error that should be fixed, or a warning you should be aware of. @@ -311,4 +311,4 @@ If a custom configuration is required for a custom notification method, the foll } ``` -If you want to get the notifications by email, Simple Mail Tranfer Protocol (SMTP) settings should also be configured in the same JSON file. +If you want to get the notifications by email, Simple Mail Transfer Protocol (SMTP) settings should also be configured in the same JSON file. diff --git a/16/umbraco-cms/extending/health-check/README.md b/16/umbraco-cms/extending/health-check/README.md index 366d89f3f90..75f784091d4 100644 --- a/16/umbraco-cms/extending/health-check/README.md +++ b/16/umbraco-cms/extending/health-check/README.md @@ -31,7 +31,7 @@ Umbraco comes with the following checks by default: * **HTTPS Configuration (id: `EB66BB3B-1BCD-4314-9531-9DA2C1D6D9A7`)** - to determine if the current site is running on a secure connection * **UseHttps check** - when the site is running on HTTPS, `Umbraco.Cms.Core.Configuration.Models.GlobalSettings.UseHttps` needs to be enabled to secure the backoffice. The setting can be found under `Umbraco:CMS:Global` in the `appsettings.json` file * Category **Services** - * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Tranfer Protocol (SMTP) server is configured and is accepting requests for sending emails + * **SMTP Settings (id: `1B5D221B-CE99-4193-97CB-5F3261EC73DF`)** - checks that an Simple Mail Transfer Protocol (SMTP) server is configured and is accepting requests for sending emails Each check returns a message indicating whether or not the issue in question has been found on the website installation. This could be an error that should be fixed, or a warning you should be aware of. @@ -311,4 +311,4 @@ If a custom configuration is required for a custom notification method, the foll } ``` -If you want to get the notifications by email, Simple Mail Tranfer Protocol (SMTP) settings should also be configured in the same JSON file. +If you want to get the notifications by email, Simple Mail Transfer Protocol (SMTP) settings should also be configured in the same JSON file. From 49921f3e16506f29f7f3c5e500cc66f1ccb8d0ab Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:37:33 +0100 Subject: [PATCH 18/42] spelling: Licences -> Licenses --- 10/umbraco-cms/extending/packages/good-practice-and-defaults.md | 2 +- 13/umbraco-cms/extending/packages/good-practice-and-defaults.md | 2 +- 14/umbraco-cms/extending/packages/good-practice-and-defaults.md | 2 +- 15/umbraco-cms/extending/packages/good-practice-and-defaults.md | 2 +- 16/umbraco-cms/extending/packages/good-practice-and-defaults.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/extending/packages/good-practice-and-defaults.md b/10/umbraco-cms/extending/packages/good-practice-and-defaults.md index b7fb3071337..102fb9d91ec 100644 --- a/10/umbraco-cms/extending/packages/good-practice-and-defaults.md +++ b/10/umbraco-cms/extending/packages/good-practice-and-defaults.md @@ -32,7 +32,7 @@ When you have a package that contains many views you might consider building a d ## License files -Umbraco products store their licenses in `/umbraco/Licences`. It is recommended for third-party packages that require license files to also store their license files in this location. +Umbraco products store their licenses in `/umbraco/Licenses`. It is recommended for third-party packages that require license files to also store their license files in this location. The default `.gitignore` for Umbraco templates will include any files in the `/Licenses` folder while ignoring most of the rest of the Umbraco folder. diff --git a/13/umbraco-cms/extending/packages/good-practice-and-defaults.md b/13/umbraco-cms/extending/packages/good-practice-and-defaults.md index 3ebb057e785..8c04a6e2c21 100644 --- a/13/umbraco-cms/extending/packages/good-practice-and-defaults.md +++ b/13/umbraco-cms/extending/packages/good-practice-and-defaults.md @@ -32,7 +32,7 @@ When you have a package that contains many views you might consider building a d ## License files -Umbraco products store their licenses in `/umbraco/Licences`. It is recommended for third-party packages that require license files to also store their license files in this location. +Umbraco products store their licenses in `/umbraco/Licenses`. It is recommended for third-party packages that require license files to also store their license files in this location. The default `.gitignore` for Umbraco templates will include any files in the `/Licenses` folder while ignoring most of the rest of the Umbraco folder. diff --git a/14/umbraco-cms/extending/packages/good-practice-and-defaults.md b/14/umbraco-cms/extending/packages/good-practice-and-defaults.md index 6df4d526d69..2046a8e15bf 100644 --- a/14/umbraco-cms/extending/packages/good-practice-and-defaults.md +++ b/14/umbraco-cms/extending/packages/good-practice-and-defaults.md @@ -36,7 +36,7 @@ When you have a package that contains many views you might consider building a d ## License files -Umbraco products store their licenses in `/umbraco/Licences`. It is recommended for third-party packages that require license files to also store their license files in this location. +Umbraco products store their licenses in `/umbraco/Licenses`. It is recommended for third-party packages that require license files to also store their license files in this location. The default `.gitignore` for Umbraco templates will include any files in the `/Licenses` folder while ignoring most of the rest of the Umbraco folder. diff --git a/15/umbraco-cms/extending/packages/good-practice-and-defaults.md b/15/umbraco-cms/extending/packages/good-practice-and-defaults.md index d692b3ca0a1..9c34c2f7a83 100644 --- a/15/umbraco-cms/extending/packages/good-practice-and-defaults.md +++ b/15/umbraco-cms/extending/packages/good-practice-and-defaults.md @@ -36,7 +36,7 @@ When you have a package that contains many views you might consider building a d ## License files -Umbraco products store their licenses in `/umbraco/Licences`. It is recommended for third-party packages that require license files to also store their license files in this location. +Umbraco products store their licenses in `/umbraco/Licenses`. It is recommended for third-party packages that require license files to also store their license files in this location. The default `.gitignore` for Umbraco templates will include any files in the `/Licenses` folder while ignoring most of the rest of the Umbraco folder. diff --git a/16/umbraco-cms/extending/packages/good-practice-and-defaults.md b/16/umbraco-cms/extending/packages/good-practice-and-defaults.md index d692b3ca0a1..9c34c2f7a83 100644 --- a/16/umbraco-cms/extending/packages/good-practice-and-defaults.md +++ b/16/umbraco-cms/extending/packages/good-practice-and-defaults.md @@ -36,7 +36,7 @@ When you have a package that contains many views you might consider building a d ## License files -Umbraco products store their licenses in `/umbraco/Licences`. It is recommended for third-party packages that require license files to also store their license files in this location. +Umbraco products store their licenses in `/umbraco/Licenses`. It is recommended for third-party packages that require license files to also store their license files in this location. The default `.gitignore` for Umbraco templates will include any files in the `/Licenses` folder while ignoring most of the rest of the Umbraco folder. From a89a5b3b1d48d6872758c0878a4c5553248633c1 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:40:19 +0100 Subject: [PATCH 19/42] spelling: obselete -> obsolete --- .../reference/management/using-services/localizationservice.md | 2 +- .../reference/routing/request-pipeline/outbound-pipeline.md | 2 +- 15/umbraco-cms/extending/backoffice-search.md | 2 +- .../reference/management/using-services/localizationservice.md | 2 +- .../reference/routing/request-pipeline/outbound-pipeline.md | 2 +- 16/umbraco-cms/extending/backoffice-search.md | 2 +- .../reference/management/using-services/localizationservice.md | 2 +- .../reference/routing/request-pipeline/outbound-pipeline.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/14/umbraco-cms/reference/management/using-services/localizationservice.md b/14/umbraco-cms/reference/management/using-services/localizationservice.md index 0f80835ec77..a922238f976 100644 --- a/14/umbraco-cms/reference/management/using-services/localizationservice.md +++ b/14/umbraco-cms/reference/management/using-services/localizationservice.md @@ -94,5 +94,5 @@ Below you can see a full example of the examples shown above - including the nec ``` {% hint style="warning" %} -The above example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The above example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} diff --git a/14/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md b/14/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md index cb177bee8bc..8acea11f095 100644 --- a/14/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md +++ b/14/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md @@ -219,7 +219,7 @@ If there is only a small change to the logic around Url generation, then a smart Add /fish on the end of every URL. It's important to note here that since we're changing the outbound URL, but not how we handle URLs inbound, this **will** break the routing. In order to make the routing work again you have to implement a custom content finder, see [IContentFinder](icontentfinder.md) for more information on how to do that. {% hint style="warning" %} -The below example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The below example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} ```csharp diff --git a/15/umbraco-cms/extending/backoffice-search.md b/15/umbraco-cms/extending/backoffice-search.md index ff396b6f9e5..885e47d8cde 100644 --- a/15/umbraco-cms/extending/backoffice-search.md +++ b/15/umbraco-cms/extending/backoffice-search.md @@ -51,7 +51,7 @@ public class BackofficeSearchComposer : IComposer ``` {% hint style="warning" %} -The below example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` instead. +The below example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` instead. {% endhint %} ```csharp diff --git a/15/umbraco-cms/reference/management/using-services/localizationservice.md b/15/umbraco-cms/reference/management/using-services/localizationservice.md index 0440a602b45..e4cf4a3a46c 100644 --- a/15/umbraco-cms/reference/management/using-services/localizationservice.md +++ b/15/umbraco-cms/reference/management/using-services/localizationservice.md @@ -94,5 +94,5 @@ Below you can see a full example of the examples shown above - including the nec ``` {% hint style="warning" %} -The above example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The above example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} 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 563a89208db..de18159a7b4 100644 --- a/15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md +++ b/15/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md @@ -226,7 +226,7 @@ If there is only a small change to the logic around Url generation, then a smart Add /fish on the end of every URL. It's important to note here that since we're changing the outbound URL, but not how we handle URLs inbound, this **will** break the routing. In order to make the routing work again you have to implement a custom content finder, see [IContentFinder](icontentfinder.md) for more information on how to do that. {% hint style="warning" %} -The below example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The below example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} ```csharp diff --git a/16/umbraco-cms/extending/backoffice-search.md b/16/umbraco-cms/extending/backoffice-search.md index ff396b6f9e5..885e47d8cde 100644 --- a/16/umbraco-cms/extending/backoffice-search.md +++ b/16/umbraco-cms/extending/backoffice-search.md @@ -51,7 +51,7 @@ public class BackofficeSearchComposer : IComposer ``` {% hint style="warning" %} -The below example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` instead. +The below example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` instead. {% endhint %} ```csharp diff --git a/16/umbraco-cms/reference/management/using-services/localizationservice.md b/16/umbraco-cms/reference/management/using-services/localizationservice.md index 0440a602b45..e4cf4a3a46c 100644 --- a/16/umbraco-cms/reference/management/using-services/localizationservice.md +++ b/16/umbraco-cms/reference/management/using-services/localizationservice.md @@ -94,5 +94,5 @@ Below you can see a full example of the examples shown above - including the nec ``` {% hint style="warning" %} -The above example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The above example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} 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 ee6d8d8a1e9..6c05f2166e5 100644 --- a/16/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md +++ b/16/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md @@ -219,7 +219,7 @@ If there is only a small change to the logic around Url generation, then a smart Add /fish on the end of every URL. It's important to note here that since we're changing the outbound URL, but not how we handle URLs inbound, this **will** break the routing. In order to make the routing work again you have to implement a custom content finder, see [IContentFinder](icontentfinder.md) for more information on how to do that. {% hint style="warning" %} -The below example is using `ILocalizationService` which is currently obselete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. +The below example is using `ILocalizationService` which is currently obsolete and will be removed in v15. Use `ILanguageService` or `IDictionaryItemService` (for dictionary item operations) instead. {% endhint %} ```csharp From e61bfa6d292e3390c92ece0f31a93c939b420790 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:43:21 +0100 Subject: [PATCH 20/42] spelling: individial -> individual --- 14/umbraco-cms/fundamentals/backoffice/variants.md | 2 +- 15/umbraco-cms/fundamentals/backoffice/variants.md | 2 +- 16/umbraco-cms/fundamentals/backoffice/variants.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/14/umbraco-cms/fundamentals/backoffice/variants.md b/14/umbraco-cms/fundamentals/backoffice/variants.md index 10eb9f59da2..279ee7fda07 100644 --- a/14/umbraco-cms/fundamentals/backoffice/variants.md +++ b/14/umbraco-cms/fundamentals/backoffice/variants.md @@ -82,7 +82,7 @@ This can be controlled on a User Group level. All default User Groups, except th When "Allow access to all languages" is not checked, languages can be added and/or removed. This is to determine which variants the users in the user group have access to. -![Assign access to all or individial languages on the User Group](images/Assign-Access-Languages.png) +![Assign access to all or individual languages on the User Group](images/Assign-Access-Languages.png) {% hint style="info" %} Even though the language permissions have been set, a user will still be able to view and browse all the language variations. The permission setting will ensure that only the added languages are editable by users of the User Group. diff --git a/15/umbraco-cms/fundamentals/backoffice/variants.md b/15/umbraco-cms/fundamentals/backoffice/variants.md index 63f46a99db4..df4854af045 100644 --- a/15/umbraco-cms/fundamentals/backoffice/variants.md +++ b/15/umbraco-cms/fundamentals/backoffice/variants.md @@ -82,7 +82,7 @@ This can be controlled on a User Group level. All default User Groups, except th When "Allow access to all languages" is not checked, languages can be added and/or removed. This is to determine which variants the users in the user group have access to. -![Assign access to all or individial languages on the User Group](images/Assign-Access-Languages.png) +![Assign access to all or individual languages on the User Group](images/Assign-Access-Languages.png) {% hint style="info" %} Even though the language permissions have been set, a user will still be able to view and browse all the language variations. The permission setting will ensure that only the added languages are editable by users of the User Group. diff --git a/16/umbraco-cms/fundamentals/backoffice/variants.md b/16/umbraco-cms/fundamentals/backoffice/variants.md index 63f46a99db4..df4854af045 100644 --- a/16/umbraco-cms/fundamentals/backoffice/variants.md +++ b/16/umbraco-cms/fundamentals/backoffice/variants.md @@ -82,7 +82,7 @@ This can be controlled on a User Group level. All default User Groups, except th When "Allow access to all languages" is not checked, languages can be added and/or removed. This is to determine which variants the users in the user group have access to. -![Assign access to all or individial languages on the User Group](images/Assign-Access-Languages.png) +![Assign access to all or individual languages on the User Group](images/Assign-Access-Languages.png) {% hint style="info" %} Even though the language permissions have been set, a user will still be able to view and browse all the language variations. The permission setting will ensure that only the added languages are editable by users of the User Group. From d5090c6c29e00ea4aede46fe3b4e7db065f609dd Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:48:55 +0100 Subject: [PATCH 21/42] spelling: reusabale -> reusable --- .../data/defining-content/default-document-types.md | 2 +- .../data/defining-content/default-document-types.md | 2 +- .../data/defining-content/default-document-types.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/14/umbraco-cms/fundamentals/data/defining-content/default-document-types.md b/14/umbraco-cms/fundamentals/data/defining-content/default-document-types.md index d061ca35d66..1cb58dd9bec 100644 --- a/14/umbraco-cms/fundamentals/data/defining-content/default-document-types.md +++ b/14/umbraco-cms/fundamentals/data/defining-content/default-document-types.md @@ -24,7 +24,7 @@ Use a Document Type with a template for pages like blog posts, landing pages, or ## Element Type -An Element Type is a Document Type *without a template* designed for reusabale and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. +An Element Type is a Document Type *without a template* designed for reusable and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. Element Types are not part of the Content tree and cannot render directly on the front end. When created, the **Is an Element Type** flag in the **Permissions** tab is automatically set to **True**. diff --git a/15/umbraco-cms/fundamentals/data/defining-content/default-document-types.md b/15/umbraco-cms/fundamentals/data/defining-content/default-document-types.md index c35e8106ff4..b8253cff50d 100644 --- a/15/umbraco-cms/fundamentals/data/defining-content/default-document-types.md +++ b/15/umbraco-cms/fundamentals/data/defining-content/default-document-types.md @@ -24,7 +24,7 @@ Use a Document Type with a template for pages like blog posts, landing pages, or ## Element Type -An Element Type is a Document Type *without a template* designed for reusabale and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. +An Element Type is a Document Type *without a template* designed for reusable and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. Element Types are not part of the Content tree and cannot render directly on the front end. When created, the **Is an Element Type** flag in the **Permissions** tab is automatically set to **True**. diff --git a/16/umbraco-cms/fundamentals/data/defining-content/default-document-types.md b/16/umbraco-cms/fundamentals/data/defining-content/default-document-types.md index c35e8106ff4..b8253cff50d 100644 --- a/16/umbraco-cms/fundamentals/data/defining-content/default-document-types.md +++ b/16/umbraco-cms/fundamentals/data/defining-content/default-document-types.md @@ -24,7 +24,7 @@ Use a Document Type with a template for pages like blog posts, landing pages, or ## Element Type -An Element Type is a Document Type *without a template* designed for reusabale and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. +An Element Type is a Document Type *without a template* designed for reusable and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content. Element Types are not part of the Content tree and cannot render directly on the front end. When created, the **Is an Element Type** flag in the **Permissions** tab is automatically set to **True**. From 0677ec658133f027ae662db29fde7f18b6d9f1a3 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:49:05 +0100 Subject: [PATCH 22/42] spelling: Cick -> Click --- .../fundamentals/setup/install/installing-nightly-builds.md | 2 +- .../fundamentals/setup/install/installing-nightly-builds.md | 2 +- .../fundamentals/setup/install/installing-nightly-builds.md | 2 +- .../fundamentals/setup/install/installing-nightly-builds.md | 2 +- .../fundamentals/setup/install/installing-nightly-builds.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md b/10/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md index 525414fa880..62323ec6665 100644 --- a/10/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md +++ b/10/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md @@ -63,7 +63,7 @@ To add the nightly feed using Rider: 2. Go to **View** > **Tool Windows** > **NuGet**. 3. Go to **Sources** tab. 4. Choose the `C:\Users\Úmbraco\AppData\Roaming\NuGet\NuGet.Config` to add the feed globally. -5. Cick the green `+` button in the **New Feed** field. +5. Click the green `+` button in the **New Feed** field. ![Open the new feed menu](images/Nightly/NuGet_NewFeed.jpg) diff --git a/13/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md b/13/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md index 06e9e7b98fe..93f8add8eba 100644 --- a/13/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md +++ b/13/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md @@ -62,7 +62,7 @@ To add the nightly feed using Rider: 2. Go to **View** > **Tool Windows** > **NuGet**. 3. Go to **Sources** tab. 4. Choose the `C:\Users\Úmbraco\AppData\Roaming\NuGet\NuGet.Config` to add the feed globally. -5. Cick the green `+` button in the **New Feed** field. +5. Click the green `+` button in the **New Feed** field. ![Open the new feed menu](../../../.gitbook/assets/NuGet_NewFeed.jpg) diff --git a/14/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md b/14/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md index bb9b2dfd6af..742166bb524 100644 --- a/14/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md +++ b/14/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md @@ -62,7 +62,7 @@ To add the nightly feed using Rider: 2. Go to **View** > **Tool Windows** > **NuGet**. 3. Go to **Sources** tab. 4. Choose the `C:\Users\Úmbraco\AppData\Roaming\NuGet\NuGet.Config` to add the feed globally. -5. Cick the green `+` button in the **New Feed** field. +5. Click the green `+` button in the **New Feed** field. ![Open the new feed menu](../../../.gitbook/assets/NuGet\_NewFeed.jpg) diff --git a/15/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md b/15/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md index bb9b2dfd6af..742166bb524 100644 --- a/15/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md +++ b/15/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md @@ -62,7 +62,7 @@ To add the nightly feed using Rider: 2. Go to **View** > **Tool Windows** > **NuGet**. 3. Go to **Sources** tab. 4. Choose the `C:\Users\Úmbraco\AppData\Roaming\NuGet\NuGet.Config` to add the feed globally. -5. Cick the green `+` button in the **New Feed** field. +5. Click the green `+` button in the **New Feed** field. ![Open the new feed menu](../../../.gitbook/assets/NuGet\_NewFeed.jpg) diff --git a/16/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md b/16/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md index bb9b2dfd6af..742166bb524 100644 --- a/16/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md +++ b/16/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md @@ -62,7 +62,7 @@ To add the nightly feed using Rider: 2. Go to **View** > **Tool Windows** > **NuGet**. 3. Go to **Sources** tab. 4. Choose the `C:\Users\Úmbraco\AppData\Roaming\NuGet\NuGet.Config` to add the feed globally. -5. Cick the green `+` button in the **New Feed** field. +5. Click the green `+` button in the **New Feed** field. ![Open the new feed menu](../../../.gitbook/assets/NuGet\_NewFeed.jpg) From ba64af296e1518d4254669857bae758782a9b50b Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:53:00 +0100 Subject: [PATCH 23/42] spelling: Dont -> Don't --- .../fundamentals/setup/upgrading/version-specific/README.md | 2 +- .../fundamentals/setup/upgrading/version-specific/README.md | 2 +- .../fundamentals/setup/upgrading/version-specific/README.md | 2 +- .../fundamentals/setup/upgrading/version-specific/README.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/13/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/13/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index da8e69a7cf1..12f7fb36ff0 100644 --- a/13/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/13/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -29,7 +29,7 @@ Below you can find the list of breaking changes introduced in Umbraco 13. * [Add default property value converters for all value types](https://github.com/umbraco/Umbraco-CMS/issues/14869) * [V13: Add config to limit concurrent logins](https://github.com/umbraco/Umbraco-CMS/issues/14989) * [Updates and support for re-use of CMS logic in Deploy](https://github.com/umbraco/Umbraco-CMS/issues/14990) -* [Dont explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) +* [Don't explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) * [Blocks in the Rich Text Editor](https://github.com/umbraco/Umbraco-CMS/issues/15029) * [Fix FurthestAncestorOrSelfDynamicRootQueryStep and FurthestDescendantOrSelfDynamicRootQueryStep](https://github.com/umbraco/Umbraco-CMS/issues/15113) * [Remove parameter value/return nullability in \`IImageSourceParser\`, \`ILocalLinkParser\` and \`IMacroParser\`](https://github.com/umbraco/Umbraco-CMS/issues/15130) diff --git a/14/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/14/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index 2a05f75c053..dff601d4e0a 100644 --- a/14/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/14/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -305,7 +305,7 @@ Below you can find the list of breaking changes introduced in Umbraco 13. * [Add default property value converters for all value types](https://github.com/umbraco/Umbraco-CMS/issues/14869) * [V13: Add config to limit concurrent logins](https://github.com/umbraco/Umbraco-CMS/issues/14989) * [Updates and support for re-use of CMS logic in Deploy](https://github.com/umbraco/Umbraco-CMS/issues/14990) -* [Dont explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) +* [Don't explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) * [Blocks in the Rich Text Editor](https://github.com/umbraco/Umbraco-CMS/issues/15029) * [Fix FurthestAncestorOrSelfDynamicRootQueryStep and FurthestDescendantOrSelfDynamicRootQueryStep](https://github.com/umbraco/Umbraco-CMS/issues/15113) * [Remove parameter value/return nullability in \`IImageSourceParser\`, \`ILocalLinkParser\` and \`IMacroParser\`](https://github.com/umbraco/Umbraco-CMS/issues/15130) diff --git a/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index b28154044ed..34eb878e5cf 100644 --- a/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/15/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -354,7 +354,7 @@ Below you can find the list of breaking changes introduced in Umbraco 13. * [Add default property value converters for all value types](https://github.com/umbraco/Umbraco-CMS/issues/14869) * [V13: Add config to limit concurrent logins](https://github.com/umbraco/Umbraco-CMS/issues/14989) * [Updates and support for re-use of CMS logic in Deploy](https://github.com/umbraco/Umbraco-CMS/issues/14990) -* [Dont explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) +* [Don't explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) * [Blocks in the Rich Text Editor](https://github.com/umbraco/Umbraco-CMS/issues/15029) * [Fix FurthestAncestorOrSelfDynamicRootQueryStep and FurthestDescendantOrSelfDynamicRootQueryStep](https://github.com/umbraco/Umbraco-CMS/issues/15113) * [Remove parameter value/return nullability in \`IImageSourceParser\`, \`ILocalLinkParser\` and \`IMacroParser\`](https://github.com/umbraco/Umbraco-CMS/issues/15130) diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index e2c564621de..809f0b16a0b 100644 --- a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -393,7 +393,7 @@ Below you can find the list of breaking changes introduced in Umbraco 13. * [Add default property value converters for all value types](https://github.com/umbraco/Umbraco-CMS/issues/14869) * [V13: Add config to limit concurrent logins](https://github.com/umbraco/Umbraco-CMS/issues/14989) * [Updates and support for re-use of CMS logic in Deploy](https://github.com/umbraco/Umbraco-CMS/issues/14990) -* [Dont explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) +* [Don't explicitly index nested property by default](https://github.com/umbraco/Umbraco-CMS/issues/15028) * [Blocks in the Rich Text Editor](https://github.com/umbraco/Umbraco-CMS/issues/15029) * [Fix FurthestAncestorOrSelfDynamicRootQueryStep and FurthestDescendantOrSelfDynamicRootQueryStep](https://github.com/umbraco/Umbraco-CMS/issues/15113) * [Remove parameter value/return nullability in \`IImageSourceParser\`, \`ILocalLinkParser\` and \`IMacroParser\`](https://github.com/umbraco/Umbraco-CMS/issues/15130) From 92f250a3a0229846e253ba12fd3983fe70ed6c58 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 10:58:41 +0100 Subject: [PATCH 24/42] spelling: Umbrco -> Umbraco --- 10/umbraco-cms/legacy-documentation/README.md | 2 +- 13/umbraco-cms/legacy-documentation/README.md | 2 +- 14/umbraco-cms/legacy-documentation/README.md | 2 +- 15/umbraco-cms/legacy-documentation/README.md | 2 +- 16/umbraco-cms/legacy-documentation/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/legacy-documentation/README.md b/10/umbraco-cms/legacy-documentation/README.md index 4b33e908a55..01174b16a74 100644 --- a/10/umbraco-cms/legacy-documentation/README.md +++ b/10/umbraco-cms/legacy-documentation/README.md @@ -1,5 +1,5 @@ --- -description: Resources and links for older versions of Umbrco CMS. +description: Resources and links for older versions of Umbraco CMS. --- # Legacy Documentation diff --git a/13/umbraco-cms/legacy-documentation/README.md b/13/umbraco-cms/legacy-documentation/README.md index 4b33e908a55..01174b16a74 100644 --- a/13/umbraco-cms/legacy-documentation/README.md +++ b/13/umbraco-cms/legacy-documentation/README.md @@ -1,5 +1,5 @@ --- -description: Resources and links for older versions of Umbrco CMS. +description: Resources and links for older versions of Umbraco CMS. --- # Legacy Documentation diff --git a/14/umbraco-cms/legacy-documentation/README.md b/14/umbraco-cms/legacy-documentation/README.md index cfbf35ba351..4bb1f12869a 100644 --- a/14/umbraco-cms/legacy-documentation/README.md +++ b/14/umbraco-cms/legacy-documentation/README.md @@ -1,5 +1,5 @@ --- -description: Resources and links for older versions of Umbrco CMS. +description: Resources and links for older versions of Umbraco CMS. --- # Legacy Documentation diff --git a/15/umbraco-cms/legacy-documentation/README.md b/15/umbraco-cms/legacy-documentation/README.md index cfbf35ba351..4bb1f12869a 100644 --- a/15/umbraco-cms/legacy-documentation/README.md +++ b/15/umbraco-cms/legacy-documentation/README.md @@ -1,5 +1,5 @@ --- -description: Resources and links for older versions of Umbrco CMS. +description: Resources and links for older versions of Umbraco CMS. --- # Legacy Documentation diff --git a/16/umbraco-cms/legacy-documentation/README.md b/16/umbraco-cms/legacy-documentation/README.md index cfbf35ba351..4bb1f12869a 100644 --- a/16/umbraco-cms/legacy-documentation/README.md +++ b/16/umbraco-cms/legacy-documentation/README.md @@ -1,5 +1,5 @@ --- -description: Resources and links for older versions of Umbrco CMS. +description: Resources and links for older versions of Umbraco CMS. --- # Legacy Documentation From 70273c67bf2fd24cd2f90843ea425358227bd5a2 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:00:20 +0100 Subject: [PATCH 25/42] spelling: Recommeded -> Recommended --- 10/umbraco-cms/reference/configuration/datatypes.md | 2 +- 13/umbraco-cms/reference/configuration/datatypes.md | 2 +- 14/umbraco-cms/reference/configuration/datatypes.md | 2 +- 15/umbraco-cms/reference/configuration/datatypes.md | 2 +- 16/umbraco-cms/reference/configuration/datatypes.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/datatypes.md b/10/umbraco-cms/reference/configuration/datatypes.md index 5fe3efde9fc..9bbf649a95d 100644 --- a/10/umbraco-cms/reference/configuration/datatypes.md +++ b/10/umbraco-cms/reference/configuration/datatypes.md @@ -29,6 +29,6 @@ Valid values: - `"True"` - Allows data types to be changed after creation. This can lead to data on content is not valid on the Data Type. - `"False"` - - Disallow Data Type changes. (Recommeded value, unless you really know what you are doing) + - Disallow Data Type changes. (Recommended value, unless you really know what you are doing) - `"FalseWithHelpText"` - Disallow Data Type changes, but show the users a help text so they understand why. diff --git a/13/umbraco-cms/reference/configuration/datatypes.md b/13/umbraco-cms/reference/configuration/datatypes.md index 5d65f725f6a..89ff8a7efb5 100644 --- a/13/umbraco-cms/reference/configuration/datatypes.md +++ b/13/umbraco-cms/reference/configuration/datatypes.md @@ -27,6 +27,6 @@ Valid values: - `"True"` - Allows data types to be changed after creation. This can lead to data on content is not valid on the Data Type. - `"False"` - - Disallow Data Type changes. (Recommeded value, unless you really know what you are doing) + - Disallow Data Type changes. (Recommended value, unless you really know what you are doing) - `"FalseWithHelpText"` - Disallow Data Type changes, but show the users a help text so they understand why. diff --git a/14/umbraco-cms/reference/configuration/datatypes.md b/14/umbraco-cms/reference/configuration/datatypes.md index 5d65f725f6a..89ff8a7efb5 100644 --- a/14/umbraco-cms/reference/configuration/datatypes.md +++ b/14/umbraco-cms/reference/configuration/datatypes.md @@ -27,6 +27,6 @@ Valid values: - `"True"` - Allows data types to be changed after creation. This can lead to data on content is not valid on the Data Type. - `"False"` - - Disallow Data Type changes. (Recommeded value, unless you really know what you are doing) + - Disallow Data Type changes. (Recommended value, unless you really know what you are doing) - `"FalseWithHelpText"` - Disallow Data Type changes, but show the users a help text so they understand why. diff --git a/15/umbraco-cms/reference/configuration/datatypes.md b/15/umbraco-cms/reference/configuration/datatypes.md index 5d65f725f6a..89ff8a7efb5 100644 --- a/15/umbraco-cms/reference/configuration/datatypes.md +++ b/15/umbraco-cms/reference/configuration/datatypes.md @@ -27,6 +27,6 @@ Valid values: - `"True"` - Allows data types to be changed after creation. This can lead to data on content is not valid on the Data Type. - `"False"` - - Disallow Data Type changes. (Recommeded value, unless you really know what you are doing) + - Disallow Data Type changes. (Recommended value, unless you really know what you are doing) - `"FalseWithHelpText"` - Disallow Data Type changes, but show the users a help text so they understand why. diff --git a/16/umbraco-cms/reference/configuration/datatypes.md b/16/umbraco-cms/reference/configuration/datatypes.md index 5d65f725f6a..89ff8a7efb5 100644 --- a/16/umbraco-cms/reference/configuration/datatypes.md +++ b/16/umbraco-cms/reference/configuration/datatypes.md @@ -27,6 +27,6 @@ Valid values: - `"True"` - Allows data types to be changed after creation. This can lead to data on content is not valid on the Data Type. - `"False"` - - Disallow Data Type changes. (Recommeded value, unless you really know what you are doing) + - Disallow Data Type changes. (Recommended value, unless you really know what you are doing) - `"FalseWithHelpText"` - Disallow Data Type changes, but show the users a help text so they understand why. From c60d699958ce0642331eaecd96aea7365914cec9 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:01:05 +0100 Subject: [PATCH 26/42] spelling: ExecptionFilter -> ExceptionFilter --- .../reference/configuration/exceptionfiltersettings.md | 2 +- .../reference/configuration/exceptionfiltersettings.md | 2 +- .../reference/configuration/exceptionfiltersettings.md | 2 +- .../reference/configuration/exceptionfiltersettings.md | 2 +- .../reference/configuration/exceptionfiltersettings.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/exceptionfiltersettings.md b/10/umbraco-cms/reference/configuration/exceptionfiltersettings.md index 56212464919..b475debd0de 100644 --- a/10/umbraco-cms/reference/configuration/exceptionfiltersettings.md +++ b/10/umbraco-cms/reference/configuration/exceptionfiltersettings.md @@ -9,7 +9,7 @@ description: "Information on the exception filter settings section" This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this. -By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExecptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: +By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExceptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: ```json "Umbraco": { diff --git a/13/umbraco-cms/reference/configuration/exceptionfiltersettings.md b/13/umbraco-cms/reference/configuration/exceptionfiltersettings.md index 1fecfe066e1..b69598318f4 100644 --- a/13/umbraco-cms/reference/configuration/exceptionfiltersettings.md +++ b/13/umbraco-cms/reference/configuration/exceptionfiltersettings.md @@ -5,7 +5,7 @@ description: "Information on the exception filter settings section" # Exception filter settings This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this. -By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExecptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: +By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExceptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: ```json "Umbraco": { diff --git a/14/umbraco-cms/reference/configuration/exceptionfiltersettings.md b/14/umbraco-cms/reference/configuration/exceptionfiltersettings.md index 1fecfe066e1..b69598318f4 100644 --- a/14/umbraco-cms/reference/configuration/exceptionfiltersettings.md +++ b/14/umbraco-cms/reference/configuration/exceptionfiltersettings.md @@ -5,7 +5,7 @@ description: "Information on the exception filter settings section" # Exception filter settings This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this. -By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExecptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: +By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExceptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: ```json "Umbraco": { diff --git a/15/umbraco-cms/reference/configuration/exceptionfiltersettings.md b/15/umbraco-cms/reference/configuration/exceptionfiltersettings.md index e7750ccd9cd..33c7dab5540 100644 --- a/15/umbraco-cms/reference/configuration/exceptionfiltersettings.md +++ b/15/umbraco-cms/reference/configuration/exceptionfiltersettings.md @@ -4,7 +4,7 @@ description: Information on the exception filter settings section # Exception filter settings -This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this. By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExecptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: +This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this. By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExceptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: ```json "Umbraco": { diff --git a/16/umbraco-cms/reference/configuration/exceptionfiltersettings.md b/16/umbraco-cms/reference/configuration/exceptionfiltersettings.md index 6ee5e999f65..256af1cee13 100644 --- a/16/umbraco-cms/reference/configuration/exceptionfiltersettings.md +++ b/16/umbraco-cms/reference/configuration/exceptionfiltersettings.md @@ -5,7 +5,7 @@ description: Information on the exception filter settings section # Exception filter settings This section allows you to disable the `ModelBindingExceptionFilter`, this filter is only enable if the models builder mode is set to `InMemoryAuto`. This filter will return a redirect to the page being loaded after one second, if a `ModelsBindingException` or `InvalidCastException` occurs. The reason for this filter is that a page might be requested at the same time as the content type has been changed. If this occurs, the new model might not have been generated and loaded yet. This filter will take care of this.\ -By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExecptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: +By default this filter is enabled, but will be ignored if the mode is not `InMemoryAuto`. To manually disable the filter add the `"ExceptionFilter"` section to your config with the `"Disabled"` key set to `true` like so: ```json "Umbraco": { From 29e3107b7258bd53ee0455a4b68fd499f252c2ed Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:01:25 +0100 Subject: [PATCH 27/42] spelling: virutal -> virtual --- 10/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 13/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 14/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 15/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 16/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/filesystemproviders.md b/10/umbraco-cms/reference/configuration/filesystemproviders.md index 6c340caf689..e38b9bb4fa6 100644 --- a/10/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/10/umbraco-cms/reference/configuration/filesystemproviders.md @@ -108,7 +108,7 @@ namespace FilesystemProviders } ``` -This is much the same as when you register it within the wwwroot with a virutal folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. - `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. - `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/13/umbraco-cms/reference/configuration/filesystemproviders.md b/13/umbraco-cms/reference/configuration/filesystemproviders.md index 523410fe4c4..25612a9afa8 100644 --- a/13/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/13/umbraco-cms/reference/configuration/filesystemproviders.md @@ -101,7 +101,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virutal folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/14/umbraco-cms/reference/configuration/filesystemproviders.md b/14/umbraco-cms/reference/configuration/filesystemproviders.md index 0bac9982caa..5b2af582c17 100644 --- a/14/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/14/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virutal folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/15/umbraco-cms/reference/configuration/filesystemproviders.md b/15/umbraco-cms/reference/configuration/filesystemproviders.md index 0bac9982caa..5b2af582c17 100644 --- a/15/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/15/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virutal folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/16/umbraco-cms/reference/configuration/filesystemproviders.md b/16/umbraco-cms/reference/configuration/filesystemproviders.md index 0bac9982caa..5b2af582c17 100644 --- a/16/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/16/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virutal folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). From 4a9fa6f6ed7b5901786b9061fce6dd8015960b0d Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:01:48 +0100 Subject: [PATCH 28/42] spelling: differnce -> difference --- 10/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 13/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 14/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 15/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 16/umbraco-cms/reference/configuration/filesystemproviders.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/filesystemproviders.md b/10/umbraco-cms/reference/configuration/filesystemproviders.md index e38b9bb4fa6..2f074636198 100644 --- a/10/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/10/umbraco-cms/reference/configuration/filesystemproviders.md @@ -108,7 +108,7 @@ namespace FilesystemProviders } ``` -This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only difference is that now you provide an absolute root path and root URL to the physical filesystem. - `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. - `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/13/umbraco-cms/reference/configuration/filesystemproviders.md b/13/umbraco-cms/reference/configuration/filesystemproviders.md index 25612a9afa8..c946472ffbd 100644 --- a/13/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/13/umbraco-cms/reference/configuration/filesystemproviders.md @@ -101,7 +101,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only difference is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/14/umbraco-cms/reference/configuration/filesystemproviders.md b/14/umbraco-cms/reference/configuration/filesystemproviders.md index 5b2af582c17..7042a77bf85 100644 --- a/14/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/14/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only difference is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/15/umbraco-cms/reference/configuration/filesystemproviders.md b/15/umbraco-cms/reference/configuration/filesystemproviders.md index 5b2af582c17..7042a77bf85 100644 --- a/15/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/15/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only difference is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). diff --git a/16/umbraco-cms/reference/configuration/filesystemproviders.md b/16/umbraco-cms/reference/configuration/filesystemproviders.md index 5b2af582c17..7042a77bf85 100644 --- a/16/umbraco-cms/reference/configuration/filesystemproviders.md +++ b/16/umbraco-cms/reference/configuration/filesystemproviders.md @@ -97,7 +97,7 @@ public class FilesystemComposer : IComposer } ``` -This is much the same as when you register it within the wwwroot with a virtual folder. The only differnce is that now you provide an absolute root path and root URL to the physical filesystem. +This is much the same as when you register it within the wwwroot with a virtual folder. The only difference is that now you provide an absolute root path and root URL to the physical filesystem. * `rootPath` is the full filesystem path where you want media files to be stored. It has to be rooted, must use directory separators (`\`) and must not end with a separator. For example, `Z:` or `C:\path\to\folder` or `\\servername\path`. * `rootUrl` is the URL where the files will be accessible from. It must use URL separators (`/`) and must not end with a separator. It can either be a folder, like `/UmbracoMedia`, in which case it will considered as subfolder of the main domain (`example.com/UmbracoMedia`) or can be a fully qualified URL, with also domain name and protocol (for ex `http://media.example.com/media`). From 6a97fef5bfefb81cffa18341f9ea2f7af27e6901 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:04:25 +0100 Subject: [PATCH 29/42] spelling: seperate -> separate --- 10/umbraco-cms/reference/configuration/contentsettings.md | 2 +- 10/umbraco-cms/reference/configuration/globalsettings.md | 4 ++-- .../reference/configuration/richtexteditorsettings.md | 2 +- .../reference/routing/request-pipeline/outbound-pipeline.md | 2 +- 13/umbraco-cms/reference/configuration/globalsettings.md | 4 ++-- .../reference/configuration/richtexteditorsettings.md | 2 +- 13/umbraco-commerce/reference/storefront-api/README.md | 4 ++-- 14/umbraco-cms/reference/configuration/globalsettings.md | 4 ++-- 14/umbraco-commerce/reference/storefront-api/README.md | 4 ++-- 15/umbraco-cms/reference/configuration/globalsettings.md | 4 ++-- 15/umbraco-commerce/reference/storefront-api/README.md | 4 ++-- 16/umbraco-cms/reference/configuration/globalsettings.md | 4 ++-- 16/umbraco-commerce/reference/storefront-api/README.md | 4 ++-- 13 files changed, 22 insertions(+), 22 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/contentsettings.md b/10/umbraco-cms/reference/configuration/contentsettings.md index 8f8c2a7cede..ccfe3241187 100644 --- a/10/umbraco-cms/reference/configuration/contentsettings.md +++ b/10/umbraco-cms/reference/configuration/contentsettings.md @@ -54,7 +54,7 @@ From 10.4, `AllowedUploadFiles` & `DisallowedUploadFiles` is deprecated, they wi ## Root level settings -In the root level section, that is those without a seperate sub section like Imaging, you can configure: +In the root level section, that is those without a separate sub section like Imaging, you can configure: ### Allow Edit Invariant From Non-Default diff --git a/10/umbraco-cms/reference/configuration/globalsettings.md b/10/umbraco-cms/reference/configuration/globalsettings.md index a9a921ec87f..c241b98fc43 100644 --- a/10/umbraco-cms/reference/configuration/globalsettings.md +++ b/10/umbraco-cms/reference/configuration/globalsettings.md @@ -121,11 +121,11 @@ The following snippet contains all the available options, with default values, a ## Root level settings -In the root level section, that is those without a seperate sub section like SMTP, you can configure +In the root level section, that is those without a separate sub section like SMTP, you can configure ### Reserved urls -A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. +A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. ### Reserved paths diff --git a/10/umbraco-cms/reference/configuration/richtexteditorsettings.md b/10/umbraco-cms/reference/configuration/richtexteditorsettings.md index d3ccbaa30a8..06d530d8d8c 100644 --- a/10/umbraco-cms/reference/configuration/richtexteditorsettings.md +++ b/10/umbraco-cms/reference/configuration/richtexteditorsettings.md @@ -47,7 +47,7 @@ A config with all the values can be seen underneath. Since there is a lot of def ## Plugins -Allows you to specify what plugins should be enabled for the rich text editor as a comma seperated list of the plugin names. +Allows you to specify what plugins should be enabled for the rich text editor as a comma separated list of the plugin names. ## Valid elements 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 7dbe7e5ecab..4588fe7d2e8 100644 --- a/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md +++ b/10/umbraco-cms/reference/routing/request-pipeline/outbound-pipeline.md @@ -397,7 +397,7 @@ namespace RoutingDocs.SiteDomainMapper ### Default SiteDomainMapper -Umbraco ships with a default `SiteDomainMapper`. This has some useful functionality for grouping sets of domains together. With Umbraco Cloud, or another Umbraco development environment scenario, there maybe be multiple domains setup for a site 'live, 'staging', 'testing' or a seperate domain to access the backoffice. Each domain will be setup as a 'Culture and Hostname' inside Umbraco. By default editors will see the full list of possible Urls for each of their content items on each domain, which can be confusing. If the additional urls aren't present in Culture and Hostnames, then when testing the front-end of the site on a 'staging' url, will result in navigation links taking you to the registered domain! +Umbraco ships with a default `SiteDomainMapper`. This has some useful functionality for grouping sets of domains together. With Umbraco Cloud, or another Umbraco development environment scenario, there maybe be multiple domains setup for a site 'live, 'staging', 'testing' or a separate domain to access the backoffice. Each domain will be setup as a 'Culture and Hostname' inside Umbraco. By default editors will see the full list of possible Urls for each of their content items on each domain, which can be confusing. If the additional urls aren't present in Culture and Hostnames, then when testing the front-end of the site on a 'staging' url, will result in navigation links taking you to the registered domain! ![Culture and Hostnames multiple domains](images/culture-and-hostnames-v8.png) diff --git a/13/umbraco-cms/reference/configuration/globalsettings.md b/13/umbraco-cms/reference/configuration/globalsettings.md index b825d7fc624..b271c3f53e5 100644 --- a/13/umbraco-cms/reference/configuration/globalsettings.md +++ b/13/umbraco-cms/reference/configuration/globalsettings.md @@ -62,11 +62,11 @@ The following snippet contains all the available options, with default values, a ## Root level settings -In the root level section, that is those without a seperate sub section like SMTP, you can configure +In the root level section, that is those without a separate sub section like SMTP, you can configure ### Reserved urls -A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. +A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. ### Reserved paths diff --git a/13/umbraco-cms/reference/configuration/richtexteditorsettings.md b/13/umbraco-cms/reference/configuration/richtexteditorsettings.md index a0f434faaba..bce3e36c2c4 100644 --- a/13/umbraco-cms/reference/configuration/richtexteditorsettings.md +++ b/13/umbraco-cms/reference/configuration/richtexteditorsettings.md @@ -61,7 +61,7 @@ A config with all the values can be seen underneath. Since there are a lot of de ## Plugins -Allows you to specify what plugins should be enabled for the rich text editor as a comma seperated list of the plugin names. +Allows you to specify what plugins should be enabled for the rich text editor as a comma separated list of the plugin names. To learn more about how to use the plugins, see the [Rich Text Editor Plugins](../../fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/rte-plugins.md) article. diff --git a/13/umbraco-commerce/reference/storefront-api/README.md b/13/umbraco-commerce/reference/storefront-api/README.md index f8ff08d1b7e..506d7e6891c 100644 --- a/13/umbraco-commerce/reference/storefront-api/README.md +++ b/13/umbraco-commerce/reference/storefront-api/README.md @@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 } ``` -The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. +The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. ```http GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod @@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 When using the `fields` query parameter to limit fields returned, `id` properties will always be included. -Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax. +Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax. **Request** diff --git a/14/umbraco-cms/reference/configuration/globalsettings.md b/14/umbraco-cms/reference/configuration/globalsettings.md index 1294c5eac71..11b38077578 100644 --- a/14/umbraco-cms/reference/configuration/globalsettings.md +++ b/14/umbraco-cms/reference/configuration/globalsettings.md @@ -61,14 +61,14 @@ The following snippet contains all the available options, with default values, a ## Root level settings -In the root level section, that is those without a seperate sub section like SMTP, you can configure +In the root level section, that is those without a separate sub section like SMTP, you can configure ### Reserved urls Key: `ReservedUrls` Type: `string` (default: `~/.well-known,`) -A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. +A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. ### Reserved paths diff --git a/14/umbraco-commerce/reference/storefront-api/README.md b/14/umbraco-commerce/reference/storefront-api/README.md index f8ff08d1b7e..506d7e6891c 100644 --- a/14/umbraco-commerce/reference/storefront-api/README.md +++ b/14/umbraco-commerce/reference/storefront-api/README.md @@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 } ``` -The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. +The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. ```http GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod @@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 When using the `fields` query parameter to limit fields returned, `id` properties will always be included. -Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax. +Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax. **Request** diff --git a/15/umbraco-cms/reference/configuration/globalsettings.md b/15/umbraco-cms/reference/configuration/globalsettings.md index 378016df0f6..c13629ca2d3 100644 --- a/15/umbraco-cms/reference/configuration/globalsettings.md +++ b/15/umbraco-cms/reference/configuration/globalsettings.md @@ -61,14 +61,14 @@ The following snippet contains all the available options, with default values, a ## Root level settings -In the root level section, that is those without a seperate sub section like SMTP, you can configure. +In the root level section, that is those without a separate sub section like SMTP, you can configure. ### Reserved urls Key: `ReservedUrls` Type: `string` (default: `~/.well-known,`) -A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. +A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. ### Reserved paths diff --git a/15/umbraco-commerce/reference/storefront-api/README.md b/15/umbraco-commerce/reference/storefront-api/README.md index f8ff08d1b7e..506d7e6891c 100644 --- a/15/umbraco-commerce/reference/storefront-api/README.md +++ b/15/umbraco-commerce/reference/storefront-api/README.md @@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 } ``` -The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. +The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. ```http GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod @@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 When using the `fields` query parameter to limit fields returned, `id` properties will always be included. -Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax. +Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax. **Request** diff --git a/16/umbraco-cms/reference/configuration/globalsettings.md b/16/umbraco-cms/reference/configuration/globalsettings.md index 378016df0f6..c13629ca2d3 100644 --- a/16/umbraco-cms/reference/configuration/globalsettings.md +++ b/16/umbraco-cms/reference/configuration/globalsettings.md @@ -61,14 +61,14 @@ The following snippet contains all the available options, with default values, a ## Root level settings -In the root level section, that is those without a seperate sub section like SMTP, you can configure. +In the root level section, that is those without a separate sub section like SMTP, you can configure. ### Reserved urls Key: `ReservedUrls` Type: `string` (default: `~/.well-known,`) -A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. +A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered. ### Reserved paths diff --git a/16/umbraco-commerce/reference/storefront-api/README.md b/16/umbraco-commerce/reference/storefront-api/README.md index f8ff08d1b7e..506d7e6891c 100644 --- a/16/umbraco-commerce/reference/storefront-api/README.md +++ b/16/umbraco-commerce/reference/storefront-api/README.md @@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 } ``` -The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. +The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. ```http GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod @@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9 When using the `fields` query parameter to limit fields returned, `id` properties will always be included. -Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax. +Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax. **Request** From 13b1fb3380f6c2133f8f0079ca1d4afe36439637 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:04:55 +0100 Subject: [PATCH 30/42] spelling: conjuction -> conjunction --- 10/umbraco-cms/reference/configuration/globalsettings.md | 2 +- 13/umbraco-cms/reference/configuration/globalsettings.md | 2 +- 14/umbraco-cms/reference/configuration/globalsettings.md | 2 +- 15/umbraco-cms/reference/configuration/globalsettings.md | 2 +- 16/umbraco-cms/reference/configuration/globalsettings.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/globalsettings.md b/10/umbraco-cms/reference/configuration/globalsettings.md index c241b98fc43..3ef6dce71e6 100644 --- a/10/umbraco-cms/reference/configuration/globalsettings.md +++ b/10/umbraco-cms/reference/configuration/globalsettings.md @@ -177,7 +177,7 @@ By adding this you can specify a new/different folder for storing your media fil This is not a setting that commonly needs to be configured. -If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjuction with unattended installs. +If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjunction with unattended installs. ### Disable election for single server diff --git a/13/umbraco-cms/reference/configuration/globalsettings.md b/13/umbraco-cms/reference/configuration/globalsettings.md index b271c3f53e5..00c8c0fbc32 100644 --- a/13/umbraco-cms/reference/configuration/globalsettings.md +++ b/13/umbraco-cms/reference/configuration/globalsettings.md @@ -120,7 +120,7 @@ By adding this you can specify a new/different folder for storing your media fil This is not a setting that commonly needs to be configured. -If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjuction with unattended installs. +If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjunction with unattended installs. ### Disable election for single server diff --git a/14/umbraco-cms/reference/configuration/globalsettings.md b/14/umbraco-cms/reference/configuration/globalsettings.md index 11b38077578..26dd7dfc354 100644 --- a/14/umbraco-cms/reference/configuration/globalsettings.md +++ b/14/umbraco-cms/reference/configuration/globalsettings.md @@ -158,7 +158,7 @@ Type: `bool` (default: `false`) This is not a setting that commonly needs to be configured. -If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjuction with unattended installs. +If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjunction with unattended installs. ### Disable election for single server diff --git a/15/umbraco-cms/reference/configuration/globalsettings.md b/15/umbraco-cms/reference/configuration/globalsettings.md index c13629ca2d3..5409f19f687 100644 --- a/15/umbraco-cms/reference/configuration/globalsettings.md +++ b/15/umbraco-cms/reference/configuration/globalsettings.md @@ -162,7 +162,7 @@ Type: `bool` (default: `false`) This is not a setting that commonly needs to be configured. -If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjuction with unattended installs. +If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjunction with unattended installs. ### Disable election for single server diff --git a/16/umbraco-cms/reference/configuration/globalsettings.md b/16/umbraco-cms/reference/configuration/globalsettings.md index c13629ca2d3..5409f19f687 100644 --- a/16/umbraco-cms/reference/configuration/globalsettings.md +++ b/16/umbraco-cms/reference/configuration/globalsettings.md @@ -162,7 +162,7 @@ Type: `bool` (default: `false`) This is not a setting that commonly needs to be configured. -If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjuction with unattended installs. +If enabled Umbraco will try to automatically install the database when it's missing. This is primarily used in conjunction with unattended installs. ### Disable election for single server From ea45b4b51293c8bcc10ffdffcbe8042f1f552a20 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:05:48 +0100 Subject: [PATCH 31/42] spelling: corosponding -> corresponding --- 10/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 13/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 14/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 15/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 16/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/healthchecks.md b/10/umbraco-cms/reference/configuration/healthchecks.md index ff271dd3dc9..146479057c7 100644 --- a/10/umbraco-cms/reference/configuration/healthchecks.md +++ b/10/umbraco-cms/reference/configuration/healthchecks.md @@ -48,7 +48,7 @@ But let's go through the config one by one ## Disabled checks -A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corosponding to the GUID of the health check to disable. +A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. diff --git a/13/umbraco-cms/reference/configuration/healthchecks.md b/13/umbraco-cms/reference/configuration/healthchecks.md index 8c60d712be9..27a886947c1 100644 --- a/13/umbraco-cms/reference/configuration/healthchecks.md +++ b/13/umbraco-cms/reference/configuration/healthchecks.md @@ -45,7 +45,7 @@ But let's go through the config one by one ## Disabled checks -A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corosponding to the GUID of the health check to disable. +A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. diff --git a/14/umbraco-cms/reference/configuration/healthchecks.md b/14/umbraco-cms/reference/configuration/healthchecks.md index d41e9c5991c..fe26adca402 100644 --- a/14/umbraco-cms/reference/configuration/healthchecks.md +++ b/14/umbraco-cms/reference/configuration/healthchecks.md @@ -45,7 +45,7 @@ But let's go through the config one by one ## Disabled checks -A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corosponding to the GUID of the health check to disable. +A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. diff --git a/15/umbraco-cms/reference/configuration/healthchecks.md b/15/umbraco-cms/reference/configuration/healthchecks.md index d41e9c5991c..fe26adca402 100644 --- a/15/umbraco-cms/reference/configuration/healthchecks.md +++ b/15/umbraco-cms/reference/configuration/healthchecks.md @@ -45,7 +45,7 @@ But let's go through the config one by one ## Disabled checks -A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corosponding to the GUID of the health check to disable. +A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. diff --git a/16/umbraco-cms/reference/configuration/healthchecks.md b/16/umbraco-cms/reference/configuration/healthchecks.md index d41e9c5991c..fe26adca402 100644 --- a/16/umbraco-cms/reference/configuration/healthchecks.md +++ b/16/umbraco-cms/reference/configuration/healthchecks.md @@ -45,7 +45,7 @@ But let's go through the config one by one ## Disabled checks -A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corosponding to the GUID of the health check to disable. +A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. From 42c231d1e821e9a5400850f61168462eb0852722 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:06:14 +0100 Subject: [PATCH 32/42] spelling: disabked -> disabled --- 10/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 13/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 14/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 15/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 16/umbraco-cms/reference/configuration/healthchecks.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/healthchecks.md b/10/umbraco-cms/reference/configuration/healthchecks.md index 146479057c7..110894119ae 100644 --- a/10/umbraco-cms/reference/configuration/healthchecks.md +++ b/10/umbraco-cms/reference/configuration/healthchecks.md @@ -50,7 +50,7 @@ But let's go through the config one by one A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. -There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. +There is also a `DisabledOn` key representing the date the health check was disabled and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. ## Notification diff --git a/13/umbraco-cms/reference/configuration/healthchecks.md b/13/umbraco-cms/reference/configuration/healthchecks.md index 27a886947c1..308334c9242 100644 --- a/13/umbraco-cms/reference/configuration/healthchecks.md +++ b/13/umbraco-cms/reference/configuration/healthchecks.md @@ -47,7 +47,7 @@ But let's go through the config one by one A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. -There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. +There is also a `DisabledOn` key representing the date the health check was disabled and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. ## Notification diff --git a/14/umbraco-cms/reference/configuration/healthchecks.md b/14/umbraco-cms/reference/configuration/healthchecks.md index fe26adca402..814fe593c8c 100644 --- a/14/umbraco-cms/reference/configuration/healthchecks.md +++ b/14/umbraco-cms/reference/configuration/healthchecks.md @@ -47,7 +47,7 @@ But let's go through the config one by one A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. -There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. +There is also a `DisabledOn` key representing the date the health check was disabled and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. ## Notification diff --git a/15/umbraco-cms/reference/configuration/healthchecks.md b/15/umbraco-cms/reference/configuration/healthchecks.md index fe26adca402..814fe593c8c 100644 --- a/15/umbraco-cms/reference/configuration/healthchecks.md +++ b/15/umbraco-cms/reference/configuration/healthchecks.md @@ -47,7 +47,7 @@ But let's go through the config one by one A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. -There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. +There is also a `DisabledOn` key representing the date the health check was disabled and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. ## Notification diff --git a/16/umbraco-cms/reference/configuration/healthchecks.md b/16/umbraco-cms/reference/configuration/healthchecks.md index fe26adca402..814fe593c8c 100644 --- a/16/umbraco-cms/reference/configuration/healthchecks.md +++ b/16/umbraco-cms/reference/configuration/healthchecks.md @@ -47,7 +47,7 @@ But let's go through the config one by one A list of `DisabledHealthCheckSettings` objects, each of these objects represents a disabled health check. Only the Id key needs to be present and have a value, corresponding to the GUID of the health check to disable. -There is also a `DisabledOn` key representing the date the health check was disabked and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. +There is also a `DisabledOn` key representing the date the health check was disabled and a `DisabledBy` key containing the ID of the user that disabled the health check, however these values are currently not used. ## Notification From 1f09d5674ce3057cf13a650d02fa48a276779489 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:06:58 +0100 Subject: [PATCH 33/42] spelling: AccceptUnsafeModelsDirectory -> AcceptUnsafeModelsDirectory --- 10/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 13/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 14/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 15/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 16/umbraco-cms/reference/configuration/modelsbuildersettings.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/modelsbuildersettings.md b/10/umbraco-cms/reference/configuration/modelsbuildersettings.md index 9da2bb8a1db..fd868a324de 100644 --- a/10/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/10/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -49,7 +49,7 @@ If you set this setting to true while using an `Auto` mode, it will automaticall ## Models directory -Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AccceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. +Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AcceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. {% hint style="info" %} If you want to generate models outside the web project you can change the ModelsDirectory path. Suppose you have a data project called My.Website.Data the ModelsDirectory path should be: diff --git a/13/umbraco-cms/reference/configuration/modelsbuildersettings.md b/13/umbraco-cms/reference/configuration/modelsbuildersettings.md index 009cbd0ab0f..b2d3c8275a6 100644 --- a/13/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/13/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -47,7 +47,7 @@ If you set this setting to true while using an `Auto` mode, it will automaticall ## Models directory -Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AccceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. +Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AcceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. {% hint style="info" %} If you want to generate models outside the web project you can change the ModelsDirectory path. Suppose you have a data project called My.Website.Data the ModelsDirectory path should be: diff --git a/14/umbraco-cms/reference/configuration/modelsbuildersettings.md b/14/umbraco-cms/reference/configuration/modelsbuildersettings.md index 1b7f36e5809..e42878d3bbf 100644 --- a/14/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/14/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -50,7 +50,7 @@ If you set this setting to true while using an `Auto` mode, it will automaticall ## Models directory -Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AccceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. +Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AcceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. {% hint style="info" %} If you want to generate models outside the web project you can change the ModelsDirectory path. Suppose you have a data project called My.Website.Data the ModelsDirectory path should be: diff --git a/15/umbraco-cms/reference/configuration/modelsbuildersettings.md b/15/umbraco-cms/reference/configuration/modelsbuildersettings.md index ca6f20a61b2..3b3fd62fc86 100644 --- a/15/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/15/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -51,7 +51,7 @@ If you set this setting to true while using an `Auto` mode, it will automaticall ## Models directory -Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AccceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. +Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AcceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. {% hint style="info" %} If you want to generate models outside the web project you can change the ModelsDirectory path. Suppose you have a data project called My.Website.Data the ModelsDirectory path should be: diff --git a/16/umbraco-cms/reference/configuration/modelsbuildersettings.md b/16/umbraco-cms/reference/configuration/modelsbuildersettings.md index ca6f20a61b2..3b3fd62fc86 100644 --- a/16/umbraco-cms/reference/configuration/modelsbuildersettings.md +++ b/16/umbraco-cms/reference/configuration/modelsbuildersettings.md @@ -51,7 +51,7 @@ If you set this setting to true while using an `Auto` mode, it will automaticall ## Models directory -Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AccceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. +Allows you to specify a custom directory for your generated models. By default this settings has to be a virtual directory, that is, it must start with `~/`, if needed `AcceptUnsafeModelsDirectory` can be set to true, to allow the path to be outside the website root, be aware though that this is a potential security risk. {% hint style="info" %} If you want to generate models outside the web project you can change the ModelsDirectory path. Suppose you have a data project called My.Website.Data the ModelsDirectory path should be: From 58eec8b7cd77ebcdf2afc0dabff35ffe1b59ce68 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:07:37 +0100 Subject: [PATCH 34/42] spelling: diffent -> different --- 10/umbraco-cms/reference/configuration/README.md | 2 +- 13/umbraco-cms/reference/configuration/README.md | 2 +- 14/umbraco-cms/reference/configuration/README.md | 2 +- 15/umbraco-cms/reference/configuration/README.md | 2 +- 16/umbraco-cms/reference/configuration/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/README.md b/10/umbraco-cms/reference/configuration/README.md index ea832bab727..7f153d19c0e 100644 --- a/10/umbraco-cms/reference/configuration/README.md +++ b/10/umbraco-cms/reference/configuration/README.md @@ -5,7 +5,7 @@ description: Information on configuring Umbraco # Configuration -In Umbraco 9+, we have moved away from the previous configuration using `.config` files, to instead using the .NET built-in configuration pattern. This means that there is no longer separate files for different configuration, the configuration is now primarily done using `IConfiguration` with diffent sources. E.g. The `appsettings.json` file. +In Umbraco 9+, we have moved away from the previous configuration using `.config` files, to instead using the .NET built-in configuration pattern. This means that there is no longer separate files for different configuration, the configuration is now primarily done using `IConfiguration` with different sources. E.g. The `appsettings.json` file. For more in depth information on the configuration pattern see Microsofts [Configuration in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0) article. diff --git a/13/umbraco-cms/reference/configuration/README.md b/13/umbraco-cms/reference/configuration/README.md index afc52464e9a..28b8fd2abeb 100644 --- a/13/umbraco-cms/reference/configuration/README.md +++ b/13/umbraco-cms/reference/configuration/README.md @@ -4,7 +4,7 @@ description: Information on configuring Umbraco # Configuration -In Umbraco 9+, we have moved away from the previous configuration using `.config` files, to instead using the .NET built-in configuration pattern. This means that there is no longer separate files for different configuration, the configuration is now primarily done using `IConfiguration` with diffent sources. E.g. The `appsettings.json` file. +In Umbraco 9+, we have moved away from the previous configuration using `.config` files, to instead using the .NET built-in configuration pattern. This means that there is no longer separate files for different configuration, the configuration is now primarily done using `IConfiguration` with different sources. E.g. The `appsettings.json` file. For more in depth information on the configuration pattern see Microsofts [Configuration in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0) article. diff --git a/14/umbraco-cms/reference/configuration/README.md b/14/umbraco-cms/reference/configuration/README.md index b991990fe59..027d62fdaba 100644 --- a/14/umbraco-cms/reference/configuration/README.md +++ b/14/umbraco-cms/reference/configuration/README.md @@ -4,7 +4,7 @@ description: Information on configuring Umbraco # Configuration -Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with diffent sources. +Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with different sources. For more in depth information on the configuration pattern see Microsofts [Configuration in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0) article. diff --git a/15/umbraco-cms/reference/configuration/README.md b/15/umbraco-cms/reference/configuration/README.md index 1a2519913a2..cf3d673367c 100644 --- a/15/umbraco-cms/reference/configuration/README.md +++ b/15/umbraco-cms/reference/configuration/README.md @@ -4,7 +4,7 @@ description: Information on configuring Umbraco # Configuration -Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with diffent sources. +Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with different sources. For more in depth information on the configuration pattern see Microsofts [Configuration in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0) article. diff --git a/16/umbraco-cms/reference/configuration/README.md b/16/umbraco-cms/reference/configuration/README.md index 1a2519913a2..cf3d673367c 100644 --- a/16/umbraco-cms/reference/configuration/README.md +++ b/16/umbraco-cms/reference/configuration/README.md @@ -4,7 +4,7 @@ description: Information on configuring Umbraco # Configuration -Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with diffent sources. +Umbraco uses the .NET built-in configuration pattern. This means that the configuration is handled in the `appsettings.json` file and primarily done using `IConfiguration` with different sources. For more in depth information on the configuration pattern see Microsofts [Configuration in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-6.0) article. From 7126e36fce7831934367c10bc3a233e5c1c2a944 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:08:07 +0100 Subject: [PATCH 35/42] spelling: hierachy -> hierarchy --- 10/umbraco-cms/reference/configuration/README.md | 2 +- 13/umbraco-cms/reference/configuration/README.md | 2 +- 14/umbraco-cms/reference/configuration/README.md | 2 +- 15/umbraco-cms/reference/configuration/README.md | 2 +- 16/umbraco-cms/reference/configuration/README.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/README.md b/10/umbraco-cms/reference/configuration/README.md index 7f153d19c0e..cdd1cf8e0d6 100644 --- a/10/umbraco-cms/reference/configuration/README.md +++ b/10/umbraco-cms/reference/configuration/README.md @@ -27,7 +27,7 @@ There is one caveat, to this precedence though, the `appsettings.{environment}.j ### Using Environment Variables for Configuration -It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierachy. +It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierarchy. As an example, if you want to set your unattended username, you would normally write it in the `appsettings.json` like so: diff --git a/13/umbraco-cms/reference/configuration/README.md b/13/umbraco-cms/reference/configuration/README.md index 28b8fd2abeb..64ecc56ce7f 100644 --- a/13/umbraco-cms/reference/configuration/README.md +++ b/13/umbraco-cms/reference/configuration/README.md @@ -26,7 +26,7 @@ There is one caveat, to this precedence though, the `appsettings.{environment}.j ### Using Environment Variables for Configuration -It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierachy. +It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierarchy. As an example, if you want to set your unattended username, you would normally write it in the `appsettings.json` like so: diff --git a/14/umbraco-cms/reference/configuration/README.md b/14/umbraco-cms/reference/configuration/README.md index 027d62fdaba..80e05dd2f45 100644 --- a/14/umbraco-cms/reference/configuration/README.md +++ b/14/umbraco-cms/reference/configuration/README.md @@ -34,7 +34,7 @@ There is one caveat, to this precedence though, the `appsettings.{environment}.j ### Using Environment Variables for Configuration -It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierachy. +It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierarchy. As an example, if you want to set your unattended username, you would normally write it in the `appsettings.json` like so: diff --git a/15/umbraco-cms/reference/configuration/README.md b/15/umbraco-cms/reference/configuration/README.md index cf3d673367c..ca4f292b6d4 100644 --- a/15/umbraco-cms/reference/configuration/README.md +++ b/15/umbraco-cms/reference/configuration/README.md @@ -34,7 +34,7 @@ There is one caveat, to this precedence though, the `appsettings.{environment}.j ### Using Environment Variables for Configuration -It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierachy. +It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierarchy. As an example, if you want to set your unattended username, you would normally write it in the `appsettings.json` like so: diff --git a/16/umbraco-cms/reference/configuration/README.md b/16/umbraco-cms/reference/configuration/README.md index cf3d673367c..ca4f292b6d4 100644 --- a/16/umbraco-cms/reference/configuration/README.md +++ b/16/umbraco-cms/reference/configuration/README.md @@ -34,7 +34,7 @@ There is one caveat, to this precedence though, the `appsettings.{environment}.j ### Using Environment Variables for Configuration -It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierachy. +It is not feasible to have an entire json file as an environment variable, and the `:` doesn't work with environment variables on all platforms, so instead a double underscore is used to create the hierarchy. As an example, if you want to set your unattended username, you would normally write it in the `appsettings.json` like so: From d12b92c7ca14e17c75e252ad1bfbbe09ff6bcd82 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:08:39 +0100 Subject: [PATCH 36/42] spelling: backofffice -> backoffice --- 10/umbraco-cms/reference/configuration/webroutingsettings.md | 2 +- 13/umbraco-cms/reference/configuration/webroutingsettings.md | 2 +- 14/umbraco-cms/reference/configuration/webroutingsettings.md | 2 +- 15/umbraco-cms/reference/configuration/webroutingsettings.md | 2 +- 16/umbraco-cms/reference/configuration/webroutingsettings.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/configuration/webroutingsettings.md b/10/umbraco-cms/reference/configuration/webroutingsettings.md index e3e9d16642c..8e8bddb2fff 100644 --- a/10/umbraco-cms/reference/configuration/webroutingsettings.md +++ b/10/umbraco-cms/reference/configuration/webroutingsettings.md @@ -76,5 +76,5 @@ Will set the URL provider mode, options are: Defines the Umbraco application URL that the server should reach itself. By default, Umbraco will guess that URL from the first request made to the server. Use this setting if the guess is not correct (because you are behind a load-balancer, for example). Format is: `http://www.mysite.com/`, ensure to contain the scheme (http/https) and complete hostname. {% hint style="info" %} -Previously before v9, it was required to specify **backofffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. +Previously before v9, it was required to specify **backoffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. {% endhint %} diff --git a/13/umbraco-cms/reference/configuration/webroutingsettings.md b/13/umbraco-cms/reference/configuration/webroutingsettings.md index 77b01924975..c90520f3b2f 100644 --- a/13/umbraco-cms/reference/configuration/webroutingsettings.md +++ b/13/umbraco-cms/reference/configuration/webroutingsettings.md @@ -102,5 +102,5 @@ Will set the URL provider mode, options are: Defines the Umbraco application URL that the server should reach itself. By default, Umbraco will guess that URL from the first request made to the server. Use this setting if the guess is not correct (because you are behind a load-balancer, for example). Format is: `http://www.mysite.com/`, ensure to contain the scheme (http/https) and complete hostname. {% hint style="info" %} -Previously before v9, it was required to specify **backofffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. +Previously before v9, it was required to specify **backoffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. {% endhint %} diff --git a/14/umbraco-cms/reference/configuration/webroutingsettings.md b/14/umbraco-cms/reference/configuration/webroutingsettings.md index 77b01924975..c90520f3b2f 100644 --- a/14/umbraco-cms/reference/configuration/webroutingsettings.md +++ b/14/umbraco-cms/reference/configuration/webroutingsettings.md @@ -102,5 +102,5 @@ Will set the URL provider mode, options are: Defines the Umbraco application URL that the server should reach itself. By default, Umbraco will guess that URL from the first request made to the server. Use this setting if the guess is not correct (because you are behind a load-balancer, for example). Format is: `http://www.mysite.com/`, ensure to contain the scheme (http/https) and complete hostname. {% hint style="info" %} -Previously before v9, it was required to specify **backofffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. +Previously before v9, it was required to specify **backoffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. {% endhint %} diff --git a/15/umbraco-cms/reference/configuration/webroutingsettings.md b/15/umbraco-cms/reference/configuration/webroutingsettings.md index 77b01924975..c90520f3b2f 100644 --- a/15/umbraco-cms/reference/configuration/webroutingsettings.md +++ b/15/umbraco-cms/reference/configuration/webroutingsettings.md @@ -102,5 +102,5 @@ Will set the URL provider mode, options are: Defines the Umbraco application URL that the server should reach itself. By default, Umbraco will guess that URL from the first request made to the server. Use this setting if the guess is not correct (because you are behind a load-balancer, for example). Format is: `http://www.mysite.com/`, ensure to contain the scheme (http/https) and complete hostname. {% hint style="info" %} -Previously before v9, it was required to specify **backofffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. +Previously before v9, it was required to specify **backoffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. {% endhint %} diff --git a/16/umbraco-cms/reference/configuration/webroutingsettings.md b/16/umbraco-cms/reference/configuration/webroutingsettings.md index 7f0797cab90..2f154cf9319 100644 --- a/16/umbraco-cms/reference/configuration/webroutingsettings.md +++ b/16/umbraco-cms/reference/configuration/webroutingsettings.md @@ -103,7 +103,7 @@ Will set the URL provider mode, options are: Defines the Umbraco application URL that the server should reach itself. By default, Umbraco will guess that URL from the first request made to the server. Use this setting if the guess is not correct (because you are behind a load-balancer, for example). Format is: `http://www.mysite.com/`, ensure to contain the scheme (http/https) and complete hostname. {% hint style="info" %} -Previously before v9, it was required to specify **backofffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. +Previously before v9, it was required to specify **backoffice** path as this was customizable (`/umbraco` by default). However, from v9+ this is no longer possible, so it's sufficient to use the URL that contains the scheme (http/https) and complete hostname. {% endhint %} ## Strict domain matching From dd48b1b37a8d5496fac1ff92b7c5d195e5809356 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:10:03 +0100 Subject: [PATCH 37/42] spelling: currenty -> current --- 10/umbraco-cms/reference/management/services/relationservice.md | 2 +- 13/umbraco-cms/reference/management/services/relationservice.md | 2 +- .../reference/management/using-services/relationservice.md | 2 +- .../reference/management/using-services/relationservice.md | 2 +- .../reference/management/using-services/relationservice.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/management/services/relationservice.md b/10/umbraco-cms/reference/management/services/relationservice.md index 34e0cc0d27b..dfc4f89874e 100644 --- a/10/umbraco-cms/reference/management/services/relationservice.md +++ b/10/umbraco-cms/reference/management/services/relationservice.md @@ -348,7 +348,7 @@ namespace Doccers.Core.Components // Check if they are already related if (!_relationService.AreRelated(home.Id, entity.Id)) { - // If not then let us relate the currenty entity to home + // If not then let us relate the current entity to home _relationService.Relate(home.Id, entity.Id, relationType); } } diff --git a/13/umbraco-cms/reference/management/services/relationservice.md b/13/umbraco-cms/reference/management/services/relationservice.md index e08a1439be1..521fe154e9c 100644 --- a/13/umbraco-cms/reference/management/services/relationservice.md +++ b/13/umbraco-cms/reference/management/services/relationservice.md @@ -321,7 +321,7 @@ public class RelationComponent : IComponent // Check if they are already related if (!_relationService.AreRelated(home.Id, entity.Id)) { - // If not then let us relate the currenty entity to home + // If not then let us relate the current entity to home _relationService.Relate(home.Id, entity.Id, relationType); } } diff --git a/14/umbraco-cms/reference/management/using-services/relationservice.md b/14/umbraco-cms/reference/management/using-services/relationservice.md index 02ec6266931..6384ec73bf2 100644 --- a/14/umbraco-cms/reference/management/using-services/relationservice.md +++ b/14/umbraco-cms/reference/management/using-services/relationservice.md @@ -35,7 +35,7 @@ public class ContentPublishedNotificationHandler(IContentService contentService, // Check if they are already related if (!relationService.AreRelated(home.Id, entity.Id)) { - // If not then let us relate the currenty entity to home + // If not then let us relate the current entity to home relationService.Relate(home.Id, entity.Id, relationType); } } diff --git a/15/umbraco-cms/reference/management/using-services/relationservice.md b/15/umbraco-cms/reference/management/using-services/relationservice.md index bed26552c64..2dd45eb9dc6 100644 --- a/15/umbraco-cms/reference/management/using-services/relationservice.md +++ b/15/umbraco-cms/reference/management/using-services/relationservice.md @@ -35,7 +35,7 @@ public class ContentPublishedNotificationHandler(IContentService contentService, // Check if they are already related if (!relationService.AreRelated(home.Id, entity.Id)) { - // If not then let us relate the currenty entity to home + // If not then let us relate the current entity to home relationService.Relate(home.Id, entity.Id, relationType); } } diff --git a/16/umbraco-cms/reference/management/using-services/relationservice.md b/16/umbraco-cms/reference/management/using-services/relationservice.md index bed26552c64..2dd45eb9dc6 100644 --- a/16/umbraco-cms/reference/management/using-services/relationservice.md +++ b/16/umbraco-cms/reference/management/using-services/relationservice.md @@ -35,7 +35,7 @@ public class ContentPublishedNotificationHandler(IContentService contentService, // Check if they are already related if (!relationService.AreRelated(home.Id, entity.Id)) { - // If not then let us relate the currenty entity to home + // If not then let us relate the current entity to home relationService.Relate(home.Id, entity.Id, relationType); } } From 80c16bec7978a2560f2963c8c26db1c7ce5cdac5 Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:11:08 +0100 Subject: [PATCH 38/42] spelling: refeshedContent -> refreshedContent --- .../reference/notifications/cacherefresher-notifications.md | 2 +- .../reference/notifications/cacherefresher-notifications.md | 2 +- .../reference/notifications/cacherefresher-notifications.md | 2 +- .../reference/notifications/cacherefresher-notifications.md | 2 +- .../reference/notifications/cacherefresher-notifications.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/notifications/cacherefresher-notifications.md b/10/umbraco-cms/reference/notifications/cacherefresher-notifications.md index 915e7fca320..111b2493d2b 100644 --- a/10/umbraco-cms/reference/notifications/cacherefresher-notifications.md +++ b/10/umbraco-cms/reference/notifications/cacherefresher-notifications.md @@ -103,7 +103,7 @@ public class ContentCacheRefresherExample : INotificationHandler Date: Mon, 1 Sep 2025 11:11:42 +0100 Subject: [PATCH 39/42] spelling: ICotnent -> IContent --- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/10/umbraco-cms/reference/notifications/contentservice-notifications.md b/10/umbraco-cms/reference/notifications/contentservice-notifications.md index 74342929c15..dd8f896f96b 100644 --- a/10/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/10/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -161,7 +161,7 @@ In the Published notification you can similarly use the HasPublishedCulture and ```csharp public bool HasPublishedCulture(IContent content, string culture); -public bool HasUnpublishedCulture(ICotnent content, string culture); +public bool HasUnpublishedCulture(IContent content, string culture); ``` #### IContent Helpers diff --git a/13/umbraco-cms/reference/notifications/contentservice-notifications.md b/13/umbraco-cms/reference/notifications/contentservice-notifications.md index 2f33e84fd36..9c24799a3b7 100644 --- a/13/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/13/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -156,7 +156,7 @@ In the Published notification you can similarly use the HasPublishedCulture and ```csharp public bool HasPublishedCulture(IContent content, string culture); -public bool HasUnpublishedCulture(ICotnent content, string culture); +public bool HasUnpublishedCulture(IContent content, string culture); ``` #### IContent Helpers diff --git a/14/umbraco-cms/reference/notifications/contentservice-notifications.md b/14/umbraco-cms/reference/notifications/contentservice-notifications.md index 2f33e84fd36..9c24799a3b7 100644 --- a/14/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/14/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -156,7 +156,7 @@ In the Published notification you can similarly use the HasPublishedCulture and ```csharp public bool HasPublishedCulture(IContent content, string culture); -public bool HasUnpublishedCulture(ICotnent content, string culture); +public bool HasUnpublishedCulture(IContent content, string culture); ``` #### IContent Helpers diff --git a/15/umbraco-cms/reference/notifications/contentservice-notifications.md b/15/umbraco-cms/reference/notifications/contentservice-notifications.md index b96e433fe7f..2a0378fe9e0 100644 --- a/15/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/15/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -156,7 +156,7 @@ In the Published notification you can similarly use the HasPublishedCulture and ```csharp public bool HasPublishedCulture(IContent content, string culture); -public bool HasUnpublishedCulture(ICotnent content, string culture); +public bool HasUnpublishedCulture(IContent content, string culture); ``` #### IContent Helpers diff --git a/16/umbraco-cms/reference/notifications/contentservice-notifications.md b/16/umbraco-cms/reference/notifications/contentservice-notifications.md index b96e433fe7f..2a0378fe9e0 100644 --- a/16/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/16/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -156,7 +156,7 @@ In the Published notification you can similarly use the HasPublishedCulture and ```csharp public bool HasPublishedCulture(IContent content, string culture); -public bool HasUnpublishedCulture(ICotnent content, string culture); +public bool HasUnpublishedCulture(IContent content, string culture); ``` #### IContent Helpers From f1379c635b0c29306e23bc8978dc66c56e69c92d Mon Sep 17 00:00:00 2001 From: LLaverty Date: Mon, 1 Sep 2025 11:12:16 +0100 Subject: [PATCH 40/42] spelling: hould -> should --- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/mediaservice-notifications.md | 2 +- .../reference/notifications/memberservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/mediaservice-notifications.md | 2 +- .../reference/notifications/memberservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/mediaservice-notifications.md | 2 +- .../reference/notifications/memberservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/mediaservice-notifications.md | 2 +- .../reference/notifications/memberservice-notifications.md | 2 +- .../reference/notifications/contentservice-notifications.md | 2 +- .../reference/notifications/mediaservice-notifications.md | 2 +- .../reference/notifications/memberservice-notifications.md | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) diff --git a/10/umbraco-cms/reference/notifications/contentservice-notifications.md b/10/umbraco-cms/reference/notifications/contentservice-notifications.md index dd8f896f96b..11b45d27b0e 100644 --- a/10/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/10/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -222,7 +222,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/10/umbraco-cms/reference/notifications/mediaservice-notifications.md b/10/umbraco-cms/reference/notifications/mediaservice-notifications.md index b22ab66c4b5..91624753816 100644 --- a/10/umbraco-cms/reference/notifications/mediaservice-notifications.md +++ b/10/umbraco-cms/reference/notifications/mediaservice-notifications.md @@ -128,7 +128,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/10/umbraco-cms/reference/notifications/memberservice-notifications.md b/10/umbraco-cms/reference/notifications/memberservice-notifications.md index f859042e4b5..29bbf40c02a 100644 --- a/10/umbraco-cms/reference/notifications/memberservice-notifications.md +++ b/10/umbraco-cms/reference/notifications/memberservice-notifications.md @@ -70,7 +70,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/13/umbraco-cms/reference/notifications/contentservice-notifications.md b/13/umbraco-cms/reference/notifications/contentservice-notifications.md index 9c24799a3b7..c429a44cd2e 100644 --- a/13/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/13/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -217,7 +217,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/13/umbraco-cms/reference/notifications/mediaservice-notifications.md b/13/umbraco-cms/reference/notifications/mediaservice-notifications.md index 1c75258e98c..f58ca3db7cd 100644 --- a/13/umbraco-cms/reference/notifications/mediaservice-notifications.md +++ b/13/umbraco-cms/reference/notifications/mediaservice-notifications.md @@ -128,7 +128,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/13/umbraco-cms/reference/notifications/memberservice-notifications.md b/13/umbraco-cms/reference/notifications/memberservice-notifications.md index 32eae8d9037..0bc482005a5 100644 --- a/13/umbraco-cms/reference/notifications/memberservice-notifications.md +++ b/13/umbraco-cms/reference/notifications/memberservice-notifications.md @@ -69,7 +69,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/14/umbraco-cms/reference/notifications/contentservice-notifications.md b/14/umbraco-cms/reference/notifications/contentservice-notifications.md index 9c24799a3b7..c429a44cd2e 100644 --- a/14/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/14/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -217,7 +217,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/14/umbraco-cms/reference/notifications/mediaservice-notifications.md b/14/umbraco-cms/reference/notifications/mediaservice-notifications.md index 1c75258e98c..f58ca3db7cd 100644 --- a/14/umbraco-cms/reference/notifications/mediaservice-notifications.md +++ b/14/umbraco-cms/reference/notifications/mediaservice-notifications.md @@ -128,7 +128,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/14/umbraco-cms/reference/notifications/memberservice-notifications.md b/14/umbraco-cms/reference/notifications/memberservice-notifications.md index 32eae8d9037..0bc482005a5 100644 --- a/14/umbraco-cms/reference/notifications/memberservice-notifications.md +++ b/14/umbraco-cms/reference/notifications/memberservice-notifications.md @@ -69,7 +69,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by NuCache to populate the cmsContentNu table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the NuCache and examine data manually. diff --git a/15/umbraco-cms/reference/notifications/contentservice-notifications.md b/15/umbraco-cms/reference/notifications/contentservice-notifications.md index 2a0378fe9e0..0c9613c5cde 100644 --- a/15/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/15/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -217,7 +217,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. diff --git a/15/umbraco-cms/reference/notifications/mediaservice-notifications.md b/15/umbraco-cms/reference/notifications/mediaservice-notifications.md index c2a9f884b25..0f17c472187 100644 --- a/15/umbraco-cms/reference/notifications/mediaservice-notifications.md +++ b/15/umbraco-cms/reference/notifications/mediaservice-notifications.md @@ -127,7 +127,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. diff --git a/15/umbraco-cms/reference/notifications/memberservice-notifications.md b/15/umbraco-cms/reference/notifications/memberservice-notifications.md index a1f5f1a87ec..58042f84791 100644 --- a/15/umbraco-cms/reference/notifications/memberservice-notifications.md +++ b/15/umbraco-cms/reference/notifications/memberservice-notifications.md @@ -69,7 +69,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. diff --git a/16/umbraco-cms/reference/notifications/contentservice-notifications.md b/16/umbraco-cms/reference/notifications/contentservice-notifications.md index 2a0378fe9e0..0c9613c5cde 100644 --- a/16/umbraco-cms/reference/notifications/contentservice-notifications.md +++ b/16/umbraco-cms/reference/notifications/contentservice-notifications.md @@ -217,7 +217,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. diff --git a/16/umbraco-cms/reference/notifications/mediaservice-notifications.md b/16/umbraco-cms/reference/notifications/mediaservice-notifications.md index 20baee0604e..d9969619f70 100644 --- a/16/umbraco-cms/reference/notifications/mediaservice-notifications.md +++ b/16/umbraco-cms/reference/notifications/mediaservice-notifications.md @@ -128,7 +128,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. diff --git a/16/umbraco-cms/reference/notifications/memberservice-notifications.md b/16/umbraco-cms/reference/notifications/memberservice-notifications.md index a1f5f1a87ec..58042f84791 100644 --- a/16/umbraco-cms/reference/notifications/memberservice-notifications.md +++ b/16/umbraco-cms/reference/notifications/memberservice-notifications.md @@ -69,7 +69,7 @@ Child scope will inherit the parent Scope's notification object which means if a **Why would one want to suppress events?** -The main reason for ever doing this would be performance for bulk operations. The callers hould be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. +The main reason for ever doing this would be performance for bulk operations. The callers should be aware that suppressing events will lead to an inconsistent content cache state (if notifications are suppressed for content or media services). This is because notifications are used by the Published Content Cache to populate the `cmsContentNu` table and populate the content caches. They are also used to populate the Examine indexes. So if you did suppress events, it will require you to rebuild the Published Content Cache and examine data manually. From 2ab0cc19ecf4e7fd3b4a88bcd01b75538a7cde4f Mon Sep 17 00:00:00 2001 From: Liam Laverty Date: Mon, 1 Sep 2025 13:21:17 +0100 Subject: [PATCH 41/42] Update 15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md Co-authored-by: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> --- .../extending-overview/extension-types/header-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md b/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md index 7c8b4f94ab8..117c6dafac2 100644 --- a/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md +++ b/15/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md @@ -51,7 +51,7 @@ Below you can find an example of how to setup a Header App using the manifest fi * First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI. * Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button. -* The button requires some : an icon, label of the button (name of the button) and a link which opens once clicked. +* The button requires some metadata: an icon, label of the button (name of the button) and a link which opens once clicked. 4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**: From e8bd8dd0bca936b021376444a80da558191f7c5e Mon Sep 17 00:00:00 2001 From: Liam Laverty Date: Mon, 1 Sep 2025 13:21:26 +0100 Subject: [PATCH 42/42] Update 16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md Co-authored-by: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> --- .../extending-overview/extension-types/header-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md b/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md index 7c8b4f94ab8..117c6dafac2 100644 --- a/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md +++ b/16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md @@ -51,7 +51,7 @@ Below you can find an example of how to setup a Header App using the manifest fi * First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI. * Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button. -* The button requires some : an icon, label of the button (name of the button) and a link which opens once clicked. +* The button requires some metadata: an icon, label of the button (name of the button) and a link which opens once clicked. 4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**: