diff --git a/man/cgroup-sandboxing.xml b/man/cgroup-sandboxing.xml
index 9499c9027a..c9e068f887 100644
--- a/man/cgroup-sandboxing.xml
+++ b/man/cgroup-sandboxing.xml
@@ -8,10 +8,10 @@
-This option cannot be bypassed by prefixing + to the executable path
-in the service unit, as it applies to the whole control group.
+ This option cannot be bypassed by prefixing + to the executable path
+ in the service unit, as it applies to the whole control group.
-These options cannot be bypassed by prefixing + to the executable path
-in the service unit, as it applies to the whole control group.
+ These options cannot be bypassed by prefixing + to the executable path
+ in the service unit, as it applies to the whole control group.
diff --git a/man/supported-controllers.xml b/man/supported-controllers.xml
index 62e05a6dc8..3ec06939e6 100644
--- a/man/supported-controllers.xml
+++ b/man/supported-controllers.xml
@@ -8,8 +8,8 @@
-The following controller names may be specified: , ,
-, , , , ,
-, , and .
+ The following controller names may be specified: , ,
+ , , , , ,
+ , , and .
diff --git a/man/threads-aware.xml b/man/threads-aware.xml
index 52c5c56acb..bb39266626 100644
--- a/man/threads-aware.xml
+++ b/man/threads-aware.xml
@@ -6,19 +6,19 @@
-All functions listed here are thread-agnostic and only a single specific thread may operate on a
-given object during its entire lifetime. It's safe to allocate multiple independent objects and use each from a
-specific thread in parallel. However, it's not safe to allocate such an object in one thread, and operate or free it
-from any other, even if locking is used to ensure these threads don't operate on it at the very same time.
+ All functions listed here are thread-agnostic and only a single specific thread may operate on a
+ given object during its entire lifetime. It's safe to allocate multiple independent objects and use each from a
+ specific thread in parallel. However, it's not safe to allocate such an object in one thread, and operate or free it
+ from any other, even if locking is used to ensure these threads don't operate on it at the very same time.
-All functions listed here are thread-safe and may be called in parallel from multiple threads.
+ All functions listed here are thread-safe and may be called in parallel from multiple threads.
-The code described here uses
-getenv3,
-which is declared to be not multi-thread-safe. This means that the code calling the functions described
-here must not call
-setenv3
-from a parallel thread. It is recommended to only do calls to setenv()
-from an early phase of the program when no other threads have been started.
+ The code described here uses
+ getenv3,
+ which is declared to be not multi-thread-safe. This means that the code calling the functions described
+ here must not call
+ setenv3
+ from a parallel thread. It is recommended to only do calls to setenv()
+ from an early phase of the program when no other threads have been started.