Some corrections, to make the RELEASEME file more comprehensible.

RELEASEME.md

@@ -25,7 +25,7 @@ Set of instructions to become able to release the ha-jobs project to maven centr
  * First of all, if you did not for other projects, you have to generate a [GPG Key](https://www.gnupg.org/gph/en/manual/c14.html).
  * to check which keys you own private keys for: gpg --list-secret-keys
  * generate the key: gpg --gen-key
- * send the public key to a keyserver: gpg --send-keys ID4711AA (replace ID4711AA with your own key id), if the default 
+:wq * send the public key to a keyserver: gpg --send-keys ID4711AA (replace ID4711AA with your own key id), if the default 
    server does not work try to specify a server yourself, e.g.: gpg --keyserver hkp://pool.sks-keyservers.net --send-keys ID4711AA (replace ID4711AA with your own key id), if the default
  * check if your key has been uploaded/synchronized: gpg --recv-keys ID4711AA (replace ID4711AA with your own key id)
 
@@ -36,11 +36,6 @@ Set of instructions to become able to release the ha-jobs project to maven centr
  * Request for publishing permissions in the group "de.kaufhof" via jira ticket
  * to learn how to use sonatype with your credentials, check [this](http://www.scala-sbt.org/0.13/docs/Using-Sonatype.html#Fourth+-+Adding+credentials)
 
-### SBT-PGP Plugin
-
- * add `addSbtPlugin("com.typesafe.sbt" % "sbt-pgp" % "0.8")`to your project's build.sbt, this allows you to sign and publish your artefacts by running publishSigned in sbt
-
-
 ### Sonatype Credentials File
 
  * if not existing, create ~/.sbt/0.13/sonatype.sbt
@@ -66,34 +61,18 @@ Set of instructions to become able to release the ha-jobs project to maven centr
  * btw. builds from this project are made with travis, you can see an overview [here](https://travis-ci.org/Galeria-Kaufhof/ha-jobs) 
 
 
-## Snapshot Release
-
- * Instead of the final release, a snapshot release can be changed and released several times
- * a SNAPSHOT will NOT be released at maven central but at sonatype, where it can be used from
- * To build a SNAPSHOT go to your project build.sbt and change the projectVersion by increment the version number and 
-   add -SNAPSHOT behind (e.g. `projectVersion = "1.2.4-SNAPSHOT"`)
- * there are also version numbers mentioned in the README.md, change them also to the version number you used in the build.sbt
- * start sbt on your project root
- * publish the changes with `very publishSigned`
- * confirm the publish with the your gpg password when sbt asks you
-
-
 ## Final release
 
- * the final public release will go out to maven central and, therefore, cannot be released twice with the same version number
  * to build a regular release just increment the version number in your project build.sbt AND the README.md without adding
    -SNAPSHOT at the end. If you released a SNAPSHOT with this code stand before do not incremnt the verison number, just remove the
    -SNAPSHOT ending
  * start sbt on your project root
  * publish the changes with `very publishSigned`
  * confirm the publish with the your gpg password when sbt asks you
-
-
-## Sonatype
-
  * for the final release you have to sign in to [Sonatype](https://oss.sonatype.org) with your credentials
  * go to `Staging Repositories` on the left side
  * search for the kaufhof repo, click on it
- * close the repo (the button is at the menu bar above the repo table)
+ * close the repo (the button is at the menu bar above the repo table), `remember!` that closing the repo means no further 
+   release of this version is possible!
  * after the repo has been closed, press the release button
  * after 10-30 minutes your release should be distributed