From c17d8b943900ec2b58e11206ba997d6400140c19 Mon Sep 17 00:00:00 2001 From: Anuvrat Parashar Date: Sat, 27 Jun 2015 12:34:12 +0530 Subject: [PATCH] [grammar nazi] rearrangment. --- docsite/rst/playbooks_vault.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/playbooks_vault.rst b/docsite/rst/playbooks_vault.rst index 241e418d311..745b6f21c22 100644 --- a/docsite/rst/playbooks_vault.rst +++ b/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! -Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you'd not like to betray even 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 :) +Because Ansible tasks, handlers, and so on are also data, these too can be encrypted with vault. If you'd not like to betray even 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 :) .. _creating_files: