Improve "Next steps" in README

Try to show user also "why" they might want to do it.

README.md

 The tutorial above has been cut down to really only show the most common
 features.  What you might want to do next:
 
- *  Add SPEC file and debian dir templates,
+ *  Add SPEC file and debian dir templates (adding `make rpmstuff` and
+    `make debstuff` under your belt).
 
  *  Add tokens inside some of your scripts to include stuff known
-    only on install time (versions, paths...)
+    only at install time (versions, paths...) so that your application
+    can report --version as accurately as possible.
 
- *  Do some actual development (branch off, do scratch builds, experiment).
+ *  Do some actual development (branch off, do scratch builds, experiment)
+    and see how MKit handles versioning.
 
 MKit uses SemVer so version reflected in tarbal naming, packaging
 files and tokens contains enough data to track it back to actual commit.