summaryrefslogtreecommitdiff
path: root/doc/concepts/overview.md
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2025-06-27 11:49:30 +0200
committerKlaus Aehlig <klaus.aehlig@huawei.com>2025-06-27 12:54:05 +0200
commitde7bdb452e7f600e5cb17d87710fb952f151ba29 (patch)
tree9dd3f1035799f4ee6bcf1f1315e94b57924630c7 /doc/concepts/overview.md
parent303304ef4aa66bd55a9b6fa3e561dab828d3831a (diff)
downloadjustbuild-de7bdb452e7f600e5cb17d87710fb952f151ba29.tar.gz
Documentation: fix typos
Diffstat (limited to 'doc/concepts/overview.md')
-rw-r--r--doc/concepts/overview.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/concepts/overview.md b/doc/concepts/overview.md
index 79dc301f..4346e1fa 100644
--- a/doc/concepts/overview.md
+++ b/doc/concepts/overview.md
@@ -26,7 +26,7 @@ target as a dependency, irrespectively of where the target is coming from
Of course, to actually build a single target from its dependencies, many
invocations of the compiler or other tools are necessary (so called
-"actions"); the build tool translates these high level description
+"actions"); the build tool translates these high-level description
into the individual actions necessary and only re-executes those where
inputs have changed.
@@ -40,7 +40,7 @@ typically maintained centrally for a project or an organization.
The code base is usually split into many directories, each containing
source files belonging together. To allow the definition of targets
where their code is, the targets are structured in a similar way. For
-each directory, there can be a targets files. Directories for which such
+each directory, there can be a targets file. Directories for which such
a targets file exists are called "modules". Each file belongs to the
module that is closest when searching upwards in the directory tree. The
targets file of a module defines the targets formed from the source