From fe88dee982e6f592f6f837c5dc94282fe1c2e0e3 Mon Sep 17 00:00:00 2001 From: myqlarson Date: Wed, 24 Apr 2013 20:49:19 +1200 Subject: [PATCH] Fixes #1822 Update 02-libraries.md If username is unrelated, then I propose `username` rather than `composer` or `acme` to avoid confusion. --- doc/02-libraries.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/02-libraries.md b/doc/02-libraries.md index 94b6e9272..59f2a3a26 100644 --- a/doc/02-libraries.md +++ b/doc/02-libraries.md @@ -122,7 +122,7 @@ the `.gitignore`. Once you have a vcs repository (version control system, e.g. git) containing a `composer.json` file, your library is already composer-installable. In this example we will publish the `acme/hello-world` library on GitHub under -`github.com/acme/hello-world`. +`github.com/username/hello-world`. Now, To test installing the `acme/hello-world` package, we create a new project locally. We will call it `acme/blog`. This blog will depend on @@ -150,7 +150,7 @@ We do this by adding a package repository specification to the blog's "repositories": [ { "type": "vcs", - "url": "https://github.com/acme/hello-world" + "url": "https://github.com/username/hello-world" } ], "require": {