Spellchecker : Fix or rephrase issues found by spellchecker, and upda…

…te the NUT custom dictionary

TODO

@@ -113,6 +113,6 @@ and https://alioth.debian.org/tracker/?atid=411545&group_id=30602&func=browse[fe
 solar panel driver, and the powerman internal approach of a generic engine with
 a scripting interface is a cool idea.
 Ref http://powerman.svn.sourceforge.net/viewvc/powerman/trunk/etc/apcpdu.dev?revision=969&view=markup
-- integrate the (future) new powerman LUA engine (maybe/mustbe used for the driver above?)
+- integrate the (future) new powerman LUA engine (maybe/must-be used for the driver above?)
 for native PDU support
 - see how we can help and collaborate with DeviceKit-power

UPGRADING

@@ -171,7 +171,7 @@ Changes from 2.2.1 to 2.2.2
 This enable the additional build and distribution of the static
 version of libupsclient, along with the pkg-config helper and manual
 pages. The default configure option is to distribute only the shared
-version of libupsclient. This can be overriden by using the
+version of libupsclient. This can be overridden by using the
 "--disable-shared" configure option (distribute static only binaries).
 - The UPS poweroff handling of the usbhid-ups driver has been reworked.
 Though regression is not expected, users of this driver are
@@ -182,7 +182,7 @@ Changes from 2.2.0 to 2.2.1
 ---------------------------
 
 - nothing that affects upgraded systems.
-(The below message is repetead due to previous omission)
+(The below message is repeated due to previous omission)
 - Developers of external client application using libupsclient are
 encouraged to rename their "UPSCONN" client structure to "UPSCONN_t"
 since the former will disappear by the release of NUT 2.4.

common/parseconf.c

@@ -171,7 +171,7 @@ static void addchar(PCONF_CTX_t *ctx)
 
 	wbuflen = strlen(ctx->wordbuf);
 
