From 5b34a61b4a9802fd18d02c49a538b3f7fea90469 Mon Sep 17 00:00:00 2001
From: Frank Prins <25006490+PrinsFrank@users.noreply.github.com>
Date: Mon, 5 Oct 2020 21:13:02 +0200
Subject: [PATCH] Capitalize composer name occurrences

---
 doc/articles/authentication-for-private-packages.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/articles/authentication-for-private-packages.md b/doc/articles/authentication-for-private-packages.md
index 3762465dd..9c7e7633e 100644
--- a/doc/articles/authentication-for-private-packages.md
+++ b/doc/articles/authentication-for-private-packages.md
@@ -11,9 +11,9 @@ package(s).
 
 # Authentication principles
 
-Whenever composer encounters a protected composer repository it will try to authenticate
+Whenever Composer encounters a protected Composer repository it will try to authenticate
 using already defined credentials first. When none of those credentials apply it will prompt
-for credentials instead otherwise overridden and save those (or a token if composer is able
+for credentials instead otherwise overridden and save those (or a token if Composer is able
 to retrieve one).
 
 |type|Generated by Prompt?|
@@ -43,7 +43,7 @@ command line or manually edit or create it.
 
 If you don't want to supply credentials for every project you work on, storing your credentials
 globally might be a better idea. These credentials are stored in a global `auth.json` in your
-composer home directory.
+Composer home directory.
 
 ### Command line global credential editing
 
@@ -124,7 +124,7 @@ composer config [--global] --editor --auth
 
 For the inline http-basic authentication method the credentials are not stored in a separate
 `auth.json` in the project or globally, but in the `composer.json` or global configuration
-in the same place where the composer repository definition is defined.
+in the same place where the Composer repository definition is defined.
 
 ### Command line inline http-basic