patch: fix some typos and grammar issues (#133)

* patch: minor grammar fixes

* patch: grammar and typo fixes

Author: Tbusk

docs/about.md

@@ -32,7 +32,7 @@ C is not difficult. The Vala library only has to install the generated
 header files and C applications may then access the GObject-based API of
 the Vala library as usual. It should also be easily possible to write a
 bindings generator for access to Vala libraries from applications
-written in e.g. C# as the Vala parser is written as a library, so that
+written in e.g., C# as the Vala parser is written as a library, so that
 all compile-time information is available when generating a binding.
 
 ## Why Vala?

docs/contributor-guide/compiler-guide/02-00-environment-setup.md

@@ -33,10 +33,10 @@ coding style.
 -   Hanging braces.
 -   Cuddled else.
 -   Braces necessary for single-line blocks.
--   Variable and method identifiers in lowercase, words seperated by
+-   Variable and method identifiers in lowercase, words separated by
     underscores.
 -   Type identifiers in CamelCase.
--   Enum members and constants in ALL_CAPS, words seperated by
+-   Enum members and constants in ALL_CAPS, words separated by
     underscores.
 -   C-style _/* comments. */_
 -   Hungarian notation not used.
@@ -45,7 +45,7 @@ coding style.
 -   No function-length limit.
 -   Space between method name and parameters' opening parenthesis.
 -   Property _get_, _set_, _default_
-    declaration all on one line, seperated by semicolons, if default
+    declaration all on one line, separated by semicolons, if default
     implementations are used.
 -   If properties have implementations, then _get {_, _set {_ open new lines.
 -   Attributes on their own line.

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-01-vala-in-a-nutshell.md

@@ -52,7 +52,7 @@ generator object. This object walks the code tree and generates code.
 
 Vala.CodeContext contains an important method called `accept`, which
 initiates a depth-first traversal of the code tree. This method, and the
-CodeVisitor pattern will be discussed later.
+CodeVisitor pattern, will be discussed later.
 
 **Data diagram**
 

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-02-parser.md

@@ -297,7 +297,7 @@ yourself bouncing between different classes.
 ## 3.2.2. Back to the Parser
 
 Vala.Parser is a highly specialized CodeVisitor - the only type of code
-node it visits is a Vala.SourceFile. However the Parser calls back to
+node it visits is a Vala.SourceFile. However, the Parser calls back to
 the context and uses it to create code nodes (mentioned before), then
 adds these code nodes into the context's root code node.
 
@@ -312,7 +312,7 @@ declarations of a namespace, class, struct, or interface. Fixme.
 
 This grammar is hand-generated from Vala.Parser. Sometimes the structure
 of this grammar diverges slightly from the code, for example optional
-non-terminal symbols. However the non-terminal symbol names usually
+non-terminal symbols. However, the non-terminal symbol names usually
 match a parse_ method in Vala.Parser.
 
 More literal-specific grammar at

docs/contributor-guide/compiler-guide/03-00-the-vala-compiler/03-04-symbol-resolution.md

@@ -11,9 +11,9 @@ implement themselves.
 
 Every expression has a static type. This is computed by the semantic
 analyzer. Vala.DataType is called a "type reference" because it
-contains a reference to a Vala.Typesymbol (a class, interface, etc) as
-well as information about the expression's type e.g. if it can be null,
-if it's an out parameter.
+contains a reference to a Vala.Typesymbol (a class, interface, etc.) as
+well as information about the expression's type, e.g., if it can be null,
+or, if it's an out parameter.
 
 ::: info TODO
 expand this section
@@ -29,12 +29,12 @@ variables, scope also determines their lifetime. As the code tree is
 traversed, SymbolResolver keeps track of the current scope. For example,
 when a class is visited, current_scope is set to that class's scope.
 
-When the parser parses a type, e.g. in the statement Gtk.Window
-main_window;, the type Gtk.Window is initially a Vala.UnresolvedType. In
+When the parser parses a type, e.g., in the statement Gtk.Window
+main_window, the type Gtk.Window is initially a Vala.UnresolvedType. In
 visit_data_type (), the UnresolvedType code node asks its parent to
 replace it with a new Vala.DataType created with resolve_type ().
 
-UnresolvedTypes have UnresolvedSymbols.resolve_type () uses
+UnresolvedTypes have UnresolvedSymbols. resolve_type () uses
 resolve_symbol () to find the Typesymbol referred to, and then wraps it
 in a new DataType object.
 

docs/contributor-guide/compiler-guide/09-00-build-system.md

@@ -2,7 +2,7 @@
 
 Vala is built using the standard GNU Autotools. The built executables
 are actually stored in .libs directories and wrapped by scripts.
-Therefore to debug, follow these instructions:
+Therefore, to debug, follow these instructions:
 
 ::: info TODO
 Add Vala debug instructions.
@@ -47,5 +47,5 @@ fixme           fixme          fixme                  fixme
     rodney@solaria:~/dev/buildvala % make
 ```
 
-All Makefiles, etc, generated by configure will be put in the buildvala
-directory and you can run make directly from there.
+All Makefiles generated by configure will be put in the buildvala
+directory, and you can run make directly from there.

docs/developer-guides/bindings/generating-a-vapi-with-gobject-introspection.md

@@ -202,7 +202,7 @@ library uses GTK+ and GConf, use:
 vapigen --pkg gtk+-2.0 --pkg gconf-2.0 --library [...]
 ```
 
-Otherwise you'll get errors like that, or an incomplete binding:
+Otherwise, you'll get errors like that, or an incomplete binding:
 
 ```shell
 error: The type name ``GLib.tkWidget' could not be found
@@ -309,7 +309,7 @@ values. For example,
 has an [event signal](https://developer-old.gnome.org/clutter/stable/ClutterActor.html#ClutterActor-event),
 which takes a single argument: a
 [ClutterEvent](http://developer-old.gnome.org/clutter/stable/clutter-Events.html#ClutterEvent)
-intance. It also has an [event method](http://developer-old.gnome.org/clutter/stable/ClutterActor.html#clutter-actor-event)
+instance. It also has an [event method](http://developer-old.gnome.org/clutter/stable/ClutterActor.html#clutter-actor-event)
 which takes two arguments: a ClutterEvent instance and a boolean. In
 this case, we resolve the conflict by renaming the method to
 "emit_event":
@@ -353,7 +353,7 @@ GIR assumes all pointer return values are nullable ("allow-none" in
 G-I terminology) and does not provide a way to override this assumption
 ([bug #660879](https://bugzilla.gnome.org/show_bug.cgi?id=660879)).
 Vala, on the other hand, assumes return values are not nullable unless
-otherwise otherwise specified, and comparing a non-nullable value to
+otherwise specified, and comparing a non-nullable value to
 null (e.g., to check for validity) will cause a warning. Luckily, making
 a value nullable is easy to do from a metadata file, as you can see from
 this example (for
@@ -401,7 +401,7 @@ annotations to the metadata.
 ### Abstract/Virtual Distinction
 
 Vala distinguishes between abstract and virtual methods (virtual methods
-do not need to be implemented by an class which implements the interface
+do not need to be implemented by a class which implements the interface
 whereas abstract methods do require an implementation) while GIR does
 not. In order to mark a method as virtual instead of abstract, you could
 do something like this (from
@@ -419,7 +419,7 @@ types which should be generic ([bug #639908](https://bugzilla.gnome.org/show_bug
 example,
 [GDataList](http://developer-old.gnome.org/glib/unstable/glib-Keyed-Data-Lists.html)
 is a generic in Vala but is not supported as such by GObject
-Introspection, so the the following is necessary for
+Introspection, so the following is necessary for
 [soup_form_encode_datalist](http://developer.gnome.org/libsoup/stable/libsoup-2.4-HTML-Form-Support.html#soup-form-encode-datalist):
 
 ```xml
@@ -455,8 +455,8 @@ Buffer base_type="Gst.MiniObject"
 
 GObject Introspection does not currently offer a way to annotate the
 relationship between an async function and its corresponding finish
-function ([bug #623635](https://bugzilla.gnome.org/show_bug.cgi?id=623635)). By default
-Vala will look for function with the same base name, but a "_finish"
+function ([bug #623635](https://bugzilla.gnome.org/show_bug.cgi?id=623635)). By default,
+Vala will look for a function with the same base name, but a "_finish"
 suffix, but you can point it to other functions in metadata using
 "finish_name":
 

docs/developer-guides/bindings/upstream-guide.md

@@ -34,12 +34,12 @@ errors.
 
 ## Higher quality bindings
 
-You know your library better than the Vala developers do and you can
-make sure your APIs look, and behave, as you intended.
+You know your library better than the Vala developers do, and you can
+make sure your APIs look and behave as you intended.
 
 ## API documentation
 
-We provide documentation for many libraries which ship a VAPI on
+We provide documentation for many libraries that ship a VAPI on
 [Valadoc.org](https://www.valadoc.org/).
 
 **But...**
@@ -64,7 +64,7 @@ valac automatically handle dependencies for them.
 
 GObject Introspection also allows for some things which Vala does not,
 which is where the real problems begin. These issues can cause errors
-from Vala's GIR parser (like the ones mentioned earier from GIO),
+from Vala's GIR parser (like the ones mentioned earlier from GIO),
 resulting in your GIR being useless to valac. The classic example of
 this is duplicate symbols; GObject Introspection allows for methods,
 virtual methods, and signals with the same name but different signatures
@@ -172,7 +172,7 @@ similar to what GI provides for g-ir-scanner in the form of an autoconf
 macro and a Makefile. In order to avoid introducing a hard dependency to
 your project, it is recommended you copy the
 [vapigen.m4](https://gitlab.gnome.org/GNOME/vala/-/blob/master/vapigen/vapigen.m4)
-file into your macro directory (usually an m4/ folder in the top level
+file into your macro directory (usually a m4/ folder in the top level
 of your project). The macro has the following signature:
 
 ```shell
@@ -202,8 +202,7 @@ FOUND-INTROSPECTION
 
 DEFAULT
 
->   The default value of the argument (yes, no, or auto). The default
-    default is auto.
+>   The default value of the argument (yes, no, or auto). The default value of default is auto.
 
 This macro will define three variables for you to use in your automake
 files:
@@ -214,7 +213,7 @@ VAPIGEN
 
 VAPIGEN_VAPIDIR
 
->   The location to install the your bindings to
+>   The location to install your bindings to
 
 VAPIGEN_MAKEFILE
 
@@ -267,7 +266,7 @@ FILES
 
 >   The GIR file to generate the VAPI from
 
-To use our "Foo" example from eariler:
+To use our "Foo" example from earlier:
 
 ```make
 if ENABLE_VAPIGEN

docs/developer-guides/bindings/writing-a-vapi-manually.md

@@ -2,7 +2,7 @@
 
 This document intends to be a tutorial and reference on how to write a
 Vala binding to an existing C library. If the library uses GLib, do not
-follow this document. Instead read
+follow this document. Instead, read
 [Generating a VAPI with GObject Introspection](generating-a-vapi-with-gobject-introspection). 
 A library may not follow the GLib coding practices
 precisely, but it is better to fix the library to work with GObject
@@ -20,9 +20,9 @@ would be to:
 
 1.  Bind an enum first because enums are easy to test.
 
->   Once your test gives the expected result you know that the build
+>   Once your test gives the expected result, you know that the build
     process works. This means working through the "Getting Started"
-    section and the "Enums and Flags" sub-section. Binding an enum
+    section and the "Enums and Flags" subsection. Binding an enum
     also introduces the idea that there isn't a straight mapping from
     C to Vala
 
@@ -42,9 +42,9 @@ would be to:
     document becomes more of a reference for solving tricky function
     bindings
 
-The above assumes that the library is written in an object oriented
+The above assumes that the library is written in an object-oriented
 style of C. A C binding, however, is only made up of structs and
-functions so understanding that in enough detail is the purpose of the
+functions, so understanding that in enough detail is the purpose of the
 approach.
 
 #### [1. Prerequisites](writing-a-vapi-manually/01-00-prerequisites){style="color: white;"}

docs/developer-guides/bindings/writing-a-vapi-manually/02-00-getting-started/02-08-documentation-and-valadoc-org.md

@@ -51,7 +51,7 @@ valadoc --directory docs --force --package-name mybinding mybinding.vapi
 
 This will generate the HTML documentation in the `docs` directory.
 `valadoc` expects the `docs` directory to not exist, but `--force`
-overrides this. `--package-name mybinding` will create a sub-directory
+overrides this. `--package-name mybinding` will create a subdirectory
 called `mybinding` in `docs` that contains the generated documentation
 for `mybinding.vapi`.