Browse Source

finish updating links to .md

Jordi Boggiano 13 years ago
parent
commit
f3c4b8661d
4 changed files with 8 additions and 8 deletions
  1. 2 2
      doc/02-libraries.md
  2. 3 3
      doc/03-cli.md
  3. 2 2
      doc/04-schema.md
  4. 1 1
      doc/05-repositories.md

+ 2 - 2
doc/02-libraries.md

@@ -74,7 +74,7 @@ Here are some examples of version branch names:
     1.1.*
 
 > **Note:** When you install a dev version, it will install it from source.
-See [Repositories](05-repositories) for more information.
+See [Repositories](05-repositories.md) for more information.
 
 ## Lock file
 
@@ -129,7 +129,7 @@ We do this by adding a package repository specification to the blog's
     }
 
 For more details on how package repositories work and what other types are
-available, see [Repositories](05-repositories).
+available, see [Repositories](05-repositories.md).
 
 That's all. You can now install the dependencies by running composer's
 `install` command!

+ 3 - 3
doc/03-cli.md

@@ -5,7 +5,7 @@ things. This chapter documents all the available commands.
 
 ## init
 
-In the [Libraries](02-libraries) chapter we looked at how to create a `composer.json` by
+In the [Libraries](02-libraries.md) chapter we looked at how to create a `composer.json` by
 hand. There is also an `init` command available that makes it a bit easier to
 do this.
 
@@ -106,7 +106,7 @@ specific version.
 ### Options
 
 * **--installed:** Will list the packages that are installed.
-* **--platform:** Will list only [Platform packages].
+* **--platform:** Will list only platform packages (php & extensions).
 
 ## depends
 
@@ -171,7 +171,7 @@ directory other than `vendor`.
 
 ### COMPOSER_BIN_DIR
 
-By setting this option you can change the `bin` ([Vendor Bins](articles/vendor-bins))
+By setting this option you can change the `bin` ([Vendor Bins](articles/vendor-bins.md))
 directory to something other than `vendor/bin`.
 
 ### COMPOSER_PROCESS_TIMEOUT

+ 2 - 2
doc/04-schema.md

@@ -247,7 +247,7 @@ The following repository types are supported:
   composer whatsoever you can define the package inline using a `package`
   repository. You basically just inline the `composer.json` object.
 
-For more information on any of these, see [Repositories](05-repositories).
+For more information on any of these, see [Repositories](05-repositories.md).
 
 Example:
 
@@ -385,7 +385,7 @@ Optional.
 A set of files that should be treated as binaries and symlinked into the `bin-
 dir` (from config).
 
-See (Vendor Bins)[articles/vendor-bins] for more details.
+See (Vendor Bins)[articles/vendor-bins.md] for more details.
 
 Optional.
 

+ 1 - 1
doc/05-repositories.md

@@ -81,7 +81,7 @@ Here is a minimal package definition:
         }
     }
 
-It may include any of the other fields specified in the [schema].
+It may include any of the other fields specified in the [schema](04-schema.md).
 
 The `composer` repository is also what packagist uses. To reference a
 `composer` repository, just supply the path before the `packages.json` file.