From 18a4aecef58588ef6d0911e1afac7b5a6cc34b18 Mon Sep 17 00:00:00 2001 From: Nils Adermann Date: Wed, 8 Mar 2017 10:29:02 +0100 Subject: [PATCH] Docs: superfluous comma & it => Composer --- doc/01-basic-usage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/01-basic-usage.md b/doc/01-basic-usage.md index 44af62d90..1e66a84e4 100644 --- a/doc/01-basic-usage.md +++ b/doc/01-basic-usage.md @@ -64,13 +64,13 @@ Please read [versions](articles/versions.md) for more in-depth information on versions, how versions relate to each other, and on version constraints. > **How does Composer download the right files?** When you specify a dependency in -> `composer.json`, Composer, first takes the name of the package that you've requested +> `composer.json`, Composer first takes the name of the package that you've requested > and searches for it in any repositories that you've registered using the > [`repositories`](04-schema.md#repositories) key. If you haven't registered > any extra repositories, or it doesn't find a package with that name in the > repositories you've specified, it falls back to Packagist (more [below](#packagist)). > -> When it finds the right package, either in Packagist or in a repo you've specified, +> When Composer finds the right package, either in Packagist or in a repo you've specified, > it then uses the versioning features of the package's VCS (i.e., branches and tags) > to attempt to find the best match for the version constraint you've specified. Be sure to read > about versions and package resolution in the [versions article](articles/versions.md).