scc

commit 30f4972a841a70650813e929c990e2ae724f355c
parent 3946f119def3a41efb115ba0c4b4948e1395913c
Author: Roberto E. Vargas Caballero <k0ga@shike2.com>
Date:   Thu, 16 Mar 2023 22:11:08 +0100

doc: Add more information about toolchain settings

There are some undocumented bits about how to setup the toolchain and that
information is very useful and needed for new users because it is hard
to realize how to port scc to new environments.

Diffstat:
M
README
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README b/README
@@ -118,12 +118,12 @@ Scc includes 3 configuration templates that can be used as base for the
 configuration of the toolchain:
 
 	- scc: It uses GNU assembler and linker with the scc libc.
-	- scc_clang: It uses clang assembler and linler with the scc libc.
+	- scc_clang: It uses clang assembler and linker with the scc libc.
 	- musl: It uses GNU assembler and linker with the musl libc.
 
 The file `include/scc/scc/sys.h` is automatically created from the scc
 toolchain configuration with the default make target. The target config
-can be used to only create the file based in the value of the variable
+can be used to only create the file based on the value of the variable
 `LIBPROFILE` allowing the user to customize that file as needed. It is
 important to highlight that the file is not removed by `make clean`
 because it can contain local user modifications. You should use
@@ -132,7 +132,7 @@ because it can contain local user modifications. You should use
 
 Musl libc support
 =================
-The scc libc is a C99 library and cannot used to compile POSIX compliant
+The scc libc is a C99 library and cannot be used to compile POSIX compliant
 programs. Scc includes a template that can be used to use a musl libc
 compiled by gcc: