From 7a7667d079d34fa46a6b6733af8eb2401396e887 Mon Sep 17 00:00:00 2001 From: Gregory Colpart Date: Wed, 21 Dec 2016 00:47:08 +0100 Subject: [PATCH] Fix typos --- CONVENTIONS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONVENTIONS.md b/CONVENTIONS.md index 6f753486..6de69e5a 100644 --- a/CONVENTIONS.md +++ b/CONVENTIONS.md @@ -33,7 +33,7 @@ The main directory is `tasks`. It will contains tasks, either all in the `main.y `vars` will hold files with variables definitions. Those differ from the defaults because of a much higher precedence (see below). -`files` is the directory where we'll put files to copy on hosts. They will be copied "as-is". When a role has multiple logical groups of tasks, it's best to create a sub-directroy for each group that needs files. The name of files in these directories doesn't have to be the same as the destination name. Example : +`files` is the directory where we'll put files to copy on hosts. They will be copied "as-is". When a role has multiple logical groups of tasks, it's best to create a sub-directory for each group that needs files. The name of files in these directories doesn't have to be the same as the destination name. Example : copy: src: apt/jessie_backports_preferences @@ -84,7 +84,7 @@ Here are some reasons : ### defaults -When a role is using variables, they must be defined (for example in the `defaults/main.yml`) with a default value (possibly Ǹull). That way, there will never be a "foo is undefined" situation. +When a role is using variables, they must be defined (for example in the `defaults/main.yml`) with a default value (possibly Null). That way, there will never be a "foo is undefined" situation. ### progressive specificity