diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2021-02-14 15:10:15 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2021-02-14 15:10:15 +0000 |
| commit | 44be69112c71fe65784cc014995044c2a191a449 (patch) | |
| tree | 774de7de5d75c202903080b74bc5eca87ed1d8d6 /doc/exitcodes.html | |
| parent | 6ff749e62652103b3ab84ef145691602ed6e0fea (diff) | |
| download | execline-44be69112c71fe65784cc014995044c2a191a449.tar.xz | |
Apply doc fixes by flexibeast and suggestions by Profpatsch&aranea
Diffstat (limited to 'doc/exitcodes.html')
| -rw-r--r-- | doc/exitcodes.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/exitcodes.html b/doc/exitcodes.html index 619f5d3..c1fcd24 100644 --- a/doc/exitcodes.html +++ b/doc/exitcodes.html @@ -24,7 +24,7 @@ Either <em>C</em> dies normally with an exit code from 0 to 255, or it is killed by a signal. How can we make sure that <em>P</em> reports to <em>G</em> what happened -to <em>C</em>, with as much precision as possible ? +to <em>C</em>, with as much precision as possible? </p> <p> @@ -33,7 +33,7 @@ structure filled in by <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/waitpid.html">waitpid()</a>) than a process can report by simply exiting. <em>P</em> could exit with the same exit code as <em>C</em>, -but then what should it do if C has been killed by a signal ? +but then what should it do if C has been killed by a signal? </p> <p> @@ -42,7 +42,7 @@ but then what should it do if C has been killed by a signal ? But that's actually not right, because <em>P</em> itself could be killed by a signal from another source, and G needs that information. "<em>P</em> has been killed by a signal" and "<em>C</em> has been killed by a signal" are two -different informations, so they should not be reported in the same way. +different pieces of information, so they should not be reported in the same way. </p> <p> |