Fix line wrapping consistency - round 1

Comply with the 'wrap at 120 chars' style rule stated in the contributing.md document

_posts/04-02-01-Composer-and-Packagist.md

@@ -5,26 +5,35 @@ anchor: composer_and_packagist
 
 ## Composer and Packagist {#composer_and_packagist_title}
 
-Composer is a **brilliant** dependency manager for PHP. List your project's dependencies in a `composer.json` file and, with a few simple commands, Composer will automatically download your project's dependencies and setup autoloading for you.
+Composer is a **brilliant** dependency manager for PHP. List your project's dependencies in a `composer.json` file and,
+with a few simple commands, Composer will automatically download your project's dependencies and setup autoloading for
+you.
 
-There are already a lot of PHP libraries that are compatible with Composer, ready to be used in your project. These "packages" are listed on [Packagist][1], the official repository for Composer-compatible PHP libraries.
+There are already a lot of PHP libraries that are compatible with Composer, ready to be used in your project. These
+"packages" are listed on [Packagist][1], the official repository for Composer-compatible PHP libraries.
 
 ### How to Install Composer
 
-You can install Composer locally (in your current working directory; though this is no longer recommended) or globally (e.g. /usr/local/bin). Let's assume you want to install Composer locally. From your project's root directory:
+You can install Composer locally (in your current working directory; though this is no longer recommended) or globally
+(e.g. /usr/local/bin). Let's assume you want to install Composer locally. From your project's root directory:
 
 {% highlight console %}
 curl -s https://getcomposer.org/installer | php
 {% endhighlight %}
 
-This will download `composer.phar` (a PHP binary archive). You can run this with `php` to manage your project dependencies. <strong>Please Note:</strong> If you pipe downloaded code directly into an interpreter, please read the code online first to confirm it is safe.
+This will download `composer.phar` (a PHP binary archive). You can run this with `php` to manage your project
+dependencies. <strong>Please Note:</strong> If you pipe downloaded code directly into an interpreter, please read the
+code online first to confirm it is safe.
 
 #### Installing on Windows
-For Windows users the easiest way to get up and running is to use the [ComposerSetup][6] installer, which performs a global install and sets up your `$PATH` so that you can just call `composer` from any directory in your command line.
+For Windows users the easiest way to get up and running is to use the [ComposerSetup][6] installer, which performs a
+global install and sets up your `$PATH` so that you can just call `composer` from any directory in your command line.
 
 ### How to Install Composer (manually)
 
-Manually installing Composer is an advanced technique; however, there are various reasons why a developer might prefer this method vs. using the interactive installation routine. The interactive installation checks your PHP installation to ensure that:
+Manually installing Composer is an advanced technique; however, there are various reasons why a developer might prefer
+this method vs. using the interactive installation routine. The interactive installation checks your PHP installation
+to ensure that:
 
 - a sufficient version of PHP is being used
 - `.phar` files can be executed correctly
@@ -32,16 +41,19 @@ Manually installing Composer is an advanced technique; however, there are variou
 - certain problematic extensions are not loaded
 - certain `php.ini` settings are set
 
-Since a manual installation performs none of these checks, you have to decide whether the trade-off is worth it for you. As such, below is how to obtain Composer manually:
+Since a manual installation performs none of these checks, you have to decide whether the trade-off is worth it for
+you. As such, below is how to obtain Composer manually:
 
 {% highlight console %}
 curl -s https://getcomposer.org/composer.phar -o $HOME/local/bin/composer
 chmod +x $HOME/local/bin/composer
 {% endhighlight %}
 
-The path `$HOME/local/bin` (or a directory of your choice) should be in your `$PATH` environment variable. This will result in a `composer` command being available.
+The path `$HOME/local/bin` (or a directory of your choice) should be in your `$PATH` environment variable. This will
+result in a `composer` command being available.
 
