[perl-Glib] Fix typos

[Torsten Schönfeld <tsch src gnome org>]

commit 7dcbd1f597d8fcbb13b0e026329b6be400ca2293
Author: intrigeri <intrigeri boum org>
Date:   Sat Jan 2 10:14:00 2016 +0000

    Fix typos
    
    https://bugzilla.gnome.org/show_bug.cgi?id=760065

 lib/Glib/GenPod.pm          |    2 +-
 lib/Glib/MakeHelper.pm      |    2 +-
 lib/Glib/Object/Subclass.pm |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/lib/Glib/GenPod.pm b/lib/Glib/GenPod.pm
index 2dd2bd2..1187fda 100644
--- a/lib/Glib/GenPod.pm
+++ b/lib/Glib/GenPod.pm
@@ -1126,7 +1126,7 @@ So, in general, you will want to specify at least one of these, so that you
 don't credit your work to us under the LGPL.
 
 To set them do something similar to the following in the first part of your
-postamble section in Makefile.PL.  All occurences of <br> in the copyright
+postamble section in Makefile.PL.  All occurrences of <br> in the copyright
 are replaced with newlines, to make it easier to put in a multi-line string.
 
   POD_SET=Glib::GenPod::set_copyright(qq{Copyright 1999 team-foobar<br>LGPL});
diff --git a/lib/Glib/MakeHelper.pm b/lib/Glib/MakeHelper.pm
index d67a4e4..dfe752f 100644
--- a/lib/Glib/MakeHelper.pm
+++ b/lib/Glib/MakeHelper.pm
@@ -453,7 +453,7 @@ Create and return the text of Makefile rules to manage building RPMs.
 You'd put this in your Makefile.PL's MY::postamble.
 
 I<HASH> is a set of search and replace keys for the spec file.  All 
-occurences of @I<key>@ in the spec file template perl-$(DISTNAME).spec.in
+occurrences of @I<key>@ in the spec file template perl-$(DISTNAME).spec.in
 will be replaced with I<value>.  'VERSION' and 'SOURCE' are supplied for
 you.  For example:
 
diff --git a/lib/Glib/Object/Subclass.pm b/lib/Glib/Object/Subclass.pm
index 6bdca20..9fac3df 100644
--- a/lib/Glib/Object/Subclass.pm
+++ b/lib/Glib/Object/Subclass.pm
@@ -327,7 +327,7 @@ GLib pulls some fancy tricks with function pointers to implement methods
 in C.  This is not very language-binding-friendly, as you might guess.
 
 However, as described above, every signal allows a "class closure"; you
-may override thie class closure with your own function, and you can chain
+may override the class closure with your own function, and you can chain
 from the overridden method to the original.  This serves to implement
 virtual overrides for language bindings.