some fixes

README.md

@@ -18,10 +18,10 @@
 
 ## Why?
 
-- Bumped separates the processes of creating and publishing software.
-- It syncronizes, unifies and publishes different software versions into the different package managers.
-- It is easy to integrate it with both with your current and new projects.
-- It will associate actions before or after publishing your software *(not yet, but soon!)*.
+- Separates the processes of creating and publishing software.
+- Syncronizes, unifies and publishes different software versions into the different package managers.
+- Easy to integrate it with both with your current and new projects.
+- Associated actions before or after publishing your software *(not yet, but soon!)*.
 
 **Bumped** synchronizes your software version across different package manager configuration files (npm, bower,...) and controls, edits and releases each of its versions to ensure all the files have the same version.
 
@@ -43,12 +43,12 @@ The first command that you need to run is `bumped init`. If you run it in a tota
 $ bumped init
 
 warn  : It has been impossible to detect files automatically.
-warn  : It tries to add manually with 'add' command.
-warn  : There is no version declared.
+warn  : Try to add manually with 'add' command.
+warn  : There isn't version declared.
 success : Config file created!.
 ```
 
-The magic appears when running it in a project with common package manager configuration files, for instance, both `package.json` and `bower.json`:
+The magic appears when running it in a project with common package manager configuration files, for instance, like `package.json` or `bower.json`:
 
 ```bash
 $ bumped init
@@ -66,11 +66,11 @@ files: [
 ]
 ```
 
-The file format is [CSON](https://github.com/bevry/cson). You can also use JSON format, hover, this file is auto-generated by **Bumped**.
+The file format is [CSON](https://github.com/bevry/cson). You can also use JSON format, however, this file is auto-generated by **Bumped**.
 
 ### .version
 
-If you're not sure what the current synchronized version across your configuration files is, then run `bumped version`:
+If you're not sure what the current synchronized version across your configuration files, then run `bumped version`:
 
 ```bash
 $ bumped version
@@ -160,10 +160,13 @@ info	: 'component.json' has been removed.
 
 The most interesting aspect in **Bumped** is the posibility to associate *hooks* before or after a release action. Usually, every time you releases a new version of your software, you always have to accomplish several tasks:
 - Run a grunt/gulp task to generate a build.
+- Lint the code.
 - Create a tagged version using `git`.
 - Push the code to a `git` repository.
 - Check if you are using dependencies with vulnerabilities using [NSP](https://nodesecurity.io).
 
+And, basically, whatever that you need.
+
 Due to the core is stable and usable, I decided to release early without this new feature. I just need a little bit of time!
 
 ## License

lib/Bumped.messages.coffee

@@ -16,6 +16,6 @@ module.exports =
   NOT_DETECTED_FILE   : (file) -> "'#{file}' hasn\'t been detected in the directory."
   NOT_VALID_VERSION   : (version) -> "version '#{version}' provided to release is not valid."
   NOT_GREATER_VERSION : (last, old) -> "version '#{last}' is not greater that the current '#{old}' version."
-  NOT_CURRENT_VERSION : -> 'There aren\'t a version declared.'
+  NOT_CURRENT_VERSION : -> 'There isn\'t version declared.'
   NOT_AUTODETECTED    : -> "It has been impossible to detect files automatically."
   NOT_AUTODETECTED_2  : -> "Try to add manually with 'add' command."