config: merge "Busybox Settings" and "Busybox Library Tuning" into one menu

Tweak a few help texts while at it

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

2 files changed, 8 insertions, 6 deletions

diff --git a/libbb/Config.src b/libbb/Config.src
index c51640305..16c79dbf0 100644
--- a/libbb/Config.src
+++ b/libbb/Config.src
@@ -3,7 +3,7 @@
 # see scripts/kbuild/config-language.txt.
 #
 
-menu "Busybox Library Tuning"
+comment "Library Tuning"
 
 INSERT
 
@@ -66,7 +66,7 @@ config FEATURE_FAST_TOP
         bool "Faster /proc scanning code (+100 bytes)"
         default n  # all "fast or small" options default to small
         help
-          This option makes top (and ps) ~20% faster (or 20% less CPU hungry),
+          This option makes top and ps ~20% faster (or 20% less CPU hungry),
           but code size is slightly bigger.
 
 config FEATURE_ETC_NETWORKS
@@ -302,13 +302,17 @@ config FEATURE_VERBOSE_CP_MESSAGE
         default n
         help
           Error messages with this feature enabled:
+
             $ cp file /does_not_exist/file
             cp: cannot create '/does_not_exist/file': Path does not exist
             $ cp file /vmlinuz/file
             cp: cannot stat '/vmlinuz/file': Path has non-directory component
+
           If this feature is not enabled, they will be, respectively:
+
             cp: cannot create '/does_not_exist/file': No such file or directory
             cp: cannot stat '/vmlinuz/file': Not a directory
+
           This will cost you ~60 bytes.
 
 config FEATURE_USE_SENDFILE
@@ -376,7 +380,4 @@ config FEATURE_HWIB
         bool "Support infiniband HW"
         default y
         help
-          Support for printing infiniband addresses in
-          network applets.
-
-endmenu
+          Support for printing infiniband addresses in network applets.
diff --git a/libbb/common_bufsiz.c b/libbb/common_bufsiz.c
index 2847eb57d..f1124ba0e 100644
--- a/libbb/common_bufsiz.c
+++ b/libbb/common_bufsiz.c
@@ -19,6 +19,7 @@
 //config:
 //config:         At link time, "text" is padded to a full page. At runtime, all "text"
 //config:         pages are mapped RO and executable.
+//config:
 //config:         "Data" starts on the next page boundary, but is not padded
 //config:         to a full page at the end. "Bss" starts wherever "data" ends.
 //config:         At runtime, "data" pages are mapped RW and they are file-backed