Some docs update

doc/02-libraries.md

@@ -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].
+available, see [Repositories](05-repositories).
 
 That's all. You can now install the dependencies by running composer's
 `install` command!

doc/03-cli.md

@@ -5,7 +5,7 @@ things. This chapter documents all the available commands.
 
 ## init
 
-In the [Libraries] chapter we looked at how to create a `composer.json` by
+In the [Libraries](02-libraries) 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.
 
@@ -171,7 +171,7 @@ directory other than `vendor`.
 
 ### COMPOSER_BIN_DIR
 
-By setting this option you can change the `bin` ([articles/vendor-bins.md])
+By setting this option you can change the `bin` ([Vendor Bins](articles/vendor-bins))
 directory to something other than `vendor/bin`.
 
 ### COMPOSER_PROCESS_TIMEOUT

doc/04-schema.md

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

doc/articles/packagist-update-schedule.md

@@ -19,4 +19,7 @@ indexer ran.
 
 ## Can Packagist be triggered to recrawl a package (on commit or by other means)?
 
-Not yet. :) See [#84](https://github.com/composer/packagist/issues/84).
+Yes, you can click the "Force update" button on your package page if you are
+logged in as a maintainer. The recommended way is to set up the GitHub hook,
+you can find the URL and instructions on your Packagist
+[profile](http://packagist.org/profile/) page.

doc/articles/scripts.md

@@ -1,3 +1,6 @@
+<!--
+    tagline: Script are callbacks that are called before/after installing packages
+-->
 # Scripts
 
 ## What is a script?