From 900e3b65db0bf70d456137648d2d315916f7949f Mon Sep 17 00:00:00 2001
From: dtranmobil <39326050+dtranmobil@users.noreply.github.com>
Date: Thu, 1 Nov 2018 04:12:21 +1100
Subject: [PATCH] Update why-can't-composer-load-repositories-recursively.md
 (#7690)

---
 doc/faqs/why-can't-composer-load-repositories-recursively.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/faqs/why-can't-composer-load-repositories-recursively.md b/doc/faqs/why-can't-composer-load-repositories-recursively.md
index efcd00772..a39aff6fb 100644
--- a/doc/faqs/why-can't-composer-load-repositories-recursively.md
+++ b/doc/faqs/why-can't-composer-load-repositories-recursively.md
@@ -15,7 +15,7 @@ associated with inline VCS repositories.
 There are three ways the dependency solver could work with custom repositories:
 
 - Fetch the repositories of root package, get all the packages from the defined
-repositories, resolve requirements. This is the current state and it works well
+repositories, then resolve requirements. This is the current state and it works well
 except for the limitation of not loading repositories recursively.
 
 - Fetch the repositories of root package, while initializing packages from the