Merge pull request #471 from ckormanyos/update_docs

Update docs typos/tools/benchmarks

readme.md

@@ -519,17 +519,14 @@ The build status badges represent the state of the nightly CI builds and tests.
 ## Modern `avr-gcc` Toolchain
 
 The repo [avr-gcc-build](https://github.com/ckormanyos/avr-gcc-build)
-builds _very_ up-to-date `avr-gcc` toolchains.
-Shell and YAML scripts build `avr-gcc`
-directly from source on GHA runner(s). The Workflow-Run(s)
-build `avr-gcc` from up-to-date releases such as `12.3.0` or other
-modern branches like `trunk` or `releases/gcc-13`.
-An `x86_64-linux-gnu`-build on `*nix` is provided.
-There is also a dependency-free, statically-linked `x86_64-w64-mingw32`-build
-intended for `Win*`.
+builds up-to-date `avr-gcc` toolchains for `x86_64-linux-gnu` and `x86_64-w64-mingw32`.
+Shell and YAML scripts build `avr-gcc` directly from source on GHA runner(s).
+In addition, occasional GitHub-releases provide pre-built
+`avr-gcc` toolchains for `x86_64-linux-gnu` and `x86_64-w64-mingw32`.
+
 This repo is a great place to learn how to build your own `avr-gcc` toolchain
-from source since the straightforward shell and YAML scripts are easy to use
-or adapt.
+from source. The straightforward, well-described shell and YAML scripts
+are easy to understand, use or adapt.
 
 ## GNU/GCC Compilers
 

ref_app/src/app/benchmark/readme.md

@@ -24,7 +24,9 @@
 
 Executing the benchmarks is straightforward. Select the desired benchmark and
 activate its corresponding flag in
-[app_benchmark.h](https://github.com/ckormanyos/real-time-cpp/blob/master/ref_app/src/app/benchmark/app_benchmark_none.h)
+[app_benchmark.h](https://github.com/ckormanyos/real-time-cpp/blob/master/ref_app/src/app/benchmark/app_benchmark.h).
+In particular, `#define` the flag `APP_BENCHMARK_TYPE` to be one of the pre-defined benchmark types
+(typically done by sinply un-commenting one of the easily-found relevant lines.
 Compile the reference application and run on the target.
 The benchmark timing will be reflected on microcontroller's corresponding
 benchmark port pin (in its MCAL).