[gnome-devel-docs] programming-guidelines: Fix a number of typos.

[Andre Klapper <aklapper src gnome org>]

commit 4771dc6450f3280b2e6a3f1896cf754d2fb34218
Author: Sebastian Rasmussen <sebras gmail com>
Date:   Wed Jan 4 21:22:26 2017 +0100

    programming-guidelines: Fix a number of typos.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=776878

 programming-guidelines/C/documentation.page |    2 +-
 programming-guidelines/C/main-contexts.page |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/programming-guidelines/C/documentation.page b/programming-guidelines/C/documentation.page
index 3a5f6cd..6fc2538 100644
--- a/programming-guidelines/C/documentation.page
+++ b/programming-guidelines/C/documentation.page
@@ -377,7 +377,7 @@ gtk_get_flow (GtkWidget *widget)
     <p>
       gtk-doc comes with support for checking the documentation with some basic
       tests. These check that all version indexes are included in the main
-      <file>*-docs.xml</file> file and that all symbols are documented, amongst
+      <file>*-docs.xml</file> file and that all symbols are documented, among
       other things.
     </p>
 
diff --git a/programming-guidelines/C/main-contexts.page b/programming-guidelines/C/main-contexts.page
index de3b2f5..2bc60af 100644
--- a/programming-guidelines/C/main-contexts.page
+++ b/programming-guidelines/C/main-contexts.page
@@ -828,7 +828,7 @@ g_assert (g_main_context_is_owner (expected_main_context));</code>
       If that’s put at the top of each function, any assertion failure will
       highlight a case where a function has been called from the wrong
       thread. It is much easier to write these assertions when initially
-      developing code, rather than debuging race conditions which can easily
+      developing code, rather than debugging race conditions which can easily
       result from a function being called in the wrong thread.
     </p>