aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2017-04-17 16:13:32 +0200
committerDenys Vlasenko <vda.linux@googlemail.com>2017-04-17 16:13:32 +0200
commit10ad622dc2a9fb6563fab13719ead8baf15ff9e4 (patch)
tree82312d6f38a517dcc7c0004f78d76c667f5a674b /docs
parentd85352b4ff51694cb35b429e4cef53302c9e7076 (diff)
downloadbusybox-w32-10ad622dc2a9fb6563fab13719ead8baf15ff9e4.tar.gz
busybox-w32-10ad622dc2a9fb6563fab13719ead8baf15ff9e4.tar.bz2
busybox-w32-10ad622dc2a9fb6563fab13719ead8baf15ff9e4.zip
Spelling fixes in comments, documentation, tests and examples
By klemens <ka7@github.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/sigint.htm10
-rw-r--r--docs/style-guide.txt2
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/sigint.htm b/docs/sigint.htm
index e230f4df7..d656aeb8c 100644
--- a/docs/sigint.htm
+++ b/docs/sigint.htm
@@ -45,7 +45,7 @@ intention.
45 45
46</td></tr><tr><th valign=top align=left>Required knowledge: </th> 46</td></tr><tr><th valign=top align=left>Required knowledge: </th>
47<td valign=top align=left>You have to know what it means to catch SIGINT or SIGQUIT and how 47<td valign=top align=left>You have to know what it means to catch SIGINT or SIGQUIT and how
48processes are waiting for other processes (childs) they spawned. 48processes are waiting for other processes (children) they spawned.
49 49
50 50
51</td></tr></table> 51</td></tr></table>
@@ -366,7 +366,7 @@ signal, it has to take care of communicating the signal status
366itself. 366itself.
367 367
368<p>Some programs don't do this. On SIGINT, they do cleanup and exit 368<p>Some programs don't do this. On SIGINT, they do cleanup and exit
369immediatly, but the calling shell isn't told about the non-normal exit 369immediately, but the calling shell isn't told about the non-normal exit
370and it will call the next program in the script. 370and it will call the next program in the script.
371 371
372<p>As a result, the user hits SIGINT and while one program exits, the 372<p>As a result, the user hits SIGINT and while one program exits, the
@@ -446,7 +446,7 @@ handlers, so it is portable.
446<code>trap</code> command. Here, the same as for C programs apply. If 446<code>trap</code> command. Here, the same as for C programs apply. If
447the intention of SIGINT is to end your program, you have to exit in a 447the intention of SIGINT is to end your program, you have to exit in a
448way that the calling programs "sees" that you have been killed. If 448way that the calling programs "sees" that you have been killed. If
449you don't catch SIGINT, this happend automatically, but of you catch 449you don't catch SIGINT, this happened automatically, but of you catch
450SIGINT, i.e. to do cleanup work, you have to end the program by 450SIGINT, i.e. to do cleanup work, you have to end the program by
451killing yourself, not by calling exit. 451killing yourself, not by calling exit.
452 452
@@ -466,7 +466,7 @@ files (which isn't really portable in C, though).
466bourne shell. Every language implementation that lets you catch SIGINT 466bourne shell. Every language implementation that lets you catch SIGINT
467should also give you the option to reset the signal and kill yourself. 467should also give you the option to reset the signal and kill yourself.
468 468
469<P>It is always desireable to exit the right way, even if you don't 469<P>It is always desirable to exit the right way, even if you don't
470expect your usual callers to depend on it, some unusual one will come 470expect your usual callers to depend on it, some unusual one will come
471along. This proper exit status will be needed for WCE and will not 471along. This proper exit status will be needed for WCE and will not
472hurt when the calling shell uses IUE or WUE. 472hurt when the calling shell uses IUE or WUE.
@@ -565,7 +565,7 @@ comments the scripts echo.
565<th>What happens when a shellscript called emacs, the user did not use 565<th>What happens when a shellscript called emacs, the user did not use
566<code>C-c</code> and the script has additional commands in it?</th> 566<code>C-c</code> and the script has additional commands in it?</th>
567<th>What happens if a non-interactive child catches SIGINT?</th> 567<th>What happens if a non-interactive child catches SIGINT?</th>
568<th>To behave properly, childs must do what?</th> 568<th>To behave properly, children must do what?</th>
569</tr> 569</tr>
570 570
571<tr valign=top align=left> 571<tr valign=top align=left>
diff --git a/docs/style-guide.txt b/docs/style-guide.txt
index 10ed893dc..9eed7f125 100644
--- a/docs/style-guide.txt
+++ b/docs/style-guide.txt
@@ -329,7 +329,7 @@ With "const int" compiler may fail to optimize it out and will reserve
329a real storage in rodata for it! (Hopefully, newer gcc will get better 329a real storage in rodata for it! (Hopefully, newer gcc will get better
330at it...). With "define", you have slight risk of polluting namespace 330at it...). With "define", you have slight risk of polluting namespace
331(#define doesn't allow you to redefine the name in the inner scopes), 331(#define doesn't allow you to redefine the name in the inner scopes),
332and complex "define" are evaluated each time they uesd, not once 332and complex "define" are evaluated each time they used, not once
333at declarations like enums. Also, the preprocessor does _no_ type checking 333at declarations like enums. Also, the preprocessor does _no_ type checking
334whatsoever, making it much more error prone. 334whatsoever, making it much more error prone.
335 335