diff --git a/source/_components/scene.markdown b/source/_components/scene.markdown
index 74e8dd09b4f..90c816cb1ca 100644
--- a/source/_components/scene.markdown
+++ b/source/_components/scene.markdown
@@ -11,7 +11,7 @@ logo: home-assistant.png
 ha_category: Organization
 ---
 
-You can create scenes that capture the states you want certain entities to be. For example a scene can specify that light A should be turned on and light B should be bright red.
+You can create scenes that capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red.
 
 ```yaml
 # Example configuration.yaml entry
@@ -38,6 +38,13 @@ Configuration variables:
 - **name** (*Required*): Friendly name of scene.
 - **entities** (*Required*): Entities to control.
 
+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#L74). 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
@@ -55,5 +62,5 @@ automation:
 ```
 
 <p class='note'>
-Please note that the scene component currently only supports one service call per entity to achieve the state. Due to this limitation you cannot set states belonging to different services.
+Please note that the scene component currently 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.
 </p>