From 070e41d88b79908107518f8716b9ce8418c4b194 Mon Sep 17 00:00:00 2001
From: Abdullah <73560425+zer-far@users.noreply.github.com>
Date: Wed, 27 Apr 2022 18:53:03 +0100
Subject: Change "Github" to "GitHub"

---
 docs/CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs')

diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index 14b52a2af..a50114d1a 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -12,7 +12,7 @@ of software solid and usable.
 * If modifying code for which Doxygen headers exist, that header must be modified to match.
 * Tests would be nice to have if you're adding functionality.
 
-Patches are preferably to be sent via a Github pull request. If that
+Patches are preferably to be sent via a GitHub pull request. If that
 can't be done, patches in "git format-patch" format can be sent
 (eg, posted to fpaste.org with a long enough timeout and a link
 posted to #monero-dev on irc.libera.chat).
@@ -43,7 +43,7 @@ Commit messages should be sensible. That means a subject line that
 describes the patch, with an optional longer body that gives details,
 documentation, etc.
 
-When submitting a pull request on Github, make sure your branch is
+When submitting a pull request on GitHub, make sure your branch is
 rebased. No merge commits nor stray commits from other people in
 your submitted branch, please. You may be asked to rebase if there
 are conflicts (even trivially resolvable ones).
-- 
cgit v1.2.3