From bde41bac359313207dadcc480a8fafb7261f465f Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Thu, 26 Dec 2013 14:33:25 -0500 Subject: [PATCH] Fix some small docsite formatting things. --- docsite/rst/playbooks_variables.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docsite/rst/playbooks_variables.rst b/docsite/rst/playbooks_variables.rst index 9d25a958735..127c0bc3002 100644 --- a/docsite/rst/playbooks_variables.rst +++ b/docsite/rst/playbooks_variables.rst @@ -67,7 +67,7 @@ This can be nice as it's right there when you are reading the playbook. .. _included_variables: Variables defined from included files and roles ------------------------------------------------ +``````````````````````````````````````````````` It turns out we've already talked about variables in another place too. @@ -85,13 +85,13 @@ Ansible allows you to reference variables in your playbooks using the Jinja2 templating system. While you can do a lot of complex things in Jinja, only the basics are things you really need to learn at first. -For instance, in a simple template, you can do something like +For instance, in a simple template, you can do something like:: My amp goes to {{ max_amp_value }} And that will provide the most basic form of variable substitution. -This is also valid directly in playbooks, and you'll occasionally want to do things like: +This is also valid directly in playbooks, and you'll occasionally want to do things like:: template: src=foo.cfg.j2 dest={{ remote_install_path}}/foo.cfg