From 8e9a5c8de7482080724cbb9bfba2dc9af5e72eb6 Mon Sep 17 00:00:00 2001
From: mclean <36020076+mcozine20@users.noreply.github.com>
Date: Thu, 24 Jan 2019 20:28:39 +0000
Subject: [PATCH] changes 'github' to 'GitHub' in community (#51111)

* changes 'github' to 'GitHub' in community
---
 docs/docsite/rst/community/committer_guidelines.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docsite/rst/community/committer_guidelines.rst b/docs/docsite/rst/community/committer_guidelines.rst
index ea71d7eb9c4..086474841c2 100644
--- a/docs/docsite/rst/community/committer_guidelines.rst
+++ b/docs/docsite/rst/community/committer_guidelines.rst
@@ -56,7 +56,7 @@ Individuals with direct commit access to ansible/ansible are entrusted with powe
 
 * Do
 
-  - Squash, avoid merges whenever possible, use github's squash commits or cherry pick if needed (bisect thanks you).
+  - Squash, avoid merges whenever possible, use GitHub's squash commits or cherry pick if needed (bisect thanks you).
   - Be active. Committers who have no activity on the project (through merges, triage, commits, etc.) will have their permissions suspended.
   - Consider backwards compatibility (goes back to "don't break existing playbooks").
   - Write tests. PRs with tests are looked at with more priority than PRs without tests that should have them included. While not all changes require tests, be sure to add them for bug fixes or functionality changes.