[gnome-devel-docs/wip/swilmet/prog-guidelines] programming-guidelines: don't use the term "pre-release increment"

[Sébastien Wilmet <swilmet src gnome org>]

commit 8d69932115300af4c7969a3c8ef516cd1a2424b2
Author: Sébastien Wilmet <swilmet gnome org>
Date:   Sat Nov 7 15:12:06 2015 +0100

    programming-guidelines: don't use the term "pre-release increment"
    
    When reading the text, I first thought that it meant "pre-commit" and
    "post-commit". But the pre-commit is useless, it can be done at the same
    time as the release commit.
    
    Saying "at the time of release" is clearer in my opinion.

 programming-guidelines/C/versioning.page |   11 +++++------
 1 files changed, 5 insertions(+), 6 deletions(-)
---
diff --git a/programming-guidelines/C/versioning.page b/programming-guidelines/C/versioning.page
index 938d3bf..9b6edf3 100644
--- a/programming-guidelines/C/versioning.page
+++ b/programming-guidelines/C/versioning.page
@@ -42,7 +42,7 @@
         (<link xref="#application-versioning"/>)
       </p></item>
       <item><p>
-        Version numbers should be updated for each release (using pre- and
+        Version numbers should be updated for each release (using release and
         post-release increments). (<link xref="#release-process"/>)
       </p></item>
       <item><p>
@@ -162,14 +162,13 @@ AC_SUBST([LT_VERSION],[0:0:0])</code>
 
     <p>
       The standard process for making a release of a module increments the
-      libtool version (if the module is a library) immediately before release,
-      does the release, then increments the package version number immediately
-      afterwards. This is called pre-release increment for libtool versioning
-      and post-release increment for package versioning.
+      libtool version (if the module is a library) at the time of release, then
+      increments the package version number immediately afterwards (this is
+      called a post-release increment).
     </p>
 
     <p>
-      The use of pre-release increment for libtool versions means that they are
+      Updating the libtool versions at the time of release means that they are
       only incremented once for all ABI changes in a release. The use of
       post-release increment for package versions means the package version
       number is not outdated (still equal to the previous release) during