[git commit master 1/1] FAQ: fix broken link

[Denys Vlasenko]

commit: http://git.busybox.net/busybox-website/commit/?id=42b12e40894b3ea8977492de0235f7da7672ddad
branch: http://git.busybox.net/busybox-website/commit/?id=refs/heads/master

Signed-off-by: Denys Vlasenko <vda.linux at googlemail.com>
---
 FAQ.html |    6 +++---
 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>
-- 
1.7.3.4