# HG changeset patch
# User Oleksandr Gavenko <gavenkoa@gmail.com>
# Date 1322429307 -7200
# Node ID 97e0815972e0ea0a73353e99324d5a945a3bf0fd
# Parent  db420d97136348a96d711a4780058c31fbade063
Switching from old to new require upgrade.

diff -r db420d971363 -r 97e0815972e0 devel-versioning.rst
--- a/devel-versioning.rst	Sun Nov 27 23:21:26 2011 +0200
+++ b/devel-versioning.rst	Sun Nov 27 23:28:27 2011 +0200
@@ -140,12 +140,13 @@
 
 Versioning for products differ from versioning for libraries.
 
-Product is a set of conponents fixed to some versions. Components can be
+Product is a set of conponents that stalled to some versions. Components can be
 switches as written for library versioning:
 
- * Any fix release interchanged.
- * Any minor release interchanged starting from some minor.
- * Major release does not interchanged at all.
+ * Any fix releases interchanged, greater version mean less bug count.
+ * Any minor release interchanged with next minor releases.
+ * Major release does not interchanged at all, switching from old to new require
+   upgrade.
 
 Product update vs upgrade.
 --------------------------
@@ -155,11 +156,11 @@
  * Replacing product executable files, resources files.
  * Config files and user data stay unchanged.
 
-Product update involve:
+Product upgrade involve:
 
  * Replacing product executable files, resources files.
  * Config files and used data require modification and performed by upgrade
-   scripts or manually by user.
+   scripts or manually by user (if this is ever possible).
 
 Release build version data.
 ===========================