Updated raylib arquitecture (markdown)

raylib-arquitecture.md

@@ -22,7 +22,7 @@ A part of those 7 main modules, some other modules have been implemented with ad
  - [`physac`](https://github.com/victorfisac/Physac): 2D physics library (collision detection, resolution, dinamics...)
  - [`rlua`](https://github.com/raysan5/raylib-lua): raylib Lua binding, supporting Lua scripting
 
-Most of the modules have been designed to be as decoupled as possible from other modules, so, some modules can be used independently of raylib, as standalone libraries. Highlight two of those modules: `rlgl` ([example](https://github.com/raysan5/raylib/blob/develop/examples/rlgl_standalone.c)) and `audio` ([example](https://github.com/raysan5/raylib/blob/develop/examples/audio_standalone.c)).
+Most of the modules have been designed to be as decoupled as possible from other modules, so, some modules can be used independently of raylib, as standalone libraries. Highlight two of those modules: `rlgl` ([example](https://github.com/raysan5/raylib/blob/develop/examples/others/rlgl_standalone.c)) and `audio` ([example](https://github.com/raysan5/raylib/blob/develop/examples/others/audio_standalone.c)).
 
 Most of the secondary modules can also be used as standalone libraries: `raymath`, `camera`, `gestures`, `raygui`, `easings`, `physac`. All those modules are distributed as configurable single-file header-only libraries to be independently added to any project. Being header-only means that header also contains the functions implementation; that's extremely useful in case you have a library (a bunch of functions) that you only want to drop on your code-base to cover a very specific functionality. But creating a header-only module is not trivial, that module has to minimize external dependencies and global variables and give a very specific functionality; let's say it has to be completely portable.