Cleaned up config docs for V14

14/umbraco-cms/SUMMARY.md

@@ -249,7 +249,6 @@
   * [Imaging settings](reference/configuration/imagingsettings.md)
   * [Indexing settings](reference/configuration/indexingsettings.md)
   * [Install Default Data Settings](reference/configuration/installdefaultdatasettings.md)
-  * [Keep alive settings](reference/configuration/keepalivesettings.md)
   * [Logging settings](reference/configuration/loggingsettings.md)
   * [Maximum Upload Size Settings](reference/configuration/maximumuploadsizesettings.md)
   * [Models builder settings](reference/configuration/modelsbuildersettings.md)
@@ -260,7 +259,6 @@
   * [Runtime settings](reference/configuration/runtimesettings.md)
   * [Security Settings](reference/configuration/securitysettings.md)
   * [Serilog settings](reference/configuration/serilog.md)
-  * [Tours settings](reference/configuration/tourssettings.md)
   * [Type finder settings](reference/configuration/typefindersettings.md)
   * [Unattended](reference/configuration/unattendedsettings.md)
   * [Web routing](reference/configuration/webroutingsettings.md)

14/umbraco-cms/fundamentals/setup/server-setup/load-balancing/README.md

@@ -58,9 +58,8 @@ The process is as follows:
 
 ## Scheduling and server role election
 
-Although there is a backoffice server designated for administration, by default this is not explicitly set as the "Scheduling server". In Umbraco there can only be a single scheduling server which performs the following 3 things:
+Although there is a backoffice server designated for administration, by default this is not explicitly set as the "Scheduling server". In Umbraco there can only be a single scheduling server which performs the following tasks:
 
-* Keep alive service - to ensure scheduled publishing occurs
 * Scheduled tasks - to initiate any configured scheduled tasks
 * Scheduled publishing - to initiate any scheduled publishing for documents
 

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

@@ -119,7 +119,6 @@ A complete list of all the configuration sections included in Umbraco, by defaul
 * [Imaging settings](imagingsettings.md)
 * [Indexing settings](indexingsettings.md)
 * [Install default data setting](installdefaultdatasettings.md)
-* [Keep alive settings](keepalivesettings.md)
 * [Logging settings](loggingsettings.md)
 * [Maximum upload size settings](maximumuploadsizesettings.md)
 * [Models builder settings](modelsbuildersettings.md)
@@ -130,7 +129,6 @@ A complete list of all the configuration sections included in Umbraco, by defaul
 * [Runtime settings](runtimesettings.md)
 * [Security settings](securitysettings.md)
 * [Serilog settings](serilog.md)
-* [Tours settings](tourssettings.md)
 * [Type finder settings](typefindersettings.md)
 * [Unattended settings](unattendedsettings.md)
 * [Web routing settings](webroutingsettings.md)

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

@@ -39,8 +39,9 @@ The following snippet will give an overview of the keys and values in the conten
           }
         ]
       },
