markdown: Fix typo in docs (2)

https://bugzilla.gnome.org/show_bug.cgi?id=797129

markdown/contribute/index.md

@@ -224,7 +224,7 @@ in the current directory. Attach these files to a bug report in bugzilla.
 Please make sure your patches are as terse and precise as possible. Do not
 include 'clean-ups' or non-functional changes, since they distract from the
 real changes and make things harder to review, and also lower the chances that
-the patch will still apply cleanly to the lastest version in git. If you feel
+the patch will still apply cleanly to the latest version in git. If you feel
 there are things to clean up, please submit the clean-ups as a separate patch
 that does not contain any functional changes.
 

markdown/design/stream-status.md

@@ -90,7 +90,7 @@ The existing `STREAM_STATUS` message will be further defined and implemented in
     a pad, the message source will contain the owner as well. The idea
     is that the application should be able to see from the element/pad
     what function this thread has in the context of the application and
-    configure the thread appropriatly.
+    configure the thread appropriately.
 
   - **`object`**: `G_TYPE`, `GstTask/GThread`: A `GstTask/GThread` controlling
     this streaming thread.

markdown/installing/on-windows.md

@@ -107,7 +107,7 @@ liking, and work from there.
 > ![Information](images/icons/emoticons/information.png)
 > **64-bit Users**
 >
->Use `%GSTREAMER_ROOT_X86_64%` if you have installed GStreamer binaries for 64-bit platforms. Both GStreamer binariess (32 and 64-bit) can be installed simultaneously, and hence the separate environment variables.
+>Use `%GSTREAMER_ROOT_X86_64%` if you have installed GStreamer binaries for 64-bit platforms. Both GStreamer binaries (32 and 64-bit) can be installed simultaneously, and hence the separate environment variables.
 >
 >Make sure you select the Solution Configuration that matches GStreamer that you have installed: `Win32` for 32 bits or `x64` for 64 bits.
 >

markdown/plugin-development/advanced/allocation.md

@@ -19,8 +19,8 @@ GStreamer plugins. We will first talk about the lowlevel `GstMemory`
 object that manages access to a piece of memory and then continue with
 one of it's main users, the `GstBuffer`, which is used to exchange data
 between plugins and with the application. We will also discuss the `GstMeta`.
-This object can be placed on buffers to provide extra info about it an
-dits memory. We will also discuss the `GstBufferPool`, which allows to
+This object can be placed on buffers to provide extra info about it and
+its memory. We will also discuss the `GstBufferPool`, which allows to
 more-efficiently manage buffers of the same size.
 
 To conclude this chapter we will take a look at the `GST_QUERY_ALLOCATION`

markdown/tutorials/basic/debugging-tools.md

@@ -51,7 +51,7 @@ amount of desired output:
 |   |         | user-visible problems are expected to happen.                  |
 | 3 | FIXME   | Logs all "fixme" messages. Those typically that a codepath that|
 |   |         | is known to be incomplete has been triggered. It may work in   |
-|   |         | most cases, but mauy cause problems in specific instances.     |
+|   |         | most cases, but may cause problems in specific instances.      |
 | 4 | INFO    | Logs all informational messages. These are typically used for  |
 |   |         | events in the system that only happen once, or are important   |
 |   |         | and rare enough to be logged at this level.                    |
@@ -64,7 +64,7 @@ amount of desired output:
 |   |         | streaming and steady-state conditions. This is used for log    |
 |   |         | messages that happen on every buffer in an element for example.|
 | 7 | TRACE   | Logs all trace messages. Those are message that happen very    |
-|   |         | very often. This is for example is each each time the reference|
+|   |         | very often. This is for example is each time the reference     |
 |   |         | count of a GstMiniObject, such as a GstBuffer or GstEvent, is  |
 |   |         | modified.                                                      |
 | 8 | MEMDUMP | Logs all memory dump messages. This is the heaviest logging and|