From c39912287d9683c40aeaec370ab8ed2f29bbb698 Mon Sep 17 00:00:00 2001 From: Gilles Cornu Date: Thu, 6 Mar 2014 23:57:47 +0100 Subject: [PATCH] website/docs: remove unwanted brackets (typo) --- website/docs/source/v2/provisioning/ansible.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/source/v2/provisioning/ansible.html.md b/website/docs/source/v2/provisioning/ansible.html.md index 6a841e0e9..89523dad5 100644 --- a/website/docs/source/v2/provisioning/ansible.html.md +++ b/website/docs/source/v2/provisioning/ansible.html.md @@ -223,7 +223,7 @@ Vagrant is designed to provision [multi-machine environments](/v2/multi-machine) Certain settings in Ansible are (only) adjustable via a [configuration file](http://docs.ansible.com/intro_configuration.html), and you might want to ship such a file in your Vagrant project. -As `ansible-playbook` command looks for local [`ansible.cfg`] configuration file in its *current directory* (but not in the directory that contains the main playbook), you have to store this file adjacent to your Vagrantfile. +As `ansible-playbook` command looks for local `ansible.cfg` configuration file in its *current directory* (but not in the directory that contains the main playbook), you have to store this file adjacent to your Vagrantfile. Note that it is also possible to reference an Ansible configuration file via `ANSIBLE_CONFIG` environment variable, if you want to be flexible about the location of this file.