diff --git a/README.md b/README.md
index a17b679..d1e5484 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ capabilities.
 ### Preparing retroactive reviews
 
 Since "reading the source code" requires advanced domain knowledge, this
-section describes a pen-and-paper aproach that can be used to cryptographically
+section describes a pen-and-paper approach that can be used to cryptographically
 ensure you can retro-actively review what you executed, even if you didn't
 review before you executed it. Pen-and-paper should be taken literally here to
 ensure this can't be modified by software. If done correctly, you don't need to
diff --git a/writeups/dockerfile.md b/writeups/dockerfile.md
index fd6d47e..fc291f1 100644
--- a/writeups/dockerfile.md
+++ b/writeups/dockerfile.md
@@ -21,12 +21,12 @@ The Dockerfile has two stages, the first one compiles the source code:
   folder that we're going to compile in and change the working directory to
   this folder.
 - `COPY . .` This copies the content of the current directory of the build
-  system into the container. The current dirctory on the build system is
+  system into the container. The current directory on the build system is
   expected to be the folder that this repository was cloned to, so the files
   that are copied are only those from the git repository.
 - `RUN cargo build --release --locked --target=x86_64-unknown-linux-musl` This
   compiles the rust source code into a binary. The command is explained in
-  detail in the [`Makefile`](makefile.md) writeup. This commnand is likely making our temporary
+  detail in the [`Makefile`](makefile.md) writeup. This command is likely making our temporary
 
 The temporary build image is done at this point, the second `FROM` starts a new
 image: