From 4302ede68abd7aba56489473390dccc770c99316 Mon Sep 17 00:00:00 2001 From: Dmitry Menshikov Date: Thu, 11 Oct 2012 21:20:49 +0300 Subject: [PATCH] Fixed urls on the troubleshooting page --- doc/articles/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 54ee71967..9c71ea3ec 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -8,7 +8,7 @@ This is a list of common pitfalls on using Composer, and how to avoid them. ## General 1. When facing any kind of problems using Composer, be sure to **work with the - latest version**. See [self-update](03-cli.md#self-update) for details. + latest version**. See [self-update](../03-cli.md#self-update) for details. 2. Ensure you're **installing vendors straight from your `composer.json`** via `rm -rf vendor && composer update -v` when troubleshooting, excluding any @@ -21,7 +21,7 @@ This is a list of common pitfalls on using Composer, and how to avoid them. branches and tag names. 2. Be sure to **set the right - [minimum-stability](04-schema.md#minimum-stability)**. To get started or be + [minimum-stability](../04-schema.md#minimum-stability)**. To get started or be sure this is no issue, set `minimum-stability` to "dev". 3. Packages **not coming from [Packagist](http://packagist.org/)** should