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/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/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/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/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/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/10/umbraco-cms/reference/configuration/README.md b/10/umbraco-cms/reference/configuration/README.md index ea832bab727..cdd1cf8e0d6 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. @@ -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/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/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/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/10/umbraco-cms/reference/configuration/filesystemproviders.md b/10/umbraco-cms/reference/configuration/filesystemproviders.md index 6c340caf689..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 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 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/10/umbraco-cms/reference/configuration/globalsettings.md b/10/umbraco-cms/reference/configuration/globalsettings.md index a9a921ec87f..3ef6dce71e6 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 @@ -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/10/umbraco-cms/reference/configuration/healthchecks.md b/10/umbraco-cms/reference/configuration/healthchecks.md index ff271dd3dc9..110894119ae 100644 --- a/10/umbraco-cms/reference/configuration/healthchecks.md +++ b/10/umbraco-cms/reference/configuration/healthchecks.md @@ -48,9 +48,9 @@ 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. +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/10/umbraco-cms/reference/configuration/modelsbuildersettings.md b/10/umbraco-cms/reference/configuration/modelsbuildersettings.md index 938eabb1539..fd868a324de 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. @@ -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/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/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/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/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 **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/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/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/13/umbraco-cms/reference/configuration/README.md b/13/umbraco-cms/reference/configuration/README.md index afc52464e9a..64ecc56ce7f 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. @@ -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/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/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/13/umbraco-cms/reference/configuration/filesystemproviders.md b/13/umbraco-cms/reference/configuration/filesystemproviders.md index 523410fe4c4..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 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 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/globalsettings.md b/13/umbraco-cms/reference/configuration/globalsettings.md index b825d7fc624..00c8c0fbc32 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 @@ -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/13/umbraco-cms/reference/configuration/healthchecks.md b/13/umbraco-cms/reference/configuration/healthchecks.md index 8c60d712be9..308334c9242 100644 --- a/13/umbraco-cms/reference/configuration/healthchecks.md +++ b/13/umbraco-cms/reference/configuration/healthchecks.md @@ -45,9 +45,9 @@ 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. +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/modelsbuildersettings.md b/13/umbraco-cms/reference/configuration/modelsbuildersettings.md index 6de288f2375..b2d3c8275a6 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. @@ -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/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-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/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/13/umbraco-cms/reference/notifications/cacherefresher-notifications.md b/13/umbraco-cms/reference/notifications/cacherefresher-notifications.md index da54f65f7a6..2e4920f4cba 100644 --- a/13/umbraco-cms/reference/notifications/cacherefresher-notifications.md +++ b/13/umbraco-cms/reference/notifications/cacherefresher-notifications.md @@ -103,7 +103,7 @@ public class ContentCacheRefresherExample : INotificationHandler -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) @@ -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 possible for you to only configure the Element via properties of the Manifest. 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/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..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 metdata: 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**: 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/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/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/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/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/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/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/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/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/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/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/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/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/15/umbraco-cms/reference/configuration/README.md b/15/umbraco-cms/reference/configuration/README.md index 1a2519913a2..ca4f292b6d4 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. @@ -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/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/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/15/umbraco-cms/reference/configuration/filesystemproviders.md b/15/umbraco-cms/reference/configuration/filesystemproviders.md index 0bac9982caa..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 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 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/globalsettings.md b/15/umbraco-cms/reference/configuration/globalsettings.md index 378016df0f6..5409f19f687 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 @@ -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/15/umbraco-cms/reference/configuration/healthchecks.md b/15/umbraco-cms/reference/configuration/healthchecks.md index d41e9c5991c..814fe593c8c 100644 --- a/15/umbraco-cms/reference/configuration/healthchecks.md +++ b/15/umbraco-cms/reference/configuration/healthchecks.md @@ -45,9 +45,9 @@ 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. +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/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/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/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/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/15/umbraco-cms/reference/notifications/cacherefresher-notifications.md b/15/umbraco-cms/reference/notifications/cacherefresher-notifications.md index da54f65f7a6..2e4920f4cba 100644 --- a/15/umbraco-cms/reference/notifications/cacherefresher-notifications.md +++ b/15/umbraco-cms/reference/notifications/cacherefresher-notifications.md @@ -103,7 +103,7 @@ public class ContentCacheRefresherExample : INotificationHandler- 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 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 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..58d4360855a 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) @@ -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 possible for you to only configure the Element via properties of the Manifest. 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. 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..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 metdata: 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**: 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 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 } } 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.") } }); ``` 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. diff --git a/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md b/16/umbraco-cms/customizing/foundation/umbraco-controller/README.md index 910e8cd3487..9d06e2753d2 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 = () => { @@ -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 { 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) 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: { 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/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); }); 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. 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. 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. 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**. 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) 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) 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 diff --git a/16/umbraco-cms/reference/configuration/README.md b/16/umbraco-cms/reference/configuration/README.md index 1a2519913a2..ca4f292b6d4 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. @@ -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/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. 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": { diff --git a/16/umbraco-cms/reference/configuration/filesystemproviders.md b/16/umbraco-cms/reference/configuration/filesystemproviders.md index 0bac9982caa..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 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 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/globalsettings.md b/16/umbraco-cms/reference/configuration/globalsettings.md index 378016df0f6..5409f19f687 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 @@ -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/healthchecks.md b/16/umbraco-cms/reference/configuration/healthchecks.md index d41e9c5991c..814fe593c8c 100644 --- a/16/umbraco-cms/reference/configuration/healthchecks.md +++ b/16/umbraco-cms/reference/configuration/healthchecks.md @@ -45,9 +45,9 @@ 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. +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/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: 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 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/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); } } diff --git a/16/umbraco-cms/reference/notifications/cacherefresher-notifications.md b/16/umbraco-cms/reference/notifications/cacherefresher-notifications.md index da54f65f7a6..2e4920f4cba 100644 --- a/16/umbraco-cms/reference/notifications/cacherefresher-notifications.md +++ b/16/umbraco-cms/reference/notifications/cacherefresher-notifications.md @@ -103,7 +103,7 @@ public class ContentCacheRefresherExample : INotificationHandler