From 244277adddfadc1fe5ef1cc34cab6b6857d95267 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Fri, 21 Feb 2020 13:56:35 +0300 Subject: [PATCH] dev_guide/developing_modules_best_practices.rst: fix typo (#67639) --- .../docsite/rst/dev_guide/developing_modules_best_practices.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst index 35a65771a01..68609d0e716 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst @@ -31,7 +31,7 @@ Designing module interfaces General guidelines & tips ========================= -* Each module should be self-contained in one file, so it can be be auto-transferred by Ansible. +* Each module should be self-contained in one file, so it can be auto-transferred by Ansible. * Module name MUST use underscores instead of hyphens or spaces as a word separator. Using hyphens and spaces will prevent Ansible from importing your module. * Always use the ``hacking/test-module.py`` script when developing modules - it will warn you about common pitfalls. * If you have a local module that returns facts specific to your installations, a good name for this module is ``site_facts``.