diff --git a/source/_components/scene.markdown b/source/_components/scene.markdown
index df4b6bbf432..ee34b7d0dfc 100644
--- a/source/_components/scene.markdown
+++ b/source/_components/scene.markdown
@@ -15,15 +15,15 @@ You can create scenes that capture the states you want certain entities to be. F
 scene:
   - name: Romantic
     entities:
-      light.tv_back_light: true
+      light.tv_back_light: on
       light.ceiling:
-        state: true
+        state: on
         xy_color: [0.33, 0.66]
         brightness: 200
   - name: Movies
     entities:
       light.tv_back_light:
-        state: true
+        state: on
         brightness: 100
       light.ceiling: false
       media_player.sony_bravia_tv:
@@ -46,8 +46,6 @@ As you can see, there are two ways to define the states of each `entity_id`:
 - Define the `state` directly with the entity.
 - Define a complex state with its attributes.
 
-The mapping from states to services is done with the [state helper](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/helpers/state.py#L82). So, please have a look there for available states for your scenes.
-
 Scenes can be activated using the service `scene.turn_on` (there is no 'scene.turn_off' service).
 
 ```yaml
@@ -63,7 +61,3 @@ automation:
     service: scene.turn_on
     entity_id: scene.romantic
 ```
-
-<div class='note'>
-Please note that the scene integration for the most part only supports one service call per entity to achieve the state. Due to this limitation, you cannot set states belonging to different services. A workaround for this limitation is to write a script, which you then turn on in your scene. A few integrations have direct support for multiple service calls per state, Currently this is the media_player and climate components.
-</div>