system/man-db: Updated for version 2.7.0.1.

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>

1 files changed, 8 insertions, 9 deletions

diff --git a/system/man-db/README.Slackware b/system/man-db/README.Slackware
index f0eb6b57ca84..165e9dfa4c42 100644
--- a/system/man-db/README.Slackware
+++ b/system/man-db/README.Slackware
@@ -12,15 +12,14 @@ installed in this case.
 When installing man-db, the doinst.sh script may take several minutes to
 run. This is because it's indexing all the man pages on the system. Also,
 a cron job is installed in /etc/cron.daily, which adds newly-installed
-man pages to the database. The index speeds up searching via "man -K",
-"man -k", or "apropos". It's fast enough that "man -K" is now actually
-useful... the disadvantage is that newly-installed man pages won't be
-found in these searches until the database has been updated, so any time
-you install new man pages, you'll want to run "mandb" as root, or wait
-for cron to do it for you (if you don't do this, the new pages can still
-be displayed, they just won't be searchable). The indexing runs quickly
-once the initial database has been created, so the cron job or manual
-update shouldn't bring your system to its knees.
+man pages to the database. The index speeds up searching via "man -k"
+or "apropos". The disadvantage is that newly-installed man pages won't
+be found in these searches until the database has been updated, so any
+time you install new man pages, you'll want to run "mandb" as root, or
+wait for cron to do it for you (if you don't do this, the new pages can
+still be displayed, they just won't be searchable). The indexing runs
+quickly once the initial database has been created, so the cron job or
+manual update shouldn't bring your system to its knees.
 
 The database is located in /var/cache/man, and on a full Slackware install
 will be approximately 5MB in size. During index creation, approximately