Improve documentation of settings

Author: GladeDiviney

README.md

@@ -52,7 +52,7 @@ The code is generated by combining each version part with a multiplier. Unspecif
 
 Intermediate versions do *not* produce a new code. The code only advances when a new version tag is specified.
 
-You can configure this behavior with `multipler` and `parts` properties, but be warned that changing the version code scheme for a released Android project can cause problems if your new version code does not [increase monotonically](http://developer.android.com/tools/publishing/versioning.html).
+You can configure this behavior with `multiplier` and `parts` properties, but be warned that changing the version code scheme for a released Android project can cause problems if your new version code does not [increase monotonically](http://developer.android.com/tools/publishing/versioning.html).
 
 ## Methods
 
@@ -86,12 +86,12 @@ androidGitVersion {
 ```
 
 ### prefix (string)
-Set a tag prefix to indicate that relevant version tags will start with the specified string. For example, with `prefix 'lib'`, a tags like `lib-1.5` will be found while a tag like `1.0` or `app-2.4.2` will be ignored.
+`prefix` sets the required prefix for any relevant version tag. For example, with `prefix 'lib'`, the tag `lib-1.5` is used to determine the version, while tags `1.0` are `app-2.4.2` are ignored.
 
-The default for prefix is `''` which matches all numeric version tags.
+The default prefix is `''`, which matches all numeric version tags.
 
 ### onlyIn (string)
-Set the onlyIn path to indicate a path within your project. Commits that change files in this path will count, while other commits will not. This is useful when building a versioned library from a git project containing other projects (apps and other libraries).
+`onlyIn` sets the required path for relevant files. Commits that change files in this path will count, while other commits will not.
 
 For example, consider this directory tree:
 ```
@@ -105,12 +105,12 @@ For example, consider this directory tree:
         +-- build.gradle
         +-- src/
 ```
-If a commit is tagged with `1.0.1`, and `my-app/lib/build.gradle` is configured with `onlyIn 'lib'`, then commits that change `my-app/build.gradle` or `my-app/app/src` will not affect the version name or code generated from `my-app/lib/build.gradle`.
+If `my-app/lib/build.gradle` is configured with `onlyIn 'lib'`, then changes to files in other paths (like `my-app/build.gradle` or `my-app/app/src`) will not affect the version name.
 
-The default onlyIn path is `''`, which includes all commits that change files.
+The default onlyIn path is `''`, which includes all paths.
 
 ### multiplier (int)
-Changes the multipler used to combine each part of the version number.
+`multiplier` sets the space allowed each part of the version when calculating the version code.
 
 For example, if you want version 1.2.3 to have a version code of 100020003 (allowing for 9999 patch increments), use `multiplier 10000`.
 
@@ -119,7 +119,7 @@ Use caution when increasing this value, as the maximum version code is 214748364
 The default multiplier is 1000.
 
 ### parts (int)
-Changes the assumed number of parts.
+`parts` sets the number of parts the version number will have.
 
 For example, if you know your product will only ever use two version number parts (1.2) then use `parts 2`.
 
@@ -128,15 +128,14 @@ Use caution when increasing this value, as the maximum version code is 214748364
 The default number of parts is 3.
 
 ### baseCode (int)
-A base version code added to all generated version codes. Use this when you have already released a version with a code, and don't want to go backwards.
+`baseCode` set a floor for all generated version codes. Use this when you have already released a version with a code, and don't want to go backwards.
 
 The default baseCode is 0.
 
 ### hideBranches (list of strings)
+`hideBranches` sets the branches which should *not* be mentioned explicitly when building intermediate versions (that is, versions without a tag). This will result in somewhat cleaner intermediate version names.
 
-A list of branches which should *not* be added to builds for intermediate (non-tagged) commits. This will result in somewhat cleaner intermediate version names.
-
-The default hideBranches are `[ 'master', 'release' ]`.
+The default hideBranches are `[ 'master', 'release' ]`, meaning that intermediate builds will not show these branch names.
 
 ## License