fix typos

Author: RainRat

CHANGES.md

@@ -183,7 +183,7 @@ v0.11.7 - 2022-02-06
 
 v0.11.6 - 2022-01-22
 ====================
-* WASAPI: Fix a bug where the device is not stopped when an error occurrs when writing to a playback device.
+* WASAPI: Fix a bug where the device is not stopped when an error occurs when writing to a playback device.
 * PulseAudio: Fix a rare crash due to a division by zero.
 * The node graph can now be used as a node. This allows node graphs to be connected to other node graphs.
 * Fix a crash with high-pass and band-pass filters.
@@ -477,7 +477,7 @@ v0.10.26 - 2020-11-24
 
 v0.10.25 - 2020-11-15
   - PulseAudio: Fix a bug where the stop callback isn't fired.
-  - WebAudio: Fix an error that occurs when Emscripten increases the size of it's heap.
+  - WebAudio: Fix an error that occurs when Emscripten increases the size of its heap.
   - Custom Backends: Change the onContextInit and onDeviceInit callbacks to take a parameter which is a pointer to the config that was
     passed into ma_context_init() and ma_device_init(). This replaces the deviceType parameter of onDeviceInit.
   - Fix compilation warnings on older versions of GCC.

CONTRIBUTING.md

@@ -21,7 +21,7 @@ significant work without talking to me first. If I don't like it, it won't be me
 [Discord](https://discord.gg/9vpqbjU) and [Twitter](https://twitter.com/mackron).
 
 Always base your pull request branch on the "dev" branch. The master branch contains the latest release, which
-means your pull request may not be including the lastest in-development changes which may result in unnecessary
+means your pull request may not be including the latest in-development changes which may result in unnecessary
 conflicts.
 
 I need to review your pull requests before merging. If your pull request is non-trivial, try to break it up into
@@ -63,7 +63,7 @@ not contribute to this project.
 
 Predictable Questions
 ---------------------
-### "Would you consider splitting out [some section of code] into it's own file?"
+### "Would you consider splitting out [some section of code] into its own file?"
 No, the idea is to keep everything in one place. It would be nice in specific cases to split out specific sections
 of the code, such as the resampler, for example. However, this will completely violate one of the major goals of the
 project - to have a complete audio library contained within a single file.

README.md

@@ -180,7 +180,7 @@ Documentation
 Online documentation can be found here: https://miniaud.io/docs/
 
 Documentation can also be found at the top of [miniaudio.h](https://raw.githubusercontent.com/mackron/miniaudio/master/miniaudio.h)
-which is always the most up-to-date and authoritive source of information on how to use miniaudio. All other
+which is always the most up-to-date and authoritative source of information on how to use miniaudio. All other
 documentation is generated from this in-code documentation.
 
 

examples/custom_backend.c

@@ -261,7 +261,7 @@ static ma_result ma_context_get_device_info__sdl(ma_context* pContext, ma_device
     of the device's _actual_ ideal format.
     
     Note: With Emscripten, it looks like non-zero values need to be specified for desiredSpec. Whatever is specified in
-    desiredSpec will be used by SDL since it uses it just does it's own format conversion internally. Therefore, from what
+    desiredSpec will be used by SDL since it uses it just does its own format conversion internally. Therefore, from what
     I can tell, there's no real way to know the device's actual format which means I'm just going to fall back to the full
     range of channels and sample rates on Emscripten builds.
     */

examples/simple_enumeration.c

@@ -1,7 +1,7 @@
 /*
 Demonstrates how to enumerate over devices.
 
-Device enumaration requires a `ma_context` object which is initialized with `ma_context_init()`. Conceptually, the
+Device enumeration requires a `ma_context` object which is initialized with `ma_context_init()`. Conceptually, the
 context sits above a device. You can have many devices to one context.
 
 If you use device enumeration, you should explicitly specify the same context you used for enumeration in the call to

examples/simple_mixing.c

@@ -4,7 +4,7 @@ Demonstrates one way to load multiple files and play them all back at the same t
 When mixing multiple sounds together, you should not create multiple devices. Instead you should create only a single
 device and then mix your sounds together which you can do by simply summing their samples together. The simplest way to
 do this is to use floating point samples and use miniaudio's built-in clipper to handling clipping for you. (Clipping
-is when sample are clampled to their minimum and maximum range, which for floating point is -1..1.)
+is when sample are clamped to their minimum and maximum range, which for floating point is -1..1.)
 
 ```
 Usage:   simple_mixing [input file 0] [input file 1] ... [input file n]