# (devel) Playbooks and tasks now check themselves for typos a bit better

**URL:** <https://forum.ansible.com/t/devel-playbooks-and-tasks-now-check-themselves-for-typos-a-bit-better/11697>\
**Category:** Ansible Project\
**Created:** [July 17, 2012, 11:23pm UTC](https://forum.ansible.com/t/devel-playbooks-and-tasks-now-check-themselves-for-typos-a-bit-better/11697 "2012-07-17T23:23:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [July 17, 2012, 11:23pm UTC](https://forum.ansible.com/t/devel-playbooks-and-tasks-now-check-themselves-for-typos-a-bit-better/11697/1 "2012-07-17T23:23:40Z")

</div>

If you type "var" for "vars", or try to use a keyword that Ansible doesn't know about, it will now yell at you.

If you were doing things like:

"comment: this is a comment"

You should switch to YAML comments

# YAML comments look like this.

This was done to prevent the whole class of questions in the form of:

&nbsp;&nbsp;&nbsp;- Ansible is broken! Here is a snippet of my playbook!  
&nbsp;&nbsp;&nbsp;- What does your playbook look like?  
&nbsp;&nbsp;&nbsp;- Here it is  
&nbsp;&nbsp;&nbsp;- It's "vars\_files" not "var\_files"!  
&nbsp;&nbsp;&nbsp;- It's still not working!  
&nbsp;&nbsp;&nbsp;- Let me see your playbook…

In the event that I have somehow forgotten something legal that should be in the list, and you think it's yelling about you about something  
valid, let me know.

(Grep for VALID\_KEYS in the source if you are curious where this is)

--Michael