KEP-0005.txt

[Jeroen van Meeuwen]

 KEP-0005.txt |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

New commits:
commit 18e69b60771dcdaf45e55be71c0fac44a817f8f3
Author: Alex Potter <alex at ap-consulting.co.uk>
Date:   Tue Mar 15 20:06:29 2011 +0000

    Patch from Alex Potter to fix spelling and clumsy construction

diff --git a/KEP-0005.txt b/KEP-0005.txt
index 63ab1d8..1c2c25f 100644
--- a/KEP-0005.txt
+++ b/KEP-0005.txt
@@ -30,7 +30,7 @@ An increment of the Major component of the version is often associated with a la
 
 The Major component in the product versioning shema '''MUST''' be incremented in any of the following situations;
 
-* No seemless (e.g. automatic without intervention, guaranteed) upgrade path exists,
+* No seamless (e.g. automatic without intervention, guaranteed) upgrade path exists,
 * No downgrade path exists (for purposes of failed upgrade rollbacks),
 * Manual intervention is required altering data (conversion of objects),
 * Changes to the product that entail '''functional changes''', e.g. a change in how the product works or how administrators or users can, should or must work with the product,
@@ -42,7 +42,7 @@ The Major component '''MAY''' be incremented in any of the following situations;
 * To mark a point in time the versioning starts to conform to the guidelines documented here,
 * Based on community and/or release engineering/management consensus.
 
-However, seeing as how incrementing the major version raises expectations and workload on the receiving end of the product, careful consideration is warranted.
+However, because incrementing the major version raises expectations and workload on the receiving end of the product, careful consideration is warranted.
 
 === The Minor Version Component ===
 
@@ -58,7 +58,7 @@ An increment of the Minor component of the version usually warrants the followin
 The Minor component in the product versioning schema '''MUST''' be incremented in any of the following situations;
 
 * Feature enhancements that require additional configuration or setup are included in the release,
-* Despite whether the release contains only bug-fixes, the upgrade path is not seemless,
+* Despite whether the release contains only bug-fixes, the upgrade path is not seamless,
 * Backwards compatibility is being marked deprecated in any ABI, API or configuration, and as such issues warnings in a reasonable fashion,
 * Any of the components are upgraded, whether automatically or not.
 
@@ -70,7 +70,7 @@ The Minor component in the product versioning schema '''MAY''' be incremented in
 
 === The Teeny Version Component ===
 
-The Teeny Version '''SHALL''' only be incremented for bug-fix releases. Included with bug-fix releases are, of course, security fixes. The ''update'' '''MUST''' be seemless.
+The Teeny Version '''SHALL''' only be incremented for bug-fix releases. Included with bug-fix releases are, of course, security fixes. The ''update'' '''MUST''' be seamless.
 
 === Release ===