[gnome-devel-docs/wip/swilmet/prog-guidelines] programming-guidelines: fixes in the API stability page

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

commit 36c4f32549ee0b2b264e62861ff5262073aa780e
Author: Sébastien Wilmet <swilmet gnome org>
Date:   Sat Nov 7 16:10:27 2015 +0100

    programming-guidelines: fixes in the API stability page
    
    When the API breaks, the major number is incremented, not the minor
    version.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=757735

 programming-guidelines/C/api-stability.page |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/programming-guidelines/C/api-stability.page b/programming-guidelines/C/api-stability.page
index 0f14117..f89d54e 100644
--- a/programming-guidelines/C/api-stability.page
+++ b/programming-guidelines/C/api-stability.page
@@ -84,10 +84,10 @@
       without worrying about constantly updating their code to keep up with
       API changes. Typical API stability guarantees mean that code which is
       compiled against one version of a library will run without problems
-      against all future versions of that library with the same minor version
+      against all future versions of that library with the same major version
       number — or similarly that code which runs against a daemon will
       continue to run against all future versions of that daemon with the same
-      minor version number.
+      major version number.
     </p>
 
     <p>