=head1 DESCRIPTION
This program is run on each Unix machine in which you want
-to monitor local system attributes, and report that information to the
+to monitor local system attributes, and reports that information to the
spong server. It runs one or more configured checks. It then sleeps for
a time period you have defined in your configuration file and does it all
again (it actually adds or subtracts a random amount of time - no more
=head2 Running the program
You should start this program in your system startup file, and it should be
-running constantly. If no parameters are specified, B<spong-network> forks
+running constantly. If no parameters are specified, B<spong-client> forks
and detaches itself to run as a daemon.
If you provide the B<--debug> I<n> flag, then debugging information will be
The B<--nosleep> or B<--refresh> flag causes the program to cycle through all
of the checks once then exit. These flags can be used to run spong-client as a
-cron job (B<depreciated>), this reduced the effectiveness of the B<check_logs>
+cron job (B<depreciated>), this reduces the effectiveness of the B<check_logs>
module.
=head2 Client Checks
B<spong-client>. The list of modules to run are defined in the I<$CHECKS>
configuration variable. Upon initialization, B<spong-client> will load the
modules defined in I<$CHECKS> from the F<LIBDIR/Spong/Client/plugins/>
-directory. As each modules is initialized, it registers itself with the the
+directory. As each module is initialized, it registers itself with the the
plugins registry (see the L<Developer Guide|developer-guide>).
=head2 Extending Functionality
=item $SPONGTMP
The directory that Spong programs use for temporary store and work files. It
-should be different directory than F</tmp> for operation and security reasons.
+should be a different directory than F</tmp> for operation and security reasons.
=item $SPONG_LOG_FILE
=item status
-the status color to reported lines matching pattern
+the status color to reporte when lines match pattern
=item duration
=head1 BUGS
-None know bugs.
+No known bugs.
=head1 SEE ALSO
If you provide the B<--restart> flag, a signal will be sent to the B<spong-network>
process that is currently running that will cause it to reload it's
configuration files. If you provide the B<--kill> flag, a signal will be sent
-to the running spong-client process causing it to exit.
+to the running spong-network process causing it to exit.
The B<--nosleep> or B<--refresh> flag causes the program to cycle through all
-of the checks once then exit. These flags can be used to run spong-client as a
+of the checks once then exit. These flags can be used to run spong-network as a
cron job (B<depreciated>), but it recommended that you run the program
continuously.
=item $SPONGTMP
The directory that Spong programs use for temporary store and work files. It
-should be different a directory than F</tmp> for operation and security reasons.
+should be a different directory than F</tmp> for operation and security reasons.
=item $SPONG_LOG_FILE
All of the host names defined in %HOSTS are the list of hosts that
B<spong-network> will check. The services defined in the I<services> attribute
-are the list of services that will be check for each host. The I<ping> service
+are the list of services that will be checked for each host. The I<ping> service
is prepended to the list of services unless 'noping' is defined.
Another important attribute for a host is the
L<skip_network_checks|spong.hosts/"skip_network_check"> flag. If this flag is
-set for a host. The B<spong-network> proram will skip the check for the host.
+set for a host, the B<spong-network> program will skip the check for the host.
=back