public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Docs: superfluous comma & it => Composer

pull/6093/merge
Nils Adermann 2017-03-08 10:29:02 +01:00
parent 7bdc929e6d
commit 18a4aecef5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/01-basic-usage.md
View File

@ -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. versions, how versions relate to each other, and on version constraints.
> **How does Composer download the right files?** When you specify a dependency in > **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 > and searches for it in any repositories that you've registered using the
> [`repositories`](04-schema.md#repositories) key. If you haven't registered > [`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 > 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)). > 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) > 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 > 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). > about versions and package resolution in the [versions article](articles/versions.md).