audio_standalone.c did not exist and caused a 404.

raylib-architecture.md

@@ -21,7 +21,7 @@ Beyond the seven main modules that are described above, there is a small collect
  - [`easings`](https://github.com/raysan5/raylib/blob/master/src/easings.h): Easing functions for animations (based on [Robert Penner](http://robertpenner.com/easing/) implementation).
  - [`physac`](https://github.com/victorfisac/Physac): 2D physics library (collision detection, resolution, dynamics et cetera).
 
-Wherever possible, raylib modules were designed to be as decoupled as possible from the other modules. In fact, some modules can be used as standalone libraries, independently of raylib, including the `rlgl` ([example](https://github.com/raysan5/raylib/blob/master/examples/others/rlgl_standalone.c)) and `audio` ([example](https://github.com/raysan5/raylib/blob/master/examples/others/audio_standalone.c)) modules.
+Wherever possible, raylib modules were designed to be as decoupled as possible from the other modules. In fact, some modules can be used as standalone libraries, independently of raylib, including the `rlgl` ([example](https://github.com/raysan5/raylib/blob/master/examples/others/rlgl_standalone.c)) and `raudio` ([example](https://github.com/raysan5/raylib/blob/master/examples/others/raudio_standalone.c)) modules.
 
 Most of the secondary modules (`raymath`, `camera`, `gestures`, `raygui`, `easings` and `physac`) can also be used as standalone libraries. They are distributed as configurable, single-file, header-only libraries, allowing them to be independently added to any project. Being header-only means that the file also contains function implementations. That can be extremely useful when you want to drop a library (a bunch of functions) into your codebase to provide specific functionality. However, creating a header-only module is not trivial, as the module must implement very specific functionality, while minimizing external dependencies and global variables. Simply put, it must be completely portable.