docs: fix wording

tsvetomir · web-flow · commit ba3154808109 · 2017-06-12T10:08:44.000+03:00
diff --git a/README.md b/README.md
@@ -47,4 +47,4 @@ With the above setup, new official releases (bearing the `latest` dist-tag) can
 
     git checkout master && git merge --ff-only develop && git push
 
-> Your first official release will be published with version 0.1.0 to enable automatic releases during initial development. You must mark a commit as a [major release](https://github.com/semantic-release/semantic-release#major-breaking-release) to release bump the major version to 1. This is different than vanilla semantic-release where your first release is 1.0.0
+> Your first official release will be published with version 0.1.0 to enable automatic releases during initial development. You must mark a commit as a [major release](https://github.com/semantic-release/semantic-release#major-breaking-release) to bump the major version to 1. This is different than vanilla semantic-release where your first release is 1.0.0

Original file line number	Diff line number	Diff line change
@@ -47,4 +47,4 @@ With the above setup, new official releases (bearing the `latest` dist-tag) can
`47`	`47`
`48`	`48`	`git checkout master && git merge --ff-only develop && git push`
`49`	`49`
`50`		`-> Your first official release will be published with version 0.1.0 to enable automatic releases during initial development. You must mark a commit as a [major release](https://github.com/semantic-release/semantic-release#major-breaking-release) to release bump the major version to 1. This is different than vanilla semantic-release where your first release is 1.0.0`
	`50`	`+> Your first official release will be published with version 0.1.0 to enable automatic releases during initial development. You must mark a commit as a [major release](https://github.com/semantic-release/semantic-release#major-breaking-release) to bump the major version to 1. This is different than vanilla semantic-release where your first release is 1.0.0`