docs; nitpicks

doc/site/blog/2-0.3.0-released.markdown

@@ -22,7 +22,7 @@ and mark what we managed to get done:
 With 0.3.0 we've separated the CLI from the Wren repo,
 and updated the docs to make the distinction clearer.
 
-The [CLI now has it's own corner of the docs](../cli), so that the modules
+The [CLI now has its own corner of the docs](../cli), so that the modules
 and API docs aren't overlapped like before. This opens up space for the
 CLI to get better, fuller documentation, and removes confusion about
 built in modules vs ones that are in the CLI only.

doc/site/cli/index.markdown

@@ -14,8 +14,8 @@ That includes the built in language features, the standard library and the VM it
 
 In order to access files, networks and other IO, you'd need to make a tool _using_ the language VM. 
 That's what the CLI project is! It is not bundled as part of the wren project,
-instead it is it's own project as a standalone tool you can run.
-It exposes it's own standard library and modules that may be of interest
+instead it is its own project as a standalone tool you can run.
+It exposes its own standard library and modules that may be of interest
 if looking for a general purpose single binary scriptable tool.
 
 Wren CLI is a work in progress, and contributions are welcome to make it more useful over time.

doc/site/cli/modules/index.markdown

@@ -1,6 +1,6 @@
 ^title CLI Modules
 
-The Wren CLI executable extends the built in language modules with it's own,
+The Wren CLI executable extends the built in language modules with its own,
 which offer access to IO and other facilities for scripting.
 
 The CLI modules are deeply tied to [libuv][], each other, and other internals