From f52d35605687fc0c3fb05c089315a2b2c2c46e17 Mon Sep 17 00:00:00 2001 From: Carl Smith Date: Fri, 9 Oct 2020 02:45:10 +0100 Subject: [PATCH] Just making the markup consistent with other pages. --- raylib-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/raylib-architecture.md b/raylib-architecture.md index aa3dcbd..7176035 100644 --- a/raylib-architecture.md +++ b/raylib-architecture.md @@ -25,7 +25,7 @@ Wherever possible, raylib modules were designed to be as decoupled as possible f 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. -NOTE: *The `raymath`, `camera` and `gestures` modules are all compiled with raylib by default.* +**NOTE**: *The `raymath`, `camera` and `gestures` modules are all compiled with raylib by default.* raylib also uses some external libraries (most of which are included as single-file, header-only libraries), including the well known [stb libraries](https://github.com/nothings/stb) and [some other similar libraries](https://github.com/raysan5/raylib/tree/master/src/external).