cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject git commit: CB-7774 fix typos
Date Tue, 14 Oct 2014 18:01:47 GMT
Repository: cordova-coho
Updated Branches:
  refs/heads/master 8a5fd63c9 -> 4b1833f21

CB-7774 fix typos


Branch: refs/heads/master
Commit: 4b1833f21e61f0500d7cc4d2b925bb7553a2d20b
Parents: 8a5fd63
Author: Marcel Kinard <>
Authored: Tue Oct 14 14:01:25 2014 -0400
Committer: Marcel Kinard <>
Committed: Tue Oct 14 14:01:25 2014 -0400

 docs/ | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/ b/docs/
index c0d8147..f8f2227 100644
--- a/docs/
+++ b/docs/
@@ -97,7 +97,7 @@ but plugins will not.
 Where Cordova components have dependencies upon other Cordova components
 (i.e., CLI depends on `cordova-lib`) or upon third-party components (i.e.,
 CLI depends on `nopt`), the `package.json` should fully pin the version of
-the dependent component (i.e., "nopt: "2.3.4") (dependency pinning).
+the dependent component (i.e., "nopt": "2.3.4") (dependency pinning).
 This is in lieu of npm-shrinkwrap since npm-shrinkwrap is not reasonably mature.
 For users that want to install a "fixed recipie" of specific versions
@@ -114,7 +114,7 @@ of all the Cordova components, there are two ways to do that:
 Do note that third-party dependencies which themselves have dependencies on
 other third-party content (i.e., `nopt` depends on `abbrev`), those relationships
 may not be fully pinned since we don't have control of those third-party
-contents. For example, `nopt` 2.2.1 may specify a dependency on version 1.x.x of
+contents. For example, `nopt` 2.2.1 may specify a non-pinned dependency on version 1.x.x
 `abbrev`. So a user may get different versions of `abbrev` at different times
 even though they consistently executed `npm install cordova@3.8.0`. As
 npm-shrinkwrap matures, we hope that it will take care of dependency pinning

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message