diff --git a/source/_integrations/cast.markdown b/source/_integrations/cast.markdown
index 65900c5bfb7..def2b009577 100644
--- a/source/_integrations/cast.markdown
+++ b/source/_integrations/cast.markdown
@@ -23,7 +23,7 @@ Support for mDNS discovery in your local network is mandatory. Make sure that yo
 Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device.  You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url` Typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
 
 ```yaml
-'cast_downstairs_on_kitchen':
+cast_downstairs_on_kitchen:
   alias: Show Downstairs on kitchen
   sequence:
   - data: