Browse Source

Update why-are-unbound-version-constraints-a-bad-idea.md

Minor text improvement
Felix Kiss 10 years ago
parent
commit
65f8d1c247
1 changed files with 1 additions and 1 deletions
  1. 1 1
      doc/faqs/why-are-unbound-version-constraints-a-bad-idea.md

+ 1 - 1
doc/faqs/why-are-unbound-version-constraints-a-bad-idea.md

@@ -14,7 +14,7 @@ compatible with the new major version of your dependency.
 
 
 For example instead of using `>=3.4` you should use `~3.4` which allows all
 For example instead of using `>=3.4` you should use `~3.4` which allows all
 versions up to `3.999` but does not include `4.0` and above. The `~` operator
 versions up to `3.999` but does not include `4.0` and above. The `~` operator
-works very well with libraries follow [semantic versioning](http://semver.org).
+works very well with libraries following [semantic versioning](http://semver.org).
 
 
 **Note:** As a package maintainer, you can make the life of your users easier
 **Note:** As a package maintainer, you can make the life of your users easier
 by providing an [alias version](../articles/aliases.md) for your development
 by providing an [alias version](../articles/aliases.md) for your development