# Documentation glossary added -- now let's go make it better :)

**URL:** <https://forum.ansible.com/t/documentation-glossary-added-now-lets-go-make-it-better/12371>\
**Category:** Ansible Project\
**Created:** [February 16, 2013, 11:53pm UTC](https://forum.ansible.com/t/documentation-glossary-added-now-lets-go-make-it-better/12371 "2013-02-16T23:53:15Z")\
**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:** [February 16, 2013, 11:53pm UTC](https://forum.ansible.com/t/documentation-glossary-added-now-lets-go-make-it-better/12371/1 "2013-02-16T23:53:15Z")

</div>

I've had a few requests for a glossary of terms to help people  
understand things, for when the documentation explaining things down  
the one golden path didn't quite succeed in explaning what it set out  
to explain. I think that's valid, we can reinforce things by  
explaining them in different ways.

So I wrote a glossary. This document is a start, just a start. Here  
it is: [http://ansible.cc/docs/glossary.html](http://ansible.cc/docs/glossary.html)

Since all of our documentation lives in git (docsite/rst/glossary.rst)  
I would welcome for anyone to improve it by adding more content,  
crosslinks back into the documentation where things are being  
discussed, etc.

Patches welcome for all kinds of things.

I'm going to work on the best practices page and making that better  
tomorrow too (along with a handful of other features). Today was  
mostly about merging a TON of pull requests. Lots of great stuff  
lately.

--Michael