From 062b05d37d7de0e5fbf8cf3f5d5d5fc98233b893 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Sat, 27 Apr 2013 17:51:05 +0200 Subject: [PATCH] Fix typos/wording --- doc/articles/troubleshooting.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 4dcfcf17f..c0630cb61 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -53,23 +53,24 @@ This is a list of common pitfalls on using Composer, and how to avoid them. Use: `before_script: COMPOSER_ROOT_VERSION=dev-master composer install` to export the variable for the call to composer. -## Need to override package version +## Need to override a package version -Let say your project depends on package A which in turn depends on a spesific version of -package B (say 0.1) and you need a different version of that package - version 0.11. +Let say your project depends on package A which in turn depends on a specific +version of package B (say 0.1) and you need a different version of that +package - version 0.11. -You fix this by renaming version 0.11 as 0.1: +You can fix this by aliasing version 0.11 to 0.1: composer.json: + { - name: "My project", require: { "A": "0.2", "B": "0.11 as 0.1" } } -Also, se [aliases](aliases.md) for more information. +See [aliases](aliases.md) for more information. ## Memory limit errors