Fix some documentation typos

svn path=/trunk/; revision=7707

docs/reference/gobject/tut_gobject.xml

@@ -725,7 +725,7 @@ g_object_set (G_OBJECT (foo),
       <para>
         These high level functions have one drawback - they don't provide a return result.
         One should pay attention to the argument types and ranges when using them.
-        A know source of errors is to e.g. pass a gfloat instead of a gdouble and thus
+        A known source of errors is to e.g. pass a gfloat instead of a gdouble and thus
         shifting all subsequent parameters by four bytes. Also forgetting the terminating
         NULL will lead to unexpected behaviour.
       </para>

docs/reference/gobject/tut_gsignal.xml

@@ -501,7 +501,7 @@ void                  g_signal_emit_by_name (gpointer            instance,
 	  <para>
 		This completely optional filtering mechanism is mainly used as an optimization for signals
 		which are often emitted for many different reasons: the clients can filter out which events they are
-		interested into before the closure's marshalling code runs. For example, this is used extensively
+		interested in before the closure's marshalling code runs. For example, this is used extensively
 		by the <emphasis>notify</emphasis> signal of GObject: whenever a property is modified on a GObject,
 		instead of just emitting the <emphasis>notify</emphasis> signal, GObject associates as a detail to this
 		signal emission the name of the property modified. This allows clients who wish to be notified of changes

docs/reference/gobject/tut_howto.xml

@@ -319,7 +319,7 @@ G_DEFINE_TYPE (MamanBar, maman_bar, G_TYPE_OBJECT);
 static void
 maman_bar_init (MamanBar *self)
 {
-  self->private = MAMAN_BAR_GET_PRIVATE (self); 
+  self->priv = MAMAN_BAR_GET_PRIVATE (self); 
 
   /* initialize all public and private members to reasonable default values. */