From 632f63a9a34c6b676e8f383591e1b9d126a74412 Mon Sep 17 00:00:00 2001
From: Philipp Bammes <8144115+tyrann0us@users.noreply.github.com>
Date: Wed, 12 Oct 2022 17:02:26 +0200
Subject: [PATCH] Fix typo in "WordPress" (#11082)

---
 doc/05-repositories.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/05-repositories.md b/doc/05-repositories.md
index 1ab7f5ca6..b71027f1b 100644
--- a/doc/05-repositories.md
+++ b/doc/05-repositories.md
@@ -591,7 +591,7 @@ time, there are some use cases for hosting your own repository.
 * **Separate ecosystem:** If you have a project which has its own ecosystem,
   and the packages aren't really reusable by the greater PHP community, you
   might want to keep them separate to packagist. An example of this would be
-  wordpress plugins.
+  WordPress plugins.
 
 For hosting your own packages, a native `composer` type of repository is
 recommended, which provides the best performance.