grim/purple-objects-docbook

Some grammar/mechanics/spelling fixes.

2009-05-03, John Bailey
6fe3c31683d2
Parents facefe68d9da
Children 69e3ee38959c
Some grammar/mechanics/spelling fixes.
3 files changed, 9 insertions(+), 9 deletions(-)
  • +3 -3
    xml/about.xml
  • +5 -5
    xml/graphs.xml
  • +1 -1
    xml/plugins.xml
    • --- a/xml/about.xml Sun May 03 01:14:25 2009 -0500
    +++ b/xml/about.xml Sun May 03 09:10:32 2009 -0400
    @@ -8,8 +8,8 @@
    <title>Why use GObjects in libpurple?</title>
    <para>
    - There are many benefits GObjects can bring to purple. Some of
    - which we have implemented ourselves already and others that we've
    + There are many benefits GObjects can bring to purple, some of
    + which we have already implemented ourselves and others that we've
    considered adding in the past but no one has gotten to yet.
    </para>
    @@ -20,7 +20,7 @@
    using inheritance. For example: PurpleBlistNode is the base class
    for PurpleBuddy, PurpleChat, PurpleContact, and PurpleGroup. There
    are quite a few problems with the current setup. It's error prone,
    - theres no type checking, and it's impossible to subclass unless
    + there's no type checking, and it's impossible to subclass unless
    the new "type" is added to libpurple itself.
    </para>
    </simplesect>
    --- a/xml/graphs.xml Sun May 03 01:14:25 2009 -0500
    +++ b/xml/graphs.xml Sun May 03 09:10:32 2009 -0400
    @@ -57,10 +57,10 @@
    <para>
    The second section contains the object's member variables. They
    are prefixed with a '-' meaning they're private or '+' meaning
    - they're public. If a scope is not defined, there will be neither
    - prefix for the member variable. The rest of each member variable
    + they're public. If a scope is not defined, neither prefix will
    + appear for the member variable. The rest of each member variable
    is a 'name : type' pair, describing the member variable name and
    - it's type.
    + its type.
    </para>
    <para>
    @@ -68,7 +68,7 @@
    methods, like the member variables, have the typical scope prefixes.
    Following the prefix is the name of the method. Next, is a list of
    arguments to the method in the same 'name : type' pair format,
    - which are encapsulated in parenthesis. After the arguments, is the
    + which are encapsulated in parenthesis. After the arguments is the
    final ': type', which is the return type of the method.
    </para>
    @@ -83,7 +83,7 @@
    <title>Enumerations</title>
    <para>
    - Enumerations are presented similarly to class. In
    + Enumerations are presented similarly to classes, shown in
    <xref linkend="example-enum"/>.
    </para>
    --- a/xml/plugins.xml Sun May 03 01:14:25 2009 -0500
    +++ b/xml/plugins.xml Sun May 03 09:10:32 2009 -0400
    @@ -6,7 +6,7 @@
    <para>
    Plugins won't change too much when it comes to plugin developers, but
    - theres a bit that'll change in the backend to make better use of the
    + theres a bit that will change in the backend to make better use of the
    type system.
    </para>