diff --git a/README.md b/README.md
index d5e3629..1f07757 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,7 @@ All commands are prefixed with `PackageControl:`.
 * Open the `Keypirinha: Console`
 * Enter the following:
     ```python
-    import keypirinha as kp,keypirinha_net as kpn,os;p="PackageControl.keypirinha-package";d=kpn.build_urllib_opener().open("https://github.com/ueffel/Keypirinha-PackageControl/releases/download/0.2.2/"+p);pb=d.read();d.close();f=open(os.path.join(kp.installed_package_dir(),p),"wb");f.write(pb);f.close()
+    import keypirinha as kp,keypirinha_net as kpn,os;p="PackageControl.keypirinha-package";d=kpn.build_urllib_opener().open("https://github.com/ueffel/Keypirinha-PackageControl/releases/download/0.3/"+p);pb=d.read();d.close();f=open(os.path.join(kp.installed_package_dir(),p),"wb");f.write(pb);f.close()
     ```
 
 ### Manually
@@ -56,9 +56,5 @@ overview of available packages can be viewed [here](https://ue.spdns.de/packagec
 If you created your own package and want it to be available via PackageControl to other Keypirinha
 users you can submit it [here](https://ue.spdns.de/packagecontrol/new_package). The preferred way of
 publishing is Github. Your package repository should have the ready-to-use `.keypirinha-package`
-file in the release section. The package repository looks for the newest release (not pre-release) 
+file in the release section. The package repository looks for the newest release (not pre-release)
 that has such a file und exposes it.
-
-(If I find the time for it I will clean up and publish the code for the package repository web app
-for everyone that wants his own package repository. It's a python wsgi application written with
-flask.)