Merge pull request #823 from nshenoy/patch-1

Update configuration.md

Author: gep13

docs/configuration.md

@@ -75,9 +75,9 @@ The options in here are:
  - **`prevent-increment-of-merged-branch-version:`** When `release-2.0.0` is merged into master, we want master to build `2.0.0`.
     If `release-2.0.0` is merged into develop we want it to build `2.1.0`, this option prevents incrementing after a versioned branch is merged
 
- - **`tag-number-pattern:`** Pull requests require us to pull the pre-release number out of the branch name so `refs/pulls/534/merge` builds as `PullRequest.5`.
+ - **`tag-number-pattern:`** Pull requests require us to pull the pre-release number out of the branch name so `refs/pulls/534/merge` builds as `PullRequest.534`.
    This is a regex with a named capture group called `number`
 
  - **`track-merge-target:`** Strategy which will look for tagged merge commits directly off the current branch. For example `develop` → `release/1.0.0` → merge into `master` and tag `1.0.0`. The tag is *not* on develop, but develop should be version `1.0.0` now.
 
-We don't envision many people needing to change most of these configuration values, but they are there if you need to.
+We don't envision many people needing to change most of these configuration values, but they are there if you need to.