Jordi Boggiano 13 anni fa
parent
commit
38ef1dcb24
3 ha cambiato i file con 12 aggiunte e 12 eliminazioni
  1. 4 4
      doc/00-intro.md
  2. 7 7
      doc/02-libraries.md
  3. 1 1
      doc/04-schema.md

+ 4 - 4
doc/00-intro.md

@@ -14,10 +14,10 @@ node's [npm](http://npmjs.org/) and ruby's [bundler](http://gembundler.com/).
 But there has not been such a tool for PHP so far.
 
 The problem that composer solves is the following. You have a project that
-depends on a number of libraries. Some of libraries have dependencies of their
-own. You declare the things you depend on. Composer will then go ahead and
-find out which versions of which packages need to be installed, and install
-them.
+depends on a number of libraries. Some of those libraries have dependencies of
+their own. You declare the things you depend on. Composer will then go ahead
+and find out which versions of which packages need to be installed, and
+install them.
 
 ## Declaring dependencies
 

+ 7 - 7
doc/02-libraries.md

@@ -154,15 +154,15 @@ every time is cumbersome. You don't want to force all your users to do that.
 The other thing that you may have noticed is that we did not specify a package
 repository for `monolog/monolog`. How did that work? The answer is packagist.
 
-Packagist is the main package repository for composer, and it is enabled by
-default. Anything that is published on packagist is available automatically
-through composer. Since monolog [is on
-packagist](http://packagist.org/packages/monolog/monolog), we can depend on it
-without having to specify any additional repositories.
+[Packagist](http://packagist.org/) is the main package repository for
+composer, and it is enabled by default. Anything that is published on
+packagist is available automatically through composer. Since monolog
+[is on packagist](http://packagist.org/packages/monolog/monolog), we can depend
+on it without having to specify any additional repositories.
 
 Assuming we want to share `hello-world` with the world, we would want to
 publish it on packagist as well. And this is really easy.
 
 You simply hit the big "Submit Package" button and sign up. Then you submit
-the URL to your VCS, at which point packagist will start crawling it. Once it
-is done, your package will be available to anyone.
+the URL to your VCS repository, at which point packagist will start crawling
+it. Once it is done, your package will be available to anyone.

+ 1 - 1
doc/04-schema.md

@@ -412,6 +412,6 @@ Optional.
 A set of files that should be treated as binaries and symlinked into the `bin-
 dir` (from config).
 
-See [faq/bin.md] for more details.
+See [articles/bin.md] for more details.
 
 Optional.