From 487ff1fe9bf0bfd80f73e5ecce3a5269813f7066 Mon Sep 17 00:00:00 2001 From: Kevin Breit Date: Mon, 26 Feb 2018 05:24:53 -0600 Subject: [PATCH] Fix typos (#36671) Fix minor typos --- docs/docsite/rst/dev_guide/developing_modules_in_groups.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst b/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst index 7a0300da8c..2d6a972b0d 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst @@ -64,7 +64,7 @@ Ansible has a thriving and knowledgeable community of module developers that is On :doc:`../community` you can find how to: * Subscribe to the Mailing Lists - We suggest "Ansible Development List" (for codefreeze info) and "Ansible Announce list" -* ``#ansible-devel`` - We have found that IRC ``#ansible-devel`` on FreeNodes IRC network works best for module developers so we can have an interactive dialogue. +* ``#ansible-devel`` - We have found that IRC ``#ansible-devel`` on FreeNode's IRC network works best for module developers so we can have an interactive dialogue. * IRC meetings - Join the various weekly IRC meetings `meeting schedule and agenda page `_ @@ -114,7 +114,7 @@ Over the years we've experimented with different sized module PRs, ranging from * PRs with multiple modules are harder for the creator to ensure all feedback has been applied * PRs with many modules take a lot more work to review, and tend to get passed over for easier-to-review PRs. -You can raise up to five PRs at one (5 PRs = 5 new modules) **after** your first PR has been merged. We've found this is a good batch size to keep the review process flowing. +You can raise up to five PRs at once (5 PRs = 5 new modules) **after** your first PR has been merged. We've found this is a good batch size to keep the review process flowing. Finally ```````