Move {% raw %}

fabaff · fabaff · commit 4998875ac8ac · 2018-11-11T23:37:47.000+01:00
diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown
@@ -14,6 +14,7 @@ In Home Assistant 0.19 we introduced a new powerful feature: variables in script
 
 The trigger data made is available during [template](/docs/configuration/templating/) rendering as the `trigger` variable.
 
+{% raw %}
 ```yaml
 # Example configuration.yaml entries
 automation:
@@ -23,28 +24,29 @@ automation:
   action:
     service: notify.notify
     data_template:
-      message: >{% raw %}
+      message: >
         Paulus just changed from {{ trigger.from_state.state }}
-        to {{ trigger.to_state.state }}{% endraw %}
+        to {{ trigger.to_state.state }}
 
 automation 2:
   trigger:
     platform: mqtt
     topic: /notify/+
   action:
-    service_template: >{% raw %}
-      notify.{{ trigger.topic.split('/')[-1] }}{% endraw %}
+    service_template: >
+      notify.{{ trigger.topic.split('/')[-1] }}
     data_template:
-      message: {% raw %}'{{ trigger.payload }}'{% endraw %}
+      message: '{{ trigger.payload }}'
 ```
+{% endraw %}
 
 ## {% linkable_title Important Template Rules %}
 
 There are a few very important rules to remember when writing automation templates:
 
-1. You ***must*** use `data_template` in place of `data` when using templates in the `data` section of a service call.
-1. You ***must*** use `service_template` in place of `service` when using templates in the `service` section of a service call.
-1. You ***must*** surround single-line templates with double quotes (`"`) or single quotes (`'`).
+1. You **must** use `data_template` in place of `data` when using templates in the `data` section of a service call.
+1. You **must** use `service_template` in place of `service` when using templates in the `service` section of a service call.
+1. You **must** surround single-line templates with double quotes (`"`) or single quotes (`'`).
 1. It is advised that you prepare for undefined variables by using `if ... is not none` or the [`default` filter](http://jinja.pocoo.org/docs/dev/templates/#default), or both.
 1. It is advised that when comparing numbers, you convert the number(s) to a [`float`](http://jinja.pocoo.org/docs/dev/templates/#float) or an [`int`](http://jinja.pocoo.org/docs/dev/templates/#int) by using the respective [filter](http://jinja.pocoo.org/docs/dev/templates/#list-of-builtin-filters).
 1. While the [`float`](http://jinja.pocoo.org/docs/dev/templates/#float) and [`int`](http://jinja.pocoo.org/docs/dev/templates/#int) filters do allow a default fallback value if the conversion is unsuccessful, they do not provide the ability to catch undefined variables.
