makes it more concise.

@msabramos's suggestions[1] incorporated.

[1] https://github.com/ansible/ansible/pull/11410#issuecomment-116319780

docsite/rst/playbooks_vault.rst

@@ -14,7 +14,7 @@ What Can Be Encrypted With Vault
 
 The vault feature can encrypt any structured data file used by Ansible.  This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json".  Role variables and defaults are also included!
 
-Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. If you don't want to even reveal the variables you are using you can go as far as keeping individual task files entirely encrypted. However, that might be a little too much and could annoy your coworkers :)
+Ansible tasks, handlers, and so on are also data so these can be encrypted with vault as well. To hide the names of variables that you're using, you can encrypt the task files in their entirety. However, that might be a little too much and could annoy your coworkers :)
 
 .. _creating_files: