fix typos

5 files changed, 9 insertions, 9 deletions

diff --git a/_posts/2015-07-03-std-call-once-bug.md b/_posts/2015-07-03-std-call-once-bug.md
index 68983cf..9e82b84 100644
--- a/_posts/2015-07-03-std-call-once-bug.md
+++ b/_posts/2015-07-03-std-call-once-bug.md
@@ -128,7 +128,7 @@ Unfortunately, matters became a bit more complicated when I tried to introduce
 two singletons, one having a dependency on the other.
 I had `Logger`, like in the example above, and some kind of a "master"
 singleton (let's call it `Duke`).
-`Duke`'s constructor was complicated and time-consuming, and definetely
+`Duke`'s constructor was complicated and time-consuming, and definitely
 required some logging to be done.
 I thought that I could simply call `Logger::get_instance` inside `Duke`'s
 constructor, and everything looked fine at first glance.
diff --git a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
index a5de5f1..caefe08 100644
--- a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
+++ b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
@@ -133,7 +133,7 @@ No warnings/errors are emitted, making the situation truly disturbing.
 I tested this with GNU compiler version 5.4.0 and Microsoft compiler version
 19.00.24210.
 
-This behaviour can be easily fixed either by making these functions `static` or
+This behavior can be easily fixed either by making these functions `static` or
 by using unnamed namespaces (see below).
 
 ### Properties
@@ -144,7 +144,7 @@ translation units.
 address in every translation unit, its local static variables will be shared,
 etc.
 * Defining different `inline` functions with the same name in different
-translation units is undefined behaviour.
+translation units is undefined behavior.
 
 Two inline functions might be different even if they are the same textually.
 For example, they might reference two global variables which have the same
@@ -208,7 +208,7 @@ classes.
 * Similar to the `static` approach, each translation unit gets its own replica
 of a function/class, including their own local static variables, etc.
 * Defining different classes with the same name in different translation units
-(without utilizing unnamed namespaces) is undefined behaviour.
+(without utilizing unnamed namespaces) is undefined behavior.
 
 Conclusion
 ----------
diff --git a/_posts/2020-05-06-docker-bind-mounts.md b/_posts/2020-05-06-docker-bind-mounts.md
index 3e7b72a..5f85597 100644
--- a/_posts/2020-05-06-docker-bind-mounts.md
+++ b/_posts/2020-05-06-docker-bind-mounts.md
@@ -107,7 +107,7 @@ so that the `redis-server` process owns the /data directory and thus can write
 to it.
 
 If you want to preserve ./data ownership, Redis' image (and many others)
-explicitly accomodates for it by _not_ changing its owner if the container is
+explicitly accommodates for it by _not_ changing its owner if the container is
 run as anybody other than root.
 For example:
 
diff --git a/_posts/2020-05-20-makefile-escaping.md b/_posts/2020-05-20-makefile-escaping.md
index 4308467..073db73 100644
--- a/_posts/2020-05-20-makefile-escaping.md
+++ b/_posts/2020-05-20-makefile-escaping.md
@@ -2,7 +2,7 @@
 title: Escaping characters in Makefile
 excerpt: Making less error-prone.
 ---
-I'm a big sucker for irrelevant neatpicks like properly quoting arguments in
+I'm a big sucker for irrelevant nitpicks like properly quoting arguments in
 shell scripts.
 I've also recently started using GNU make as a substitute for one-line shell
 scripts (so instead of a bunch of scripts like build.sh, deploy.sh, test.sh I
diff --git a/_posts/2021-03-10-ubuntu-packaging.md b/_posts/2021-03-10-ubuntu-packaging.md
index 10421f0..3c993b3 100644
--- a/_posts/2021-03-10-ubuntu-packaging.md
+++ b/_posts/2021-03-10-ubuntu-packaging.md
@@ -35,7 +35,7 @@ At best, you'll learn how to build _binary_ packages, not suitable for
 publishing in a PPA (which only accept _source_ packages and builds the
 binaries itself).
 
-First, you need to realise that there're source packages and binary packages.
+First, you need to realize that there are source packages and binary packages.
 Binary packages are the .deb files that actually contain the software.
 A source package is, confusingly, multiple files, and you need to submit them
 all to Launchpad.
@@ -47,7 +47,7 @@ the new versions naturally via the package manager (`apt`).
 Canonical's Launchpad provides a very handy PPA (Personal Package Archive)
 service so that anyone can set up a repository.
 Users could then use `add-apt-repository ppa:...` and get the packages in a
-standard and convinient way.
+standard and convenient way.
 
 Tools
 -----
@@ -68,7 +68,7 @@ email address) from environment variables.
 You can put something like
 
     export DEBFULLNAME='John Doe'
-    epxort DEBEMAIL='John.Doe@example.com'
+    export DEBEMAIL='John.Doe@example.com'
 
 in your .bashrc to set them globally.