RELEASING.md in ruby-enum-0.8.0 vs RELEASING.md in ruby-enum-0.9.0

@@ -1,8 +1,8 @@
 # Releasing Ruby-Enum
 
-There're no hard rules about when to release ruby-enum. Release bug fixes frequently, features not so frequently and breaking API changes rarely.
+There are no hard rules about when to release ruby-enum. Release bug fixes frequently, features not so frequently and breaking API changes rarely.
 
 ### Release
 
 Run tests, check that all tests succeed locally.
 
@@ -11,29 +11,23 @@
 rake
 ```
 
 Check that the last build succeeded in [Travis CI](https://travis-ci.org/dblock/ruby-enum) for all supported platforms.
 
-Increment the version, modify [lib/ruby-enum/version.rb](lib/ruby-enum/version.rb).
+Add a date to this release in [CHANGELOG.md](CHANGELOG.md).
 
-*  Increment the third number if the release has bug fixes and/or very minor features, only (eg. change `0.2.1` to `0.2.2`).
-*  Increment the second number if the release contains major features or breaking API changes (eg. change `0.2.1` to `0.3.0`).
-
-Change "Next Release" in [CHANGELOG.md](CHANGELOG.md) to the new version.
-
 ```
-### 0.2.2 (7/10/2015)
+### 0.2.2 (2015/7/10)
 ```
 
 Remove the line with "Your contribution here.", since there will be no more contributions to this release.
 
 Commit your changes.
 
 ```
 git add README.md CHANGELOG.md lib/ruby-enum/version.rb
 git commit -m "Preparing for release, 0.2.2."
-git push origin master
 ```
 
 Release.
 
 ```
@@ -48,11 +42,10 @@
 ### Prepare for the Next Version
 
 Add the next release to [CHANGELOG.md](CHANGELOG.md).
 
 ```
-Next Release
-============
+### 0.2.3 (Next)
 
 * Your contribution here.
 ```
 
 Increment the third version number in [lib/ruby-enum/version.rb](lib/ruby-enum/version.rb).