[DOCS] Slight change in the version scheme

Signed-off-by: Anup Patel <anup@brainfault.org>

docs/VersionScheme

@@ -10,15 +10,17 @@ The Xvisor Version Scheme is as follow:
     We write this in following format: 
                <major> . <minor> . <release>
  2. We will increase <release> number after 5+ feature additions. 
-    The addition of new port, driver, emulator, library, command, and daemonts
+    The addition of new port, driver, emulator, library, command, and daemons 
     will also be considered as new feature.
- 3. The range of <release> number will be 0 to 2 (i.e 0, 1 and 2). 
-    After <release>=2 we will increase <minor> number and set <release> to 0.
- 4. There will be no limit on <minor> release number, it will keep increasing.
+ 3. There is no limit on <release> number, it will keep increasing.
+    The <release> number will be reset 0 only when we increment <minor> number.
+ 4. We will increase <minor> number on reaching a milestone. Examples of
+    milestones could be First release, SMP support, Network support, etc.
+ 5. There is no limit on <minor> number, it will keep increasing.
     The <minor> number will be reset 0 only when we increment <major> number.
- 5. Increasing <major> number will be based on discussions on xvisor-devel 
+ 6. Increasing <major> number will be based on discussions on xvisor-devel 
     mailing list.
 
-In the above, points 2 and 3 are based on our current pace of development. 
-In future, we will keep adapting points 2 and 3 based on pace of development 
-at that time such that <minor> number will increase at a steady rate.
+In the above, point 2 is based on our current pace of development. 
+In future, we will keep adapting point 2 based on pace of development at that 
+time such that <release> number will increase at a steady rate.