diff options
authorDenys Vlasenko <>2011-03-21 08:49:55 (GMT)
committerDenys Vlasenko <>2011-03-21 08:49:55 (GMT)
commit42b12e40894b3ea8977492de0235f7da7672ddad (patch)
parentbc340d4021fdfbcf0bddb06eab2df8b483ab25b9 (diff)
FAQ: fix broken link
Signed-off-by: Denys Vlasenko <>
1 files changed, 3 insertions, 3 deletions
diff --git a/FAQ.html b/FAQ.html
index d7f5f56..70c10b2 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -955,7 +955,7 @@ The Busybox executable can act like many different programs depending on
the name used to invoke it. Normal practice is to create a bunch of symlinks
pointing to the Busybox binary, each of which triggers a different Busybox
function. (See <a href="FAQ.html#getting_started">getting started</a> in the
-FAQ for more information on usage, and <a href="Busybox.html">the
+FAQ for more information on usage, and <a href="BusyBox.html">the
Busybox documentation</a> for a list of symlink names and what they do.)
<p>The "one binary to rule them all" approach is primarily for size reasons: a
@@ -1114,8 +1114,8 @@ in the Busybox binary when this applet is enabled) and appname_full_usage
CONFIG_FEATURE_VERBOSE_USAGE is enabled), or it won't compile.
The other two help entry types (appname_example_usage and
appname_notes_usage) are optional. They don't take up space in the binary,
-but instead show up in the generated documentation (Busybox.html,
-Busybox.txt, and the man page Busybox.1).</li>
+but instead show up in the generated documentation (BusyBox.html,
+BusyBox.txt, and the man page busybox.1).</li>
<li>Run menuconfig, switch your applet on, compile, test, and fix the
bugs. Be sure to try both "allyesconfig" and "allnoconfig".</li>