Clarification for update mechanism #2

Lineflyer · web-flow · commit 61ab718349b2 · 2020-01-08T23:07:41.000+01:00
diff --git a/README.md b/README.md
@@ -6,4 +6,4 @@ Script for Mozilla Firefox and Google Chrome browser to [send geocaches directly
 
 Changes must be done on the `master` branch. Once the changes are validated and ready to release, they can be merged to the `release` branch. The script version number needs to be raised after that merge to roll it out.
 
-The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.
+The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release`, together with the required version number increase, users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.

Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,4 @@ Script for Mozilla Firefox and Google Chrome browser to [send geocaches directly`
`6`	`6`
`7`	`7`	Changes must be done on the `master` branch. Once the changes are validated and ready to release, they can be merged to the `release` branch. The script version number needs to be raised after that merge to roll it out.
`8`	`8`
`9`		-The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.
	`9`	+The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release`, together with the required version number increase, users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.