diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index ca7d042d65..625063f1c0 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -1972,35 +1972,35 @@ CapabilityBoundingSet=~CAP_B CAP_C</programlisting>
             <tbody>
               <row>
                 <entry><literal>success</literal></entry>
-                <entry>In case the service ran successfully and exited cleanly</entry>
+                <entry>The service ran successfully and exited cleanly.</entry>
               </row>
               <row>
                 <entry><literal>protocol</literal></entry>
-                <entry>In case of a protocol violation: the service did not take the steps required by its unit configuration (specifically what is configured in its <varname>Type=</varname> setting)</entry>
+                <entry>A protocol violation occurred: the service did not take the steps required by its unit configuration (specifically what is configured in its <varname>Type=</varname> setting).</entry>
               </row>
               <row>
                 <entry><literal>timeout</literal></entry>
-                <entry>In case of an operation timeout</entry>
+                <entry>One of the steps timed out.</entry>
               </row>
               <row>
                 <entry><literal>exit-code</literal></entry>
-                <entry>If a service process exited with a non-zero exit code; see <varname>$EXIT_CODE</varname> below for the actual exit code returned.</entry>
+                <entry>Service process exited with a non-zero exit code; see <varname>$EXIT_CODE</varname> below for the actual exit code returned.</entry>
               </row>
               <row>
                 <entry><literal>signal</literal></entry>
-                <entry>If a service process was terminated abnormally by a signal, without dumping core; see <varname>$EXIT_CODE</varname> below for the actual signal causing the termination</entry>
+                <entry>A service process was terminated abnormally by a signal, without dumping core. See <varname>$EXIT_CODE</varname> below for the actual signal causing the termination.</entry>
               </row>
               <row>
                 <entry><literal>core-dump</literal></entry>
-                <entry>If a service process terminated abnormally with a signal and dumped core, also see <varname>$EXIT_CODE</varname> for the signal causing the termination</entry>
+                <entry>A service process terminated abnormally with a signal and dumped core. See <varname>$EXIT_CODE</varname> below for the signal causing the termination.</entry>
               </row>
               <row>
                 <entry><literal>watchdog</literal></entry>
-                <entry>If the watchdog keep-alive ping was enabled for the service but it missed the deadline.</entry>
+                <entry>Watchdog keep-alive ping was enabled for the service, but the deadline was missed.</entry>
               </row>
               <row>
                 <entry><literal>start-limit-hit</literal></entry>
-                <entry>In case a start limit was applied to the unit and it was hit and the unit hence failed to start. See <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>'s <varname>StartLimitIntervalSec=</varname> and <varname>StartLimitBurst=</varname> for details.</entry>
+                <entry>A start limit was defined for the unit and it was hit, causing the unit to fail to start. See <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>'s <varname>StartLimitIntervalSec=</varname> and <varname>StartLimitBurst=</varname> for details.</entry>
               </row>
               <row>
                 <entry><literal>resources</literal></entry>