Make required post-relase version bump more obvious

... plus small styling fixes.

devel-docs/release-howto.txt

@@ -91,6 +91,10 @@
      to the next odd micro and commit this change. GIT versions always
      have odd micro numbers.
 
+     [ ] In configure.ac, modify gimp_micro_version accordingly.
+
+     [ ] In configure.ac, modify gimp_interface_age accordingly.
+
  ( ) Publish dist tarballs:
 
      [ ] Use md5sum to create a checksum of the tarball (tar.bz2).
@@ -106,9 +110,9 @@
          on the download server.
 
      [ ] Change permissions of the new files to make them writable by
-       	 the 'gimpadmins' group. This will allow other members of this
-       	 group to correct mistakes and to update the 0.0_LATEST-IS-
-       	 file next time.
+         the 'gimpadmins' group. This will allow other members of this
+         group to correct mistakes and to update the 0.0_LATEST-IS-
+         file next time.
 
  ( ) Add the new version to the GIMP product on bugzilla.gimp.org.
 
@@ -121,8 +125,8 @@
      [ ] Create a news items for the release in content/news/
 
      [ ] Commit and push the changes, the web server should then
-         update itself soon (every 5 minutes). Go to
-         https://testing.gimp.org to verify the changes.
+         update itself soon (it checks for updates every 5 minutes).
+         Go to https://testing.gimp.org to verify the changes.
 
  ( ) Grab a properly chilled beverage and enjoy yourself.
 
@@ -134,8 +138,8 @@
          the changes you did in the testing branch.
 
      [ ] Push the changes, the web server should then update itself
-         soon (every 15 minutes). Got to https://www.gimp.org to
-         verify the changes.
+         soon (it checks for updates every 15 minutes).
+         Go to https://www.gimp.org to verify the changes.
 
      [ ] Due to the tendency of news sites to front-run release
          articles even before actual announcements appear, publish