cgeo
diff --git a/Diff for: ‎README.md
+3-4 b/Diff for: ‎README.md
+3-4
diff --git a/Diff for: ‎chrome-extension/manifest.json
-17 b/Diff for: ‎chrome-extension/manifest.json
-17
diff --git a/Diff for: ‎chrome-extension/send2cgeo.48.png
-3.98 KB b/Diff for: ‎chrome-extension/send2cgeo.48.png
-3.98 KB
diff --git a/Diff for: ‎chrome-extension/send2cgeo.64.png
-5.83 KB b/Diff for: ‎chrome-extension/send2cgeo.64.png
-5.83 KB
diff --git a/Diff for: ‎chrome-extension/send2cgeo.user.js
-107 b/Diff for: ‎chrome-extension/send2cgeo.user.js
-107
diff --git a/Diff for: ‎firefox-addon/send2cgeo/data/LICENSE
-202 b/Diff for: ‎firefox-addon/send2cgeo/data/LICENSE
-202
diff --git a/Diff for: ‎firefox-addon/send2cgeo/data/NOTICE
-10 b/Diff for: ‎firefox-addon/send2cgeo/data/NOTICE
-10
diff --git a/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.48.png
-3.98 KB b/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.48.png
-3.98 KB
diff --git a/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.64.png
-5.83 KB b/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.64.png
-5.83 KB
diff --git a/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.user.js
-1 b/Diff for: ‎firefox-addon/send2cgeo/data/send2cgeo.user.js
-1
diff --git a/Diff for: ‎firefox-addon/send2cgeo/lib/main.js
-8 b/Diff for: ‎firefox-addon/send2cgeo/lib/main.js
-8
diff --git a/Diff for: ‎firefox-addon/send2cgeo/package.json
-17 b/Diff for: ‎firefox-addon/send2cgeo/package.json
-17
@@ -1,10 +1,9 @@
 # send2cgeo
 
-Script for Mozilla Firefox and Google Chrome browser to send geocaches directly from your browser to c:geo on your phone.
+Script for Mozilla Firefox and Google Chrome browser to [send geocaches directly from your browser to c:geo](http://www.cgeo.org/send2cgeo.html) on your phone.
 
 ## Version management
 
-Changes should be based on the `master` branch.
-Once the changes are validated and ready to release, the changes should be merged to the `release` branch. This merge has to include a raise of the script version number.
+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 within that merge.
 
-The script download link on the c:geo homepage directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will get the update.
+The script download link on the [c:geo homepage](http://cgeo.org) directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will see the update.