[gmime: 17/24] Fix typos

[Jeffrey Stedfast <fejj src gnome org>]

commit 2f19c71ffedaf7a4383fae8665fcc005ead5b492
Author: Jakub Wilk <jwilk jwilk net>
Date:   Mon Jul 31 12:47:12 2017 +0200

    Fix typos

 PORTING                         |    2 +-
 README.md                       |    2 +-
 docs/reference/building.sgml    |    2 +-
 docs/reference/changes-2.2.sgml |    2 +-
 docs/reference/streams.sgml     |    2 +-
 docs/tutorial/gmime-tut.sgml    |    4 ++--
 6 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/PORTING b/PORTING
index 69106cf..a6e1671 100644
--- a/PORTING
+++ b/PORTING
@@ -299,7 +299,7 @@ header this is supposed to encode. If you haven't guessed, this
 function is for encoding rfc822 'text' headers (such as Subject).
 
 - g_mime_utils_8bit_header_encode_phrase() has been renamed to
-g_mime_utils_header_encode_phrase() mostly for consistancy with the
+g_mime_utils_header_encode_phrase() mostly for consistency with the
 previous 2 changes.
 
 - g_mime_charset_name() has been renamed to
diff --git a/README.md b/README.md
index 8197e0e..681f2f3 100644
--- a/README.md
+++ b/README.md
@@ -615,7 +615,7 @@ S/MIME).
 
 Because the `multipart/signed` part may have been signed by multiple signers, the
 `g_mime_multipart_signed_verify()` function returns a `GMimeSignatureList` which contains a list of
-digital signatures (one for each signer) that each contain their own metdata describing who that
+digital signatures (one for each signer) that each contain their own metadata describing who that
 signer is and what the status of their signature is.
 
 ```c
diff --git a/docs/reference/building.sgml b/docs/reference/building.sgml
index 712d36f..9eb4c26 100644
--- a/docs/reference/building.sgml
+++ b/docs/reference/building.sgml
@@ -162,7 +162,7 @@
         <para>
          The GLib library provides core non-graphical functionality
          such as high level data types, Unicode manipulation, and
-         a object and type system to C programs. It is available
+         an object and type system to C programs. It is available
          from the <ulink url="ftp://ftp.gtk.org/pub/gtk/v2.0/";>GTK+
          FTP site.</ulink>
        </para>
diff --git a/docs/reference/changes-2.2.sgml b/docs/reference/changes-2.2.sgml
index b09f308..312b7ef 100644
--- a/docs/reference/changes-2.2.sgml
+++ b/docs/reference/changes-2.2.sgml
@@ -46,7 +46,7 @@ headers (such as Subject).</para>
         <para>
 <function>g_mime_utils_8bit_header_encode_phrase()</function> has been
 renamed to <function>g_mime_utils_header_encode_phrase()</function>
-mostly for consistancy with the previous 2 changes.</para>
+mostly for consistency with the previous 2 changes.</para>
       </listitem>
       <listitem>
         <para>
diff --git a/docs/reference/streams.sgml b/docs/reference/streams.sgml
index 88c39fc..9967fdc 100644
--- a/docs/reference/streams.sgml
+++ b/docs/reference/streams.sgml
@@ -13,7 +13,7 @@
     <para>Streams are the fundamental method for reading and writing
     data used by GMime. You'll probably notice that the basic API is 
     similar to that of the low-level Unix I/O layer (read(), write(), 
-    lseek(), etc) with some additional nicities such as a printf-like 
+    lseek(), etc) with some additional niceties such as a printf-like 
     function.</para>
 
     <para>The three (3) basic stream types are: GMimeStreamFile,
diff --git a/docs/tutorial/gmime-tut.sgml b/docs/tutorial/gmime-tut.sgml
index 52a5226..c78ea91 100644
--- a/docs/tutorial/gmime-tut.sgml
+++ b/docs/tutorial/gmime-tut.sgml
@@ -178,7 +178,7 @@ int main (int argc, char **argv)
       of the above examples is the flushing of the stream after
       writing to it. Most likely, in both examples, it is an unneeded
       call, however it is there for completeness and you should
-      probably get into the habbit of flushing a stream after you've
+      probably get into the habit of flushing a stream after you've
       finished writing to it. Like fflush(), g_mime_stream_flush()
       will flush any write-buffers that the previous write-calls may
       have left.</para>
@@ -345,7 +345,7 @@ void g_mime_stream_mem_set_owner (GMimeStreamMem *stream, gboolean owner);
       own.</para>
       
       <para>We've already seen GMimeStreamFile and GMimeStreamFs in
-      action in the prevous chapter, so let's skip them and start with
+      action in the previous chapter, so let's skip them and start with
       GMimeStreamMem.</para>
       
       <para>GMimeStremMem is a stream abstraction that reads and