--- lldb_19.html.orig	2018-07-02 11:11:45.038427145 +0200
+++ lldb_19.html	2018-07-02 11:18:44.487149418 +0200
@@ -8,13 +8,13 @@
 <h1>A brief overview of MKSANITIZER</h1>
 <p>
 A sanitizer is a special type of addition to a compiled program, and is included from a toolchain (LLVM or GCC).
-There are a few types of sanitzers. Their usual purposes are: bug detecting,
+There are a few types of sanitizers. Their usual purposes are: bug detecting,
 profiling, and security hardening.
 <p>
 NetBSD already supports the most useful ones with a decent completeness:
 <ul>
 <li>Address Sanitizer (ASan, memory usage bug detector),</li>
-<li>Undefined Behavior Sanitzer (UBSan, unspecified semantics in runtime detector),</li>
+<li>Undefined Behavior Sanitizer (UBSan, unspecified semantics in runtime detector),</li>
 <li>Thread Sanitizer (TSan, data race detector), and</li>
 <li>Memory Sanitizer (MSan, uninitialized memory read detector).</li>
 </ul>
@@ -59,8 +59,8 @@
 As an example of a well known mitigation I will note sandboxing of an application.
 <p>
 A code that is aided with sanitizers can be configured (either in build time or start/run time)
-to report the bug in the execution time of e.g. integer overflow and cause an application to halt immediatetely.
-No coding regime can have the same effect and perhaps the number of programming languages with this property is also restriced.
+to report the bug in the execution time of e.g. integer overflow and cause an application to halt immediately.
+No coding regime can have the same effect and perhaps the number of programming languages with this property is also restricted.
 <p>
 In order to use effectively sanitizers within a distribution there is need to rebuild a program and all of its dependencies (with few exceptions)
 with the same sanitizing configuration.
@@ -83,7 +83,7 @@
 <li>as of today static libraries and executables,</li>
 <li>as of today as an exception ldd(1) that borrows parts from the dynamic ELF loader.</li>
 </ul>
-The selection of unsanitzied base libraries like libc is the design choice of sanitizers that a part of the base code is unsanitized and sanitizers
+The selection of unsanitized base libraries like libc is the design choice of sanitizers that a part of the base code is unsanitized and sanitizers
 install interceptors for their public symbols.
 Sanitizers expect to use their API from high level, their features and so prevent recursive sanitization
 (although this happens sometimes in narrow cases).
@@ -106,7 +106,7 @@
 There used to be an analogous attempt in the Gentoo land (<a href="https://wiki.gentoo.org/wiki/AddressSanitizer">asantoo</a>),
 however these efforts stalled two years ago with a fiasco.
 The Google Chromium team uses a set of <a href="https://www.chromium.org/developers/testing/instrumented-libraries-for-dynamic-tools">scripts</a>
-to bootstrap sanitzied dependencies for their programs on top of a Linux distribution (as of today Ubuntu Trusty x86_64).
+to bootstrap sanitized dependencies for their programs on top of a Linux distribution (as of today Ubuntu Trusty x86_64).
 <p>
 I've started to document bugs detected with MKSANITIZER in a
 <a href="http://netbsd.org/~kamil/mksanitizer-reports/">dedicated directory</a> on my
@@ -221,7 +221,7 @@
 <h1>The first boot of a MKSANITIZER distribution with Address Sanitizer</h1>
 <p>
 The process of getting a bootable and installable (and ignoring the aspect of buildable and generatable) installation ISO image was a loop of fixing bugs and retrying the process.
-At the end of the process there is an option to inststall a fully sanitized userland with ASan, UBSan or both.
+At the end of the process there is an option to install a fully sanitized userland with ASan, UBSan or both.
 The MSan version is scheduled after finishing the kernel ptrace(2) work.
 Other options like a target prebuilt with ThreadSanitizer, safestack or The Scudo Hardened Allocator are untested.
 <p>
@@ -341,7 +341,7 @@
 developers expecting to run a release with the MKSANITIER option.
 <p>
 The lack of C++ runtime pushed me towards reusing non-sanitized ATF tests (as the ATF framework is written in C++)
-against the sanitizerd userland.
+against the sanitized userland.
 There have been detected two bugs:
 <ul>
 <li>expr(1) triggering Undefined Behavior in the routines detecting overflow in arithmetic operations,</li>
@@ -389,7 +389,7 @@
 <h1>MKSANITIZER implementation</h1>
 <p>
 The initial implementation of MKSANITIZER has been designed and implemented by Christos Zoulas.
-I took this code and contiued working on it with an external LLVM toolchain (version 7svn with local patches).
+I took this code and continued working on it with an external LLVM toolchain (version 7svn with local patches).
 The final result has been documented in share/mk/bsd.README:
 <p>
 <pre>
@@ -523,7 +523,7 @@
 <p>
 <h1>Plan for the next milestone</h1>
 <p>
-The ptrace(2) tasks have been prempted by the suspended work on sanitizers,
+The ptrace(2) tasks have been preempted by the suspended work on sanitizers,
 in order to actively collaborate with the Google Summer of Code students
 (libFuzzer integration with userland, KUBSan, KASan).
 <p>