-When you come across documentation that states to run Composer as `php composer.phar install`, you can substitute that with:
+When you come across documentation that states to run Composer as `php composer.phar install`, you can substitute that
+with:
 
 {% highlight console %}
 composer install
@@ -51,19 +63,25 @@ This section will assume you have installed composer globally.
 
 ### How to Define and Install Dependencies
 
-Composer keeps track of your project's dependencies in a file called `composer.json`. You can manage it by hand if you like, or use Composer itself. The `composer require` command adds a project dependency and if you don't have a `composer.json` file, one will be created. Here's an example that adds [Twig][2] as a dependency of your project.
+Composer keeps track of your project's dependencies in a file called `composer.json`. You can manage it by hand if you
+like, or use Composer itself. The `composer require` command adds a project dependency and if you don't have a
+`composer.json` file, one will be created. Here's an example that adds [Twig][2] as a dependency of your project.
 
 {% highlight console %}
 composer require twig/twig:~1.8
 {% endhighlight %}
 
-Alternatively the `composer init` command will guide you through creating a full `composer.json` file for your project. Either way, once you've created your `composer.json` file you can tell Composer to download and install your dependencies into the `vendor/` directory. This also applies to projects you've downloaded that already provide a `composer.json` file:
+Alternatively the `composer init` command will guide you through creating a full `composer.json` file for your project.
+Either way, once you've created your `composer.json` file you can tell Composer to download and install your
+dependencies into the `vendor/` directory. This also applies to projects you've downloaded that already provide a
+`composer.json` file:
 
 {% highlight console %}
 composer install
 {% endhighlight %}
 
-Next, add this line to your application's primary PHP file; this will tell PHP to use Composer's autoloader for your project dependencies.
+Next, add this line to your application's primary PHP file; this will tell PHP to use Composer's autoloader for your
+project dependencies.
 
 {% highlight php %}
 <?php
@@ -74,18 +92,25 @@ Now you can use your project dependencies, and they'll be autoloaded on demand.
 
 ### Updating your dependencies
 
-Composer creates a file called `composer.lock` which stores the exact version of each package it downloaded when you first ran `php composer.phar install`. If you share your project with other coders and the `composer.lock` file is part of your distribution, when they run `php composer.phar install` they'll get the same versions as you. To update your dependencies, run `php composer.phar update`.
+Composer creates a file called `composer.lock` which stores the exact version of each package it downloaded when you
+first ran `php composer.phar install`. If you share your project with other coders and the `composer.lock` file is
+part of your distribution, when they run `php composer.phar install` they'll get the same versions as you. To update
+your dependencies, run `php composer.phar update`.
 
-This is most useful when you define your version requirements flexibly. For instance a version requirement of `~1.8` means "anything newer than `1.8.0`, but less than `2.0.x-dev`". You can also use the `*` wildcard as in `1.8.*`. Now Composer's `php composer.phar update` command will upgrade all your dependencies to the newest version that fits the restrictions you define.
+This is most useful when you define your version requirements flexibly. For instance a version requirement of `~1.8`
+means "anything newer than `1.8.0`, but less than `2.0.x-dev`". You can also use the `*` wildcard as in `1.8.*`. Now
+Composer's `php composer.phar update` command will upgrade all your dependencies to the newest version that fits the
+restrictions you define.
 
 ### Update Notifications
 
-To receive notifications about new version releases you can sign up for [VersionEye][3], a web service that can monitor 
+To receive notifications about new version releases you can sign up for [VersionEye][3], a web service that can monitor
 your GitHub and BitBucket accounts for `composer.json` files and send emails with new package releases.
 
 ### Checking your dependencies for security issues
 
-The [Security Advisories Checker][4] is a web service and a command-line tool, both will examine your `composer.lock` file and tell you if you need to update any of your dependencies.
+The [Security Advisories Checker][4] is a web service and a command-line tool, both will examine your `composer.lock`
+file and tell you if you need to update any of your dependencies.
 
 * [Learn about Composer][5]