changing 'SBo' to 'slackbuild' in the man pages - better SEO

1 files changed, 6 insertions, 6 deletions

diff --git a/man1/sboinstall.1 b/man1/sboinstall.1
index 8963151..8c6be06 100644
--- a/man1/sboinstall.1
+++ b/man1/sboinstall.1
@@ -1,7 +1,7 @@
 .TH sboinstall 1 "Prickle-Prickle, the 61st day of Discord in the YOLD 3178" "sbotools 0.3 fnord" dawnrazor.net
 .SH NAME
 .P
-sboinstall - install SBos
+sboinstall - install slackbuilds
 .SH SYNAPSES
 .P
 sboinstall [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-N] [-r] [-i] [-p] sbo_name (sbo_name)
@@ -17,7 +17,7 @@ Show help information.
 .P
 -d (TRUE|FALSE)
 .RS
-If TRUE, then DO remove the source code after building the SBo. By default, the source code is not removed, and lives under $SBO_HOME/distfiles, which, by default, is /usr/sbo/distfiles; this option can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default.
+If TRUE, then DO remove the source code after building the slackbuild. By default, the source code is not removed, and lives under $SBO_HOME/distfiles, which, by default, is /usr/sbo/distfiles; this option can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default.
 .RE
 .P
 -j (#|FALSE)
@@ -27,17 +27,17 @@ If numeric (2,5,10, etc), then that number will be fed to the "-j" argument to m
 .P
 -c (TRUE|FALSE)
 .RS
-If TRUE, then DO NOT clean working directories after building the SBo. These are the directories where the source is unpacked and compiled, and where the package is put together in, which are under /tmp/SBo. By default, these directories are removed after building an SBo. This option leaves those directories in place. This can be set as default via the sboconfig(1) command. Also see sbotools.conf(5). This option overrides the default.
+If TRUE, then DO NOT clean working directories after building the slackbuild. These are the directories where the source is unpacked and compiled, and where the package is put together in, which are under /tmp/slackbuild. By default, these directories are removed after building an slackbuild. This option leaves those directories in place. This can be set as default via the sboconfig(1) command. Also see sbotools.conf(5). This option overrides the default.
 .RE
 .P
 -N
 .RS
-Install any new SBos specified. So, if you want to upgrade some things and install new things with the same command, then you would use the -N flag. Note that upgrades are handled prior to new installs.
+Install any new slackbuilds specified. So, if you want to upgrade some things and install new things with the same command, then you would use the -N flag. Note that upgrades are handled prior to new installs.
 .RE
 .P
 -r
 .RS
-Skip viewing of the README and the yes or no question which accompanies it. Anytime sboupgrade or sboinstall is run, the first thing the command will attempt to do is show you the README for a given SBo and ask whether or not you wish to proceed; this option skips the README and bypasses the question. If multiple SBos are specified, this option bypasses them all.
+Skip viewing of the README and the yes or no question which accompanies it. Anytime sboupgrade or sboinstall is run, the first thing the command will attempt to do is show you the README for a given slackbuild and ask whether or not you wish to proceed; this option skips the README and bypasses the question. If multiple slackbuilds are specified, this option bypasses them all.
 .RE
 .P
 -i
@@ -47,7 +47,7 @@ Do not actually install the package created at the end of the build process. So,
 .P
 -p
 .RS
-Create a -compat32 package instead of a normal x86_64 package on multilib x86_64 systems. This requires /usr/sbin/convertpkg-compat32; this can at least be obtained from AlienBob's compat32-tools package - see http://alien.slackbook.org/blog/. Note that this may or may not be foolproof, and is not supported by anyone; not me, not AlienBob, not Slackware, etc. I recommend using this with the -i option so that the created package can be inspected prior to installation. If you find that a particular SBo needs additional help to be created as -compat32 package, contact me at j@dawnrazor.net.
+Create a -compat32 package instead of a normal x86_64 package on multilib x86_64 systems. This requires /usr/sbin/convertpkg-compat32; this can at least be obtained from AlienBob's compat32-tools package - see http://alien.slackbook.org/blog/. Note that this may or may not be foolproof, and is not supported by anyone; not me, not AlienBob, not Slackware, etc. I recommend using this with the -i option so that the created package can be inspected prior to installation. If you find that a particular slackbuild needs additional help to be created as -compat32 package, contact me at j@dawnrazor.net.
 .RE
 .P
 -v