-      "LoginBackgroundImage": "assets/img/login.jpg",
-      "LoginLogoImage": "assets/img/application/umbraco_logo_white.svg",
+      "LoginBackgroundImage": "login/login.jpg",
+      "LoginLogoImage": "login/logo_light.svg",
+      "LoginLogoImageAlternative": "login/logo_dark.svg",
       "Notifications": {
         "DisableHtmlEmail": false,
         "Email": null
@@ -133,11 +134,15 @@ This setting can be used to hide the Umbraco logo in backoffice.
 
 ### Login background image
 
-You can specify your own background image for the login screen here. The image will automatically get an overlay to match backoffice colors. This path is relative to the `wwwroot/umbraco` path. The default location is: `wwwroot/umbraco/assets/img/installer.jpg`.
+You can specify your own background image for the login screen here. The image will automatically get an overlay to match backoffice colors. This path is relative to the `wwwroot/umbraco` path. The default location is: `wwwroot/umbraco/login/login.jpg`.
 
 ### Login logo image
 
-You can specify your own image for the small logo in the top left corner of the login screen. This path is relative to the `wwwroot/umbraco` path. The default location is: `wwwroot/umbraco/assets/img/application/umbraco_logo_white.svg`.
+You can specify your own image for the small logo in the top left corner of the login screen. This path is relative to the `wwwroot/umbraco` path. The default location is: `wwwroot/umbraco/login/logo_light.svg`.
+
+### Login logo image (alternative)
+
+You can specify your own alternative image for the small logo in the top left corner of the login screen. The alternative image is shown on light backgrounds (for example for mobile resolutions). This path is relative to the `wwwroot/umbraco` path. The default location is: `wwwroot/umbraco/login/logo_dark.svg`.
 
 ### Preview badge
 

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

@@ -31,7 +31,6 @@ The following snippet contains all the available options, with default values, a
       "MainDomKeyDiscriminator": "",
       "Id": "184a8175-bc0b-43dd-8267-d99871eaec3d",
       "NoNodesViewPath": "~/umbraco/UmbracoWebsite/NoNodes.cshtml",
-      "SanitizeTinyMce": false,
       "Smtp": {
         "From": "person@umbraco.dk",
         "Host": "localhost",
@@ -254,12 +253,6 @@ Sets a value for the time to wait between each sync operation.
 
 Sets a value for the time to wait between each prune operation.
 
-### Sanitize TinyMce
-
-Gets or sets a value indicating whether TinyMCE scripting sanitization should be applied.
-
-The default value is `false`.
-
 ### Distributed Locking Mechanism
 
 This is not a setting that commonly needs to be configured.

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

@@ -4,7 +4,11 @@ description: "Information on the runtime settings section"
 
 # Runtime settings
 
-Runtime settings allows you to configure the `MaxRequestLength` and `MaxQueryStringLength` for your application. Neither of these settings needs to be configured. If nothing is configured reqests and query string can be any size.
+In the Runtime settings you can configure:
+
+- Size limits for requests and query strings. Neither of these settings needs to be configured. If nothing is configured, requests and query strings can be any size.
+- The runtime mode of Umbraco.
+- The lifetime of temporary file uploads. This is primarily used when uploading images and other media in the backoffice.
 
 An example of a configuration could look something like:
 
@@ -14,14 +18,14 @@ An example of a configuration could look something like:
     "Runtime": {
       "MaxQueryStringLength": 90,
       "MaxRequestLength": 2048,
-      "Mode": "BackofficeDevelopment"
+      "Mode": "BackofficeDevelopment",
+      "TemporaryFileLifeTime": "1.00:00:00"
     }
   }
 }
 ```
 
-`MaxRequestLength` is specified in kilobytes, limiting requests, and therefore uploaded files, to 2 megabytes. Additionally, it sets a maximum query string length of 90 characters.
-
-`Mode` can have three values: `BackofficeDevelopment` (default), `Development`, and `Production`.
-
-For more information, see the [Runtime modes](../../fundamentals/setup/server-setup/runtime-modes.md) article.
+- `MaxRequestLength` is specified in kilobytes. Setting this limits the request size, including the size of uploaded files.
+- `MaxQueryStringLength` is specified in number of characters. Setting this limits the maximum query string length.
+- `Mode` can have three values: `BackofficeDevelopment` (default), `Development`, and `Production`. For more information, see the [Runtime modes](../../fundamentals/setup/server-setup/runtime-modes.md) article.
+- `TemporaryFileLifeTime` is specified as a timespan. The default value is one day - `1.00:00:00`.

14/umbraco-cms/reference/security/ssl-https.md

@@ -36,8 +36,8 @@ In Umbraco 9, set the UseHttps key in `appSettings` to true.
 This options does multiple things when it is turned on:
 
 * Ensures that the backoffice authentication cookie is set to [secure only](https://owasp.org/www-community/controls/SecureCookieAttribute) (so it can only be transmitted over https)
-* All non-https requests to any backoffice controller is redirected to https
-* All self delivered Umbraco requests (those are scheduled publishing, keep alive, etc...) are performed over https
+* All non-https requests to any backoffice controller are redirected to https
+* All self delivered Umbraco requests are performed over https
 * All Umbraco notification emails with links generated have https links
 * All authorization attempts for backoffice handlers and services will be denied if the request is not over https