spelling: seperate -> separate

Author: liamlaverty

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
 

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
 

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
 

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

@@ -397,7 +397,7 @@ namespace RoutingDocs.SiteDomainMapper
 
 ### Default SiteDomainMapper
 
-Umbraco ships with a default `SiteDomainMapper`. This has some useful functionality for grouping sets of domains together. With Umbraco Cloud, or another Umbraco development environment scenario, there maybe be multiple domains setup for a site 'live, 'staging', 'testing' or a seperate domain to access the backoffice. Each domain will be setup as a 'Culture and Hostname' inside Umbraco. By default editors will see the full list of possible Urls for each of their content items on each domain, which can be confusing. If the additional urls aren't present in Culture and Hostnames, then when testing the front-end of the site on a 'staging' url, will result in navigation links taking you to the registered domain!
+Umbraco ships with a default `SiteDomainMapper`. This has some useful functionality for grouping sets of domains together. With Umbraco Cloud, or another Umbraco development environment scenario, there maybe be multiple domains setup for a site 'live, 'staging', 'testing' or a separate domain to access the backoffice. Each domain will be setup as a 'Culture and Hostname' inside Umbraco. By default editors will see the full list of possible Urls for each of their content items on each domain, which can be confusing. If the additional urls aren't present in Culture and Hostnames, then when testing the front-end of the site on a 'staging' url, will result in navigation links taking you to the registered domain!
 
 ![Culture and Hostnames multiple domains](images/culture-and-hostnames-v8.png)
 

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
 

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.
 

13/umbraco-commerce/reference/storefront-api/README.md

@@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9
 }
 ```
 
-The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`.
+The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`.
 
 ```http
 GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod
@@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9
 
 When using the `fields` query parameter to limit fields returned, `id` properties will always be included.
 
-Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax.
+Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax.
 
 **Request**
 

14/umbraco-cms/reference/configuration/globalsettings.md

@@ -61,14 +61,14 @@ The following snippet contains all the available options, with default values, a
 
 ## Root level settings 
 
-In the root level section, that is those without a seperate sub section like SMTP, you can configure
+In the root level section, that is those without a separate sub section like SMTP, you can configure
 
 ### Reserved urls
 
 Key: `ReservedUrls`  
 Type: `string` (default: `~/.well-known,`)
 
-A comma-seperated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered.
+A comma-separated list of files to be left alone by Umbraco, these files will be served, and the Umbraco request pipeline will not be triggered.
 
 ### Reserved paths
 

14/umbraco-commerce/reference/storefront-api/README.md

@@ -154,7 +154,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9
 }
 ```
 
-The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`.
+The `expand` query parameter can accept a comma separated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`.
 
 ```http
 GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod
@@ -462,7 +462,7 @@ GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9
 
 When using the `fields` query parameter to limit fields returned, `id` properties will always be included.
 
-Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma seperate values and the `[...]` syntax.
+Inline with the expansion feature, the `fields` paramter can also retrieve multiple fields, and nested fields using comma separate values and the `[...]` syntax.
 
 **Request**
 

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