From dd5707ddd971d0d13f4f0333ea6766b120457604 Mon Sep 17 00:00:00 2001 From: Ralph Bean Date: Tue, 11 Jun 2013 14:58:28 -0400 Subject: [PATCH] Well, a little more readability. --- docsite/latest/rst/playbooks.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/latest/rst/playbooks.rst b/docsite/latest/rst/playbooks.rst index a60b7d9f1d..c0d069bd2e 100644 --- a/docsite/latest/rst/playbooks.rst +++ b/docsite/latest/rst/playbooks.rst @@ -37,7 +37,7 @@ Playbooks are expressed in YAML format and have a minimum of syntax. Each playbook is composed of one or more 'plays' in a list. The goal of a play is to map a group of hosts to some well defined roles, represented by -things ansible called tasks. At the basic level, a task is nothing more than a call +things ansible calls tasks. At a basic level, a task is nothing more than a call to an ansible module, which you should have learned about in earlier chapters. By composing a playbook of multiple 'plays', it is possible to