diff options
author | markw <markw@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-12-19 19:44:35 +0000 |
---|---|---|
committer | markw <markw@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-12-19 19:44:35 +0000 |
commit | 2506fbc9ba283c6310435c14f38f5a80ce6877e1 (patch) | |
tree | ad69ea4340f36efa79f309058b451b8349dbe0ca /docs/new-applet-HOWTO.txt | |
parent | 599b1a1b1a686fb1b356529254cd2d6ea0a3a720 (diff) | |
download | busybox-w32-2506fbc9ba283c6310435c14f38f5a80ce6877e1.tar.gz busybox-w32-2506fbc9ba283c6310435c14f38f5a80ce6877e1.tar.bz2 busybox-w32-2506fbc9ba283c6310435c14f38f5a80ce6877e1.zip |
More spelling fixes from Larry Doolittle.
git-svn-id: svn://busybox.net/trunk/busybox@1473 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to '')
-rw-r--r-- | docs/new-applet-HOWTO.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/new-applet-HOWTO.txt b/docs/new-applet-HOWTO.txt index 638526a0c..90e124d01 100644 --- a/docs/new-applet-HOWTO.txt +++ b/docs/new-applet-HOWTO.txt | |||
@@ -78,7 +78,7 @@ useful functions in utility.c. Use these instead of reinventing the wheel. | |||
78 | 78 | ||
79 | If you use functions from utility.c, you may need to add to the preprocessor | 79 | If you use functions from utility.c, you may need to add to the preprocessor |
80 | conditionals in that file, to make sure the routines you need are included. | 80 | conditionals in that file, to make sure the routines you need are included. |
81 | So, since your mu implementation used safe_read(), append "|| define BB_MU" to | 81 | So, since your mu implementation used safe_read(), append "|| defined BB_MU" to |
82 | the #if instruction that precedes the safe_read() function in utility.c . | 82 | the #if instruction that precedes the safe_read() function in utility.c . |
83 | 83 | ||
84 | Additionally, if you have any useful, general-purpose functions in your | 84 | Additionally, if you have any useful, general-purpose functions in your |
@@ -103,7 +103,7 @@ the following: | |||
103 | If your program supports flags, the flags should be mentioned on the first | 103 | If your program supports flags, the flags should be mentioned on the first |
104 | line (mu -[bcRovma]) and a detailed description of each flag should go in the | 104 | line (mu -[bcRovma]) and a detailed description of each flag should go in the |
105 | BB_FEATURE_TRIVIAL_HELP section, one flag per line. (Numerous examples of this | 105 | BB_FEATURE_TRIVIAL_HELP section, one flag per line. (Numerous examples of this |
106 | currently exist in utility.c.) | 106 | currently exist in usage.c.) |
107 | 107 | ||
108 | 108 | ||
109 | Header Files | 109 | Header Files |