--- a/devel-versioning.rst	Sat Sep 24 15:22:30 2011 +0300
+++ b/devel-versioning.rst	Sun Sep 25 16:08:12 2011 +0300
@@ -12,8 +12,8 @@
 Marketing versioning.
 =====================
 
-Marketing versioning schema used for marketing, advertising purpose. It is
-usually inconsistent and can changed over the time.
+Marketing versioning schema used for marketing, advertising, branding purpose.
+It is usually inconsistent and can changed over the time.
 
 Examples of marketing version schema:
 
@@ -53,18 +53,29 @@
  * rev (revision)
  * build
  * date
-::
+ * hotfix, fix
+
+Version components usually combined in such group::
 
+  major.minor.build
+  major.minor.date
+  major.minor.hotfix
+  major.minor.hotfix.build
   major.minor.rev
   major.minor.rev.build
   major.current.age
 
+Its conventional to have at least a major and minor number.
+
+Prefixing version with a "v" seems to be less common.
+
 Major version component.
 ------------------------
 
-Major number change means that the new version is incompatible with the old one
-and any dependent of the prior version will require code changes to upgrade to
-the new package.
+Major number change means that fundamental change made in the architecture of
+the system the new version is incompatible with the old one, upgrade between
+versions is non-trivial, and any dependent of the prior version will require
+code changes to upgrade to the new package.
 
 Major number rare changed (this can take a lot of year).
 
@@ -72,7 +83,8 @@
 ------------------------
 
 Minor number change means that the new version is backward compatible with the
-previous version but has significant enhancements over the previous version.
+previous version but has significant enhancements over the previous version
+(like new functionality or changed UI).
 
 Functional enhancement releases. Contain new or significantly changed
 functionality and/or layout.
@@ -82,8 +94,9 @@
 Revision, micro, bugfix version component.
 ------------------------------------------
 
-Revision number is updated whenever a bugfix is applied to the build such that
-it doesn't bring a compatibility change or introduce newer features.
+Revision number is updated whenever a bugfix or security patche is applied to
+the build such that it doesn't bring a compatibility change or introduce newer
+features.
 
 Patches are released frequently (sometimes daily).