diff --git a/docs/documentation_create_page.md b/docs/documentation_create_page.md
index 929e005e..3f7e4c09 100644
--- a/docs/documentation_create_page.md
+++ b/docs/documentation_create_page.md
@@ -89,7 +89,7 @@ required: inclusive       #=> Inclusive
 required: exclusive       #=> Exclusive
 required: any string here #=> Any string here
 ```
-- **`type:`**: The type of the variable. Allowed entries: `boolean`, `string`, `integer`, `time`, `template` or `map`/`list` (for a list of entries). For multiple possibilities use `[string, integer]`. If you use `map`/`list` then you need to define `keys:` (see the [`template` sensor](https://www.home-assistant.io/components/sensor.template/) for an example).
+- **`type:`**: The type of the variable. Allowed entries: `boolean`, `string`, `integer`, `time`, `template`, `device_class`, `icon` or `map`/`list` (for a list of entries). For multiple possibilities use `[string, integer]`. If you use `map`/`list` then you need to define `keys:` (see the [`template` sensor](https://www.home-assistant.io/components/sensor.template/) for an example).
 - **`default:`**: The default value for the variable.
 
 ### Embedding Code
diff --git a/docs/documentation_standards.md b/docs/documentation_standards.md
index e5ac95d9..fe5bfb39 100644
--- a/docs/documentation_standards.md
+++ b/docs/documentation_standards.md
@@ -19,7 +19,7 @@ To ensure that the documentation for Home Assistant is consistent and easy to fo
 * The **Configuration Variables** section must use the `{% configuration %}` tag.
 * Configuration variables must document the requirement status (`false` or `true`)
 * Configuration variables must document the default value, if any.
-* Configuration variables must document the accepted value types (`string`, `boolean`, `integer`, `list`)
+* Configuration variables must document the accepted value types (see [Configuration variables details](documentation_create_page.md#configuration))
   * For configuration variables that accept multiple types, separate the types with a comma (i.e. `string, int`).
 * Use YAML sequence syntax in the sample code if it is supported.
 * All examples should be formatted to be included in `configuration.yaml` unless explicitly stated.