-	/* CVE-2012-2944: only allow the subset Ascii charset from Space to ~ */
+	/* CVE-2012-2944: only allow the subset of ASCII charset from Space to ~ */
 	if ((ctx->ch < 0x20) || (ctx->ch > 0x7f)) {
 		fprintf(stderr, "addchar: discarding invalid character (0x%02x)!\n",
 				ctx->ch);

docs/FAQ.txt

@@ -526,7 +526,7 @@ Either find the pid of the background process and send it a SIGHUP,
 or just start it again with '-c reload'.
 
 If you send the signals yourself instead of using -c, be sure you
-hit the right process.  There are usually two upsmons, and you
+hit the right process.  There are usually two upsmon processes, and you
 should only send signals to one of them.  To be safe, read the pid
 file.
 
@@ -539,7 +539,7 @@ There are several driver to support USB models.
 - bcmxcp_usb supports various Powerware units,
 - nutdrv_qx and blazer_usb support various manufacturers that use the Megatec / Q1 protocol.
 
-Refer to the 'driver-name' (8) manpage for more information.
+Refer to the 'driver-name' (8) man page for more information.
 
 You can also consult the Hardware Compatibility List (HCL) and filter on USB:
 http://www.networkupstools.org/stable-hcl.html?connection=USB
@@ -567,7 +567,7 @@ Instead of unplugging, you might also be able to run `udevadm trigger
 There was a mistake in the naming of the NUT udev rules file which resulted in
 the rules being overridden by another udev configuration file. While this has
 been fixed in the Git master branch, your distribution may still be affected.
-Details are available in the following Github issue:
+Details are available in the following GitHub issue:
 https://github.com/networkupstools/nut/issues/140
 
 == Why do you not use the Linux kernel HID driver when communicating with USB UPSes?
@@ -657,8 +657,8 @@ version out there.
 
 If you are not actively developing a driver, can you use a snapshot instead?
 The NUT instance of Buildbot generates tar files of the latest NUT source
-after each successful build, and these snapshots include a prebuilt version of
-the `./configure` script.
+after each successful build, and these snapshots include a pre-built version
+of the `./configure` script.
 
 Otherwise, you will need recent versions of autoconf, automake, libtool,
 asciidoc, a2x and its dependencies for DocBook/dblatex. Rather than publish a

docs/acknowledgements.txt

@@ -32,7 +32,7 @@ Active members
 - Jean Perriault: web consultant
 - Eric S. Raymond: Documentation consultant
 - Oden Eriksson: Mandriva packager
-- Stanislav Brabec: Novell / Suse packager
+- Stanislav Brabec: Novell / SUSE packager
 - Michal Hlavinka: Redhat packager
 - Antoine Colombier: trainee
 

docs/cables/sms.txt

@@ -11,6 +11,6 @@ FEMEA DB9      MACHO DB9
 4/8  ----------  5
 5    ----------  8
 
-- This cable is working with Manager III 1300 VA and 650 VA, SMS Ups's 
-- Jump in computer side pins 4/8 and conect to pin 1 in UPS side
+- This cable is working with Manager III 1300 VA and 650 VA, SMS UPS's
+- Jump in computer side pins 4/8 and connect to pin 1 in UPS side
 - Use NUT blazer_ser driver

docs/config-notes.txt

@@ -139,7 +139,7 @@ NOTE: USB drivers (usbhid-ups, bcmxcp_usb, tripplite_usb, blazer_usb and
 richcomm_usb) are special cases and ignore the 'port' value.
 You must still set this value, but it does not matter what you set
 it to; a common and good practice is to set 'port' to *auto*, but you can
-put whatever you like. If you only own one UBS UPS, the driver will
+put whatever you like. If you only own one USB UPS, the driver will
 find it automatically. If you own more than one, refer to the driver's
 manual page for more information on matching a specific device.
 

docs/download.txt

@@ -108,7 +108,7 @@ link:http://packages.debian.org/nut[Debian],
 link:http://packages.gentoo.org/package/sys-power/nut[Gentoo Linux],
 Mandriva,
 link:https://apps.fedoraproject.org/packages/nut[Red Hat / Fedora],
-link:http://software.opensuse.org/package/nut[Novell Suse / openSUSE],
+link:http://software.opensuse.org/package/nut[Novell SUSE / openSUSE],
 link:https://github.com/openwrt/packages/tree/master/net/nut[OpenWrt],
 link:http://sotirov-bg.net/slackpack/search.cgi?q=nut[Slackware],
 link:http://packages.ubuntu.com/nut[Ubuntu],

docs/hid-subdrivers.txt

@@ -191,7 +191,7 @@ subdrivers are written.:
 Shutting down the UPS
 ~~~~~~~~~~~~~~~~~~~~~
 
-It is desireable to support shutting down the UPS. Usually (for
+It is desirable to support shutting down the UPS. Usually (for
 devices that follow the HID Power Device Class specification), this
 requires sending the UPS two commands. One for shutting down the UPS
 (with an 'offdelay') and one for restarting it (with an 'ondelay'),

docs/new-drivers.txt

@@ -32,7 +32,7 @@ A rough heuristic is to check the length of the HID Descriptor length
 (`wDescriptorLength` in `lsusb -v` output). If it is less than 200 bytes long,
 the UPS probably has a glorified USB-to-serial converter built in. Since the
 query strings often start with the letter `Q`, this family of protocols is
-often refered to as `Q*` in the NUT documentation. See the
+often referred to as `Q*` in the NUT documentation. See the
 <<nutdrv_qx-subdrivers,Q* UPS>> chapter for more details.
 
 Otherwise, if the HID Descriptor is longer, you can go to the

docs/nut-qa.txt

@@ -55,7 +55,7 @@ NUT promotes and uses many standards, such as:
 QA tools and metrics
 ~~~~~~~~~~~~~~~~~~~~
 
-NUT's quality is constently monitored using many tools, like:
+NUT's quality is constantly monitored using many tools, like:
 
 - a Revision Control System (link:https://github.com/networkupstools/nut[Git]) to
 track development and ease regression fixes.
@@ -78,7 +78,7 @@ link:http://lists.alioth.debian.org/mailman/listinfo/nut-commits[NUT Commits]
 mailing list, and fixed quickly.
 ////////////////////////////////////////////////////////////////////////////////
 
-- a project portal with trackers for bugs, feature request, patchs and tasks
+- a project portal with trackers for bugs, feature request, patches and tasks
 
 - Static code analysis:
   * link:https://scan.coverity.com/projects/networkupstools-nut[Coverity Scan overview of NUT]