[gtk+] docs: Some style fixes to the migration guide

[Benjamin Otte <otte src gnome org>]

commit 416d132a72798d9f8af58ad73747cd4f0c935855
Author: Benjamin Otte <otte redhat com>
Date:   Wed Aug 11 05:12:49 2010 +0200

    docs: Some style fixes to the migration guide
    
    Most importantly, I decided to not capitalize "cairo".

 docs/reference/gtk/migrating-2to3.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/docs/reference/gtk/migrating-2to3.xml b/docs/reference/gtk/migrating-2to3.xml
index 1652177..389a578 100644
--- a/docs/reference/gtk/migrating-2to3.xml
+++ b/docs/reference/gtk/migrating-2to3.xml
@@ -6,7 +6,7 @@
   <title>Migrating from GTK+ 2.x to GTK+ 3</title>
 
   <para>
-    GTK+ 3 is a major new version of GTK+, which breaks both API and ABI
+    GTK+ 3 is a major new version of GTK+ that breaks both API and ABI
     compared to GTK+ 2.x, which has remained API- and ABI-stable for a
     long time. Thankfully, most of the changes are not hard to adapt to
     and there are a number of steps that you can take to prepare your
@@ -96,7 +96,7 @@
   </section>
 
   <section>
-  <title>Use accessor functions instead direct access</title>
+  <title>Use accessor functions instead of direct access</title>
   <para>
     GTK+ 3 removes many implementation details and struct members from
     its public headers.
@@ -181,7 +181,7 @@ gdk_gc_set_tile (gc, NULL);
 gdk_gc_set_fill (gc, GDK_SOLID);
 gdk_gc_set_ts_origin (gc, 0, 0);
 ]]></programlisting>
-          The equivalent Cairo code looks like this:
+          The equivalent cairo code looks like this:
 <programlisting><![CDATA[
 cairo_t *cr;
 
@@ -213,7 +213,7 @@ gdk_draw_layout (drawable, gc, x, y, layout);
 /* restore */
 gdk_gc_set_clip_rectangle (gc, NULL);
 ]]></programlisting>
-          With Cairo, the same effect can be achieved using:
+          With cairo, the same effect can be achieved using:
 <programlisting><![CDATA[
 cairo_t *cr;