Jordi Boggiano 13 лет назад
Родитель
Сommit
036c81b1cc
1 измененных файлов с 2 добавлено и 2 удалено
  1. 2 2
      doc/05-repositories.md

+ 2 - 2
doc/05-repositories.md

@@ -68,7 +68,7 @@ The only required field is `packages`. The JSON structure is as follows:
 
     {
         "packages": {
-            "vendor/packageName": {
+            "vendor/package-name": {
                 "dev-master": { @composer.json },
                 "1.0.x-dev": { @composer.json },
                 "0.0.1": { @composer.json },
@@ -161,7 +161,7 @@ project to use the patched version. If the library is on GitHub (this is the
 case most of the time), you can simply fork it there and push your changes to
 your fork. After that you update the project's `composer.json`. All you have
 to do is add your fork as a repository and update the version constraint to
-point to your custom branch. For version constraint naming conventions see 
+point to your custom branch. For version constraint naming conventions see
 [Libraries](02-libraries.md) for more information.
 
 Example assuming you patched monolog to fix a bug in the `bugfix` branch: