From ea846e45c18883dab2f58e2f0d23fd0577b58c8e Mon Sep 17 00:00:00 2001
From: Yu Watanabe <watanabe.yu+github@gmail.com>
Date: Wed, 21 Apr 2021 14:10:18 +0900
Subject: [PATCH] doc: fix typo

---
 TODO                    | 2 +-
 man/systemd.special.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/TODO b/TODO
index 19b044c648c..cf8568f28e4 100644
--- a/TODO
+++ b/TODO
@@ -22,7 +22,7 @@ Janitorial Clean-ups:
 
 Features:
 
-* ability to insert trusted configuration and secrets into the boot paramaters
+* ability to insert trusted configuration and secrets into the boot parameters
   of a kernel booting in a VM or on baremetal some way, via TPM
   protection. idea:
   1. pass via /proc/bootconfig
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index 73fd1dcc947..b09c4e9fa2e 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -413,7 +413,7 @@
             run once the <filename>/sysusr/</filename> hierarchy becomes available, on systems that come up
             initially without a root file system, but with an initialized <filename>/usr/</filename> and need
             to access that before setting up the root file system to ultimately switch to. On systems where
-            <varname>usr=</varname> is not used this target is ordered afer
+            <varname>usr=</varname> is not used this target is ordered after
             <filename>sysroot.mount</filename> and thus mostly equivalent to
             <filename>initrd-root-fs.target</filename>. In effect on any system once this target is reached
             the file system backing <filename>/usr/</filename> is mounted, though possibly at two different