diff options
| -rw-r--r-- | doc/intro.cli | 2 | ||||
| -rw-r--r-- | doc/intro1.cli | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/intro.cli b/doc/intro.cli index bb857f1..efaa0cb 100644 --- a/doc/intro.cli +++ b/doc/intro.cli @@ -230,7 +230,7 @@ every time we add, remove, or rename a source file in our project. There also appears to be some (commented out) infrastructure for importing and linking libraries (that \c{libs} variable). We will see how to use it in a moment. -\N|for simple projects that follow the canonical structure we can often +\N|In simple projects that follow the canonical structure we can often completely ignore the presence of the build definition files thus approaching the \i{build system-less} workflow found in languages like Rust and Go.| diff --git a/doc/intro1.cli b/doc/intro1.cli index 6e22135..ff86129 100644 --- a/doc/intro1.cli +++ b/doc/intro1.cli @@ -854,7 +854,7 @@ Let's try to build it and see what happens \- maybe it will magically work \ $ b config.cxx=g++-5 error: unable to import target libhello%lib{hello} - info: use config.import.libhello command line variable to specifying its project out_root + info: use config.import.libhello command line variable to specify its project out_root info: while applying rule cxx.link to update exe{hello} info: while applying rule alias to update dir{./} \ @@ -899,7 +899,7 @@ $ touch hello.cpp $ b error: unable to import target libhello%lib{hello} - info: use config.import.libhello command line variable to specifying its project out_root + info: use config.import.libhello command line variable to specify its project out_root info: while applying rule cxx.link to update exe{hello} info: while applying rule alias to update dir{./} \ |