Merge pull request #7586 from umbraco/merge-v16-changes-to-v17

Cherry picked v16 updates

Author: eshanrnh

13/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -57,7 +57,7 @@ In the constructor, or via overridden properties, we can specify details of the
 - `Name` - the name of the field presented in the backoffice.
 - `Description` - the description of the field presented in the backoffice.
 - `Icon` - the icon of the field presented in the backoffice form builder user interface.
-- `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DataTime` or `Bit` (boolean).
+- `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DateTime` or `Bit` (boolean).
 - `SupportsMandatory` - indicates whether mandatory validation can be used with the field (defaults to `true`).
 - `MandatoryByDefault` - indicates whether the field will be mandatory by default when added to a form (defaults to `false`).
 - `SupportsRegex` - indicates whether pattern based validation using regular expressions can be used with the field (defaults to `false`).

15/umbraco-deploy/installation/install-configure.md

@@ -240,7 +240,7 @@ The setting under _Project:CurrentWorkspaceName_ should match the _Name_ provide
 In Umbraco Deploy 9, this value was set using the configuration key _Debug:EnvironmentName_. Although included under a "Debug" section, this setting is required for the installations of Umbraco Deploy on-premises (i.e. other than on Umbraco Cloud). Hence why it was moved to the "Project" section in Umbraco Deploy 10.
 {% endhint %}
 
-Expected values for _Type_ are "development", "staging" or "live". These settings are required, though strictly only for the latter is it necessary to use the specific value of "live", so other values can be used if you have more than these three environments.
+Expected values for _Type_ are "development", "staging", or "live". These settings are required, though only the `live` environment strictly requires the specific value `live`. You can use other values if you have more than these three environments. All values for _Type_ must be written in lowercase.
 
 You will need to generate a unique GUID for each environment. This can be done in Visual Studio:
 

15/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -60,7 +60,7 @@ In the constructor or via overridden properties, we can specify details of the f
 * `Name` - the name of the field presented in the backoffice.
 * `Description` - the description of the field presented in the backoffice.
 * `Icon` - the icon of the field presented in the backoffice form builder user interface.
-* `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DataTime` or `Bit` (boolean).
+* `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DateTime` or `Bit` (boolean).
 * `SupportsMandatory` - indicates whether mandatory validation can be used with the field (defaults to `true`).
 * `MandatoryByDefault` - indicates whether the field will be mandatory by default when added to a form (defaults to `false`).
 * `SupportsRegex` - indicates whether pattern-based validation using regular expressions can be used with the field (defaults to `false`).

17/umbraco-deploy/installation/install-configure.md

@@ -240,7 +240,7 @@ The setting under _Project:CurrentWorkspaceName_ should match the _Name_ provide
 In Umbraco Deploy 9, this value was set using the configuration key _Debug:EnvironmentName_. Although included under a "Debug" section, this setting is required for the installations of Umbraco Deploy on-premises (other than on Umbraco Cloud). Hence why it was moved to the "Project" section in Umbraco Deploy 10.
 {% endhint %}
 
-Expected values for _Type_ are "development", "staging" or "live". These settings are required, though strictly only for the latter is it necessary to use the specific value of "live", so other values can be used if you have more than these three environments.
+Expected values for _Type_ are "development", "staging", or "live". These settings are required, though only the `live` environment strictly requires the specific value `live`. You can use other values if you have more than these three environments. All values for _Type_ must be written in lowercase.
 
 You will need to generate a unique GUID for each environment. This can be done in Visual Studio:
 

17/umbraco-forms/developer/extending/adding-a-fieldtype.md

@@ -60,7 +60,7 @@ In the constructor or via overridden properties, we can specify details of the f
 * `Name` - the name of the field presented in the backoffice.
 * `Description` - the description of the field presented in the backoffice.
 * `Icon` - the icon of the field presented in the backoffice form builder user interface.
-* `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DataTime` or `Bit` (boolean).
+* `DataType` - specifies the type of data stored by the field. Options are `String`, `LongString`, `Integer`, `DateTime` or `Bit` (boolean).
 * `SupportsMandatory` - indicates whether mandatory validation can be used with the field (defaults to `true`).
 * `MandatoryByDefault` - indicates whether the field will be mandatory by default when added to a form (defaults to `false`).
 * `SupportsRegex` - indicates whether pattern-based validation using regular expressions can be used with the field (defaults to `false`).