From 39f9beebd8015bac1969b70e01ea328a48e3baf0 Mon Sep 17 00:00:00 2001 From: Elsie Date: Tue, 13 Jan 2026 16:48:48 -0500 Subject: [PATCH] fix minor typos --- how_to/010_nob_two_stage/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how_to/010_nob_two_stage/README.md b/how_to/010_nob_two_stage/README.md index 0cbbe46b..8a554a63 100644 --- a/how_to/010_nob_two_stage/README.md +++ b/how_to/010_nob_two_stage/README.md @@ -2,7 +2,7 @@ Quite often when your project grows big enough you end up wanting to configure the build of your application: different sets of enabled features, compilation flags, etc. The recommended approach to this in nob is to setup Two Stage Build™ system. That is [nob.c](./nob.c) does not do any actual work except generating initial `./build/config.h` and building `./src_build/nob_configed.c` (which `#include`-s the `./build/config.h` file) and then running it. -Exact details of the setup is up to your. Here we present just one way of doing it. In fact you have a freedom to do as many stages of your build as you want, analysing your environment in all sorts of different ways (you literally have a system programming language at your disposal). The whole point of nob is that you bootstrap it ONLY with `cc -o nob nob.c` (no additional flags or actions should be required form the user) and the rest is taken care of by your C code. +Exact details of the setup is up to you. Here we present just one way of doing it. In fact you have the freedom to do as many stages of your build as you want, analysing your environment in all sorts of different ways (you literally have a system programming language at your disposal). The whole point of nob is that you bootstrap it ONLY with `cc -o nob nob.c` (no additional flags or actions should be required form the user) and the rest is taken care of by your C code. ## Quick Start