summaryrefslogtreecommitdiff
path: root/contractor.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-10-20 10:09:48 +0300
committerLars Wirzenius <liw@liw.fi>2020-10-20 10:09:48 +0300
commit7e80f9819632c6d0756f346f205fe177e832ff5d (patch)
treecee9fa0b6c5782959cfb51eb0bdc98f4926c55c9 /contractor.md
parent3f07b2888519ec4b5f599d4193220bb3daa643a6 (diff)
downloadick-contractor-7e80f9819632c6d0756f346f205fe177e832ff5d.tar.gz
doc: better word choice
Diffstat (limited to 'contractor.md')
-rw-r--r--contractor.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contractor.md b/contractor.md
index 72d94dd..b65ed79 100644
--- a/contractor.md
+++ b/contractor.md
@@ -42,7 +42,7 @@ have further dependencies, which have dependencies of their own. You'd
need to vet the whole dependency tree. Even decades ago, in the 1990s,
this could easily be hundreds of thousands of lines of code, and
modern systems a much larger. Note that build tools are themselves
-dependencies, as is the whole operating system. Any code that is used
+dependencies, as is the whole operating system. Any code that is invoked
in the build process is a dependency.
How certain are you that you can spot malicious code that's