Updated readme

README.md

@@ -36,7 +36,7 @@ Microsoft Windows is supported via MSYS or Cygwin.
 Osync has been designed to not delete any data, but rather make backups of conflictual files or soft deletes.
 Nevertheless, you should always have a neat backup of your data before trying a new sync tool.
 
-You can download the latest stable release of Osync at www.netpower.fr/osync or https://github.com/deajan/osync/archive/v1.1.tar.gz
+You can download the latest stable release of osync at https://github.com/deajan/osync/archive/v1.1.2.tar.gz
 
 You may also get the last development version at https://github.com/deajan/osync with the following command
 
@@ -58,9 +58,9 @@ On MSYS, On top of your basic install, you need msys-rsync and msys-coreutils-ex
 Since osync v1.1 the config file format has changed in semantics and adds new config options.
 Also, master is now called initiator and slave is now called target.
 
-You can upgrade all v1.0x-v1.1-dev config files by running the upgrade script
+You can upgrade all v1.0x-v1.2-dev config files by running the upgrade script
 
-	$ ./upgrade-v1.0x-v1.1x.sh /etc/osync/your-config-file.conf
+	$ ./upgrade-v1.0x-v1.2x.sh /etc/osync/your-config-file.conf
 
 The script will backup your config file, update it's content and try to connect to initiator and target replicas to update the state dir.
 
@@ -136,7 +136,7 @@ Systemd specific (one service per config file)
 
 Contributions
 -------------
-Bug fixes and ideas are welcome. When submitting a PR, please be sure to modify dev/n_osync.sh & dev/ofunctions.sh instead of osync.sh which is overwritten on every commit.
+Bug fixes and ideas are welcome. When submitting a PR, please be sure to modify files in dev directory (dev/n_osync.sh & dev/ofunctions.sh) instead of osync.sh which are autogenerated.
 Consider reading CODING_STYLE.TXT before submitting a patch.
 
 Troubleshooting