diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index a6f75627763..d1b448b7875 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -182,17 +182,17 @@ Listing above and below together means the numeric_state has to be between the t
 In the example above, the trigger would fire a single time if a numeric_state goes into the 17.1-24.9 range (from 17 and below or 25 and above). It will only fire again, once it has left the defined range and enters it again.
 </div>
 
-Number helpers (`input_number` entities) can be used in the `above` and `below` thresholds, making
-the trigger more dynamic, like:
+Number helpers (`input_number` entities), `number` and `sensor` entities that
+contain a numeric value, an be used in the `above` and `below` thresholds,
+making the trigger more dynamic, like:
 
 ```yaml
 automation:
   trigger:
     - platform: numeric_state
-      entity_id: sensor.temperature
-      # input_number entity id can be specified for above and/or below thresholds
-      above: input_number.temperature_threshold_high
-      below: input_number.temperature_threshold_low
+      entity_id: sensor.outside_temperature
+      # Other entity ids can be specified for above and/or below thresholds
+      above: sensor.inside_temperature
 ```
 
 The `for:` can also be specified as `HH:MM:SS` like this:
diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index 3d8ddda80b0..f6578d05df3 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -154,7 +154,8 @@ condition:
   below: 25
 ```
 
-Number helpers (`input_number` entities) can be used in the `above` and `below`
+Number helpers (`input_number` entities), `number` and `sensor` entities that
+contain a numeric value, can be used in the `above` and `below`
 options to make the condition more dynamic.
 
 ```yaml