update documentation to reflect the new implementation

Author: Simon Ejsing

docs/configuration.md

@@ -79,13 +79,10 @@ 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.534`.
-   This is a regex with a named capture group called `number`
-
- - **`tag-name-pattern:`** This is similar to `tag-number-pattern` but instead of using the pull request number as the number part of the prerelease tag, the number is instead appended to the tag.
-   This is only applicable when the branch mode is set to ContinuousDeployment, where the prerelease tag number part is based on the number of commits since the last tag.
-   It enables consecutive commits to the pull request branch to generate unique full semantic version numbers when the branch is configured to use ContinuousDeployment mode and this value is set.
-   This is a regex with a named capture group called `number`.  
+ - **`tag-number-pattern:`** Pull requests require us to extract 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`  
+   If the branch mode is set to ContinuousDeployment, then the extracted `number` is appended to the name of the pre-release tag and the number portion is the number of commits since the last tag.
+   This enables consecutive commits to the pull request branch to generate unique full semantic version numbers when the branch is configured to use ContinuousDeployment mode.  
    Example usage:
 ```yaml
 branches: