From 687f3d78d6b1fe1fb03980c70537bea331bbcf28 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=98yvind=20Kol=C3=A5s?= <pippin@gimp.org>
Date: Wed, 22 Jun 2005 09:49:48 +0000
Subject: [PATCH] minor whitespace and spellfix

---
 ChangeLog                        | 4 ++++
 doc/public/language-bindings.xml | 4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 727f83fbd..d9394cc1b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2005-06-22  Øyvind Kolås  <pippin@freedesktop.org>
+
+	* doc/public/language-bindings.xml: spelling and whitespace fix.
+
 2005-06-21  Kristian Høgsberg  <krh@redhat.com>
 
 	* src/cairo-pdf-surface.c: Split out font subsetting code from here,
diff --git a/doc/public/language-bindings.xml b/doc/public/language-bindings.xml
index 1b999d82f..b0ee8e879 100644
--- a/doc/public/language-bindings.xml
+++ b/doc/public/language-bindings.xml
@@ -418,7 +418,7 @@ public void writeToPNG (OutputStream stream) throws IOException;
       </para></listitem>
       <listitem><para>
 	  Constructors, rather than
-	  returning<constant>NULL</constant> on out-of-memory failure,
+	  returning <constant>NULL</constant> on out-of-memory failure,
 	  return a special singleton object on which all
 	  operations do nothing. Retrieving the status of the
 	  singleton object returns <constant>CAIRO_STATUS_NO_MEMORY</constant>
@@ -534,7 +534,7 @@ cairo_pattern_t
       Like patterns, surfaces, which use only the
       <link
       linkend="cairo-surface-t"><type>cairo_surface_t</type></link>
-      type in the C API should be broken up into a heirarchy of types
+      type in the C API should be broken up into a hierarchy of types
       in a language binding.
     </para>
     <programlisting>