More spelling corruptions

Author: netniV

Data-Queries.md

@@ -121,10 +121,10 @@ Field | Description
 --- | ---
 query->name | (Optional) You can enter a "friendly name" for the SNMP query here. It will not be used by Cacti, and is for identification only.
 query->description | (Optional) You can enter a description for the SNMP query here. It will not be used by Cacti, and is for identification only.
-query->oid_uptime | New with 0.8.7: If you have another OID that contains timetics, say for example a Java VM. Then, you can create a data query that specifies an alternate Uptime OID. To implement this for a data query, simply add the oid_uptime XML parameter to your XML file. Then, if you select your re-index method to be Uptime Goes Backward, Cacti will use that OID to detect whether it is time to re-index the host instead of the standard snmp OID for uptime.
+query->oid_uptime | New with 0.8.7: If you have another OID that contains ticks (time), say for example a Java VM. Then, you can create a data query that specifies an alternate uptime OID. To implement this for a data query, simply add the oid_uptime XML parameter to your XML file. Then, if you select your re-index method to be Uptime Goes Backward, Cacti will use that OID to detect whether it is time to re-index the host instead of the standard SNMP OID for uptime.
 query->oid_index | Every SNMP query must have an OID that represents the index values for the query when walked. As described above, any data query in Cacti must contain a field that uniquely identifies each row returned by the query. In the example above, the oid_index points to the OID of ifIndex in the interface MIB. Note: Starting with version 0.8.6c, Cacti is able to parse unique indexes from the OID itself. While the regular expression used for parsing the value from the OID is defined below, you must still specify an OID that can be walked by Cacti in order to obtain the list of OID's. Any OID defined for one of your input fields should work in this case. The values returned from the snmpwalk walk will be completely disregarded.
 query->oid_index_parse | This field should only be used if you are trying to parse the unique index from the OID itself. If this field is defined, to obtain a list of indexes, Cacti walks the OID provided in the oid_index field above. It then applies the regular expression provided in this field to the list of OID's that are returned. The matched substrings that remain become the list of indexes for this SNMP query.
-query->oid_num_indexes | An OID that can be queried to determine the total number of available indexes. If specified, this will be used to determine when to automatically recache this SNMP query when it is attached to a device.
+query->oid_num_indexes | An OID that can be queried to determine the total number of available indexes. If specified, this will be used to determine when to automatically re-cache this SNMP query when it is attached to a device.
 query->index_order | As of version 0.8.6, Cacti will attempt to find the best field to index off of based on whether each row in the query is unique and non-null. If specified, Cacti will perform this check on the fields listed here in the order specified. Only input fields can be specified and multiple fields should be delimited with a colon.
 query->index_order_type | For sorting purposes, specify whether the index is numeric or alphanumeric. numeric: The indexes in this SNMP query are to be sorted numerically (ie. 1,2,3,10,20,31) alphabetic: The indexes in this SNMP query are to be sorted alphabetically (1,10,2,20,3,31).
 query->index_title_format | Specify the title format to use when representing an index to the user. Any input field name can be used as a variable if enclosed in pipes (|). The variable `|chosen_order_field|` will be substituted with the field chosen by Cacti to index off of (see index_order above).
@@ -172,7 +172,7 @@ query->script_path | Enter the complete path to the script or executable that is
 query->arg_index | Enter the argument that is to be passed to the script to retrieve a list of indexes.
 query->arg_query | Enter the argument that is to be passed to the script to retrieve a list of values given a field name.
 query->arg_get | Enter the argument that is to be passed to the script to retrieve a single value given a field name and index value.
-query->arg_num_indexes | Enter the argument that is to be passed to the script to determine the total number of available indexes. If specified, this will be used to determine when to automatically recache this script query when it is attached to a device.
+query->arg_num_indexes | Enter the argument that is to be passed to the script to determine the total number of available indexes. If specified, this will be used to determine when to automatically re-cache this script query when it is attached to a device.
 query->output_delimeter | Enter the one character delimiter that will be used to separate output values. This is only used when you "query" the script in which case it outputs 'index(delimiter)value'.
 query->index_order | As of version 0.8.6, Cacti will attempt to find the best field to index off of based on whether each row in the query is unique and non-null. If specified, Cacti will perform this check on the fields listed here in the order specified. Only input fields can be specified and multiple fields should be delimited with a comma.
 query->index_order_type | For sorting purposes, specify whether the index is numeric or alphanumeric. numeric: The indexes in this script query are to be sorted numerically (ie. 1,2,3,10,20,31) alphabetic: The indexes in this script query are to be sorted alphabetically (1,10,2,20,3,31).

Debugging.md

@@ -17,12 +17,12 @@ change this, see `Settings`, `Poller` and lower the value for `The Maximum SNMP
 OID's Per SNMP Get Request`. Start at a value of 2 and increase it again, if
 the poller starts working. (1 or less disables snmpbulkwalk) Some agent's don't
 have the horsepower to deliver that many OID's at a time. Therefore, we can
-reduce the number for those older/underpowered devices.
+reduce the number for those older/under-powered devices.
 
 ## Check Basic Data Gathering
 
-For scripts, run them as cactiuser from cli to check basic functionality. E.g.
-for a perl script named `your-perl-script.pl` with parameters "p1 p2" under
+For scripts, run them as cactiuser from CLI to check basic functionality. E.g.
+for a Perl script named `your-perl-script.pl` with parameters "p1 p2" under
 *nix this would look like:
 
 ```sh
@@ -31,8 +31,8 @@ su - cactiuser
 ... (check output)
 ```
 
-For snmp, snmpget the _exact_ OID you're asking for, using same community
-string and snmp version as defined within cacti. For an OID of
+For SNMP, snmpget the _exact_ OID you're asking for, using same community
+string and SNMP version as defined within cacti. For an OID of
 `.1.3.6.1.4.something`, community string of `very-secret` and version 2 for
 target host `target-host` this would look like
 
@@ -41,12 +41,12 @@ snmpget -c very-secret -v 2c target-host .1.3.6.1.4.something
 .... (check output)
 ```
 
-## Check cacti's poller
+## Check Cacti's poller
 
 First make sure that crontab always shows poller.php. This program will either
-call cmd.php, the PHP based poller _or_ cactid, the fast alternative, written
-in C. Define the poller you're using at `Settings`, `Poller`. Cactid has to be
-implemented seperately, it does not come with cacti by default.
+call cmd.php, the PHP based poller _or_ spine, the fast alternative, written
+in C. Define the poller you're using at `Settings`, `Poller`. Spine has to be
+implemented separately, it does not come with cacti by default.
 
 Now, clear `./log/cacti.log` (or rename it to get a fresh start)
 
@@ -56,12 +56,12 @@ subsequent polling cycles.
 
 Now, find the host/data source in question. The `Host[<id>]` is given
 numerically, the `<id>` being a specific number for that host. Find this `<id>`
-from the `Devices` menue when editing the host: The url contains a string like
+from the `Devices` menu when editing the host: The URL contains a string like
 
 `id=<id>`
 
 Check, whether the output is as expected. If not, check your script (e.g.
-`/full/path/to/perl`). If ok, proceed to next step
+`/full/path/to/perl`). If OK, proceed to next step
 
 This procedure may be replaced by running the poller manually for the failing
 host only. To do so, you need the `<id>`, again. If you're using cmd.php, set the
@@ -71,13 +71,13 @@ DEBUG logging level as defined above and run
 php -q cmd.php <id> <id>
 ```
 
-If you're using cactid, you may override logging level when calling the poller:
+If you're using spine, you may override logging level when calling the poller:
 
 ```sh
-./cactid --verbosity=5 <id> <id>
+./spine --verbosity=5 <id> <id>
 ```
 
-All output is printed to STDOUT in both cases. This procdure allows for
+All output is printed to STDOUT in both cases. This procedure allows for
 repeated tests without waiting for the next polling interval. And there's no
 need to manually search for the failing host between hundreds of lines of
 output.
@@ -88,11 +88,11 @@ In most cases, this step can be skipped. You may want to return to this step if
 the next one fails (e.g. no rrdtool update to be found)
 
 From debug log, find the MySQL update statement for that host concerning table
-`poller_output`. On very rare occasions, this will fail. Copy that sql
-statement and paste it to a mysql session started from cli. This may as well be
-done from some tool like phpMyAdmin. Check the sql return code.
+`poller_output`. On very rare occasions, this will fail. Copy that SQL
+statement and paste it to a mysql session started from CLI. This may as well be
+done from some tool like phpMyAdmin. Check the SQL return code.
 
-## Check rrd file updating
+## Check RRD file updating
 
 Down in the same log, you should find some
 
@@ -106,9 +106,9 @@ RRD files should be created by the poller. If it does not create them, it will
 not fill them either. If it does check your `Poller Cache` from Utilities and
 search for your target. Does the query show up here?
 
-## Check rrd file ownership
+## Check RRD file ownership
 
-If rrd files were created e.g. with root ownership, a poller running as
+If RRD files were created e.g. with root ownership, a poller running as
 cactiuser will not be able to update those files
 
 ```sh
@@ -127,23 +127,23 @@ Run the following command to cure this problem
 chown cactiuser:cactiuser *.rrd
 ```
 
-## Check rrd file numbers
+## Check RRD file numbers
 
-You're perhaps wondering about this step, if the former was ok. But due to data
+You're perhaps wondering about this step, if the former was OK. But due to data
 sources MINIMUM and MAXIMUM definitions, it is possible, that valid updates for
-rrd files are suppressed, because MINIMUM was not reached or MAXIMUM was
+RRD files are suppressed, because MINIMUM was not reached or MAXIMUM was
 exceeded.
 
 Assuming, you've got some valid `rrdtool update` in step 3, perform a
 
 ```sh
-rrdtool fetch <rrd file> AVERAGE
+rrdtool fetch <RRD file> AVERAGE
 ```
 
 and look at the last 10-20 lines. If you find NaN's there, perform
 
 ```sh
-rrdtool info <rrd file>
+rrdtool info <RRD file>
 ```
 
 and check the `ds[...].min` and `ds[...].max` entries, e.g.
@@ -161,26 +161,26 @@ If you run into this, not only should you update the data source definition
 within the Data Template, but also perform a:
 
 ```sh
-rrdtool tune <rrd file> --maximum <ds-name>:<new ds maximum>
+rrdtool tune <RRD file> --maximum <ds-name>:<new ds maximum>
 ```
 
-for all existing rrd files belonging to that Data Template.
+for all existing RRD files belonging to that Data Template.
 
-At this step, it is wise to check `step` and `heartbeat` of the rrd file as
+At this step, it is wise to check `step` and `heartbeat` of the RRD file as
 well. For standard 300 seconds polling intervals (step=300), it is wise to set
 `minimal_heartbeat` to 600 seconds. If a single update is missing and the next
 one occurs in less than 600 seconds from the last one, rrdtool will interpolate
 the missing update. Thus, gaps are "filled" automatically by interpolation. Be
 aware of the fact, that this is no "real" data! Again, this must be done in the
-Data Template itself and by using rrdtool tune for all existing rrd files of
+Data Template itself and by using rrdtool tune for all existing RRD files of
 this type.
 
 ## Check rrdtool graph statement
 
-Last resort would be to check, that the correct data sources are used. Goto
+Last resort would be to check, that the correct data sources are used. Go to
 `Graph Management` and select your Graph. Enable DEBUG Mode to find the whole
 `rrdtool graph` statement. You should notice the `DEF` statements. They specify
-the rrd file and data source to be used. You may check, that all of them are as
+the RRD file and data source to be used. You may check, that all of them are as
 wanted.
 
 ## Miscellaneous
@@ -191,7 +191,7 @@ reasonable size.
 This is commonly due to php.ini's memory settings of 8MB default. Change this
 to at least 64 MB.
 
-To check this, run the following sql from mysql cli (or phpmyadmin or the like)
+To check this, run the following SQL from mysql CLI (or phpmyadmin or the like)
 
 ```sql
 select count(*) from poller_output;
@@ -213,10 +213,10 @@ installation instructions to the letter (which you should always do ;-) ), you
 may now have two poller running. That's not a good thing, though. Most rpm
 installations will setup cron in `/etc/cron.d/cacti`
 
-Now check all your crontabs, especially `/etc/crontab` and crontabs of users
+Now check all your crontab, especially `/etc/crontab` and crontab of users
 root and cactiuser. Leave only one poller entry for all of them. Personally,
-I've chosen `/etc/cron.d/cacti` to avoid problems when updating rpm's. Mosten
-often, you won't remember this item when updating lots of rpm's, so I felt more
+I've chosen `/etc/cron.d/cacti` to avoid problems when updating RPM's. Mosten
+often, you won't remember this item when updating lots of RPM's, so I felt more
 secure to put it here. And I've made some slight modifications, see
 
 ```sh

Frequently-Asked-Questions.md

@@ -66,7 +66,7 @@ mysql> update user_auth set password=md5('admin') where username='admin';
 to run.
 
 **A:** Give Spine, the fast replacement for poller.php a try. Unlike
-poller.php, Spine is written in c and makes use of pthreads. On a typical
+poller.php, Spine is written in c and makes use of threads. On a typical
 installation, it is not uncommon for Spine to poll about 500 items in less then
 10 seconds.
 
@@ -148,7 +148,7 @@ the Visual tab, and changing the value for Data Queries - Maximum Field Length.
 
 **Q:** One of my devices rebooted and now I have a huge spike on my graph!
 
-**A:** This occurs because the reboot causes SNMP's counters to reset, which
+**A:** This occurs because the reboot causes SNMP counters to reset, which
 can cause a rather large spike on the graph when RRDTool tries to determine the
 change between the new small counter value and the large previous value. One
 way to combat this issue is to specify realistic maximum values for your data

Graph-a-Single-SNMP-OID.md

@@ -24,7 +24,7 @@ Name | Description
 (Graph Items) Legend Text | The text that will be used to describe the data on the graph legend.
 (Data Source) Name | The title that is to be used for the new data source. It is generally a good idea to keep |host_description| in the title, as to make the data source easier to identify later.
 (Data Source) Maximum Value [snmp_oid] | The maximum value that will be accepted from the OID. Make sure you choose a value that is reasonable for the data you are trying to graph because anything larger than the maximum will be ignored. If you are graphing a percentage, you should use '100' as the value should never exceed this.
-(Data Source) Data Source Type [snmp_oid] | How the data from the OID should be stored by RRDTool and interpreted on the graph. If the value of the OID represents the actual data, you should use GAUGE for this field. If the OID value is a constantly incrementing number, you should use COUNTER for this field. The two remaining field values, DERIVE and ABSOLUTE can be ignored in most situations.
+(Data Source) Data Source Type [snmp_oid] | How the data from the OID should be stored by RRDTool and interpreted on the graph. If the value of the OID represents the actual data, you should use GAUGE for this field. If the OID value is a constantly incremented number, you should use COUNTER for this field. The two remaining field values, DERIVE and ABSOLUTE can be ignored in most situations.
 (Custom Data) OID | The actual SNMP OID to graph. It is typically a good idea to enter the number OID here as opposed to using MIB names. For instance, to get the number of open files on a Netware server, you would use ".1.3.6.1.4.1.23.2.28.2.7.0" as the OID.
 
 You will be presented with several fields that will require input before the

Install-Under-CentOS_LAMP.md

@@ -27,7 +27,7 @@ files holding your certificate (`.crt`) and private key (`.key`).
 
 ```console
 #
-# Cacti: An rrd based graphing tool
+# Cacti: An RRD based graphing tool
 #
 
 # For security reasons, the Cacti web interface is accessible only to
@@ -100,9 +100,9 @@ files holding your certificate (`.crt`) and private key (`.key`).
 The choice between MySQL server and MariaDB is normally down to the OS
 maintainers if you use one of the predefined LAMP setup installations.  If you
 are deciding between these yourself, you should research this via your
-favourite search engine.
+favorite search engine.
 
-Whilst MySQL is the original open source sql database server created in 1995
+Whilst MySQL is the original open source SQL database server created in 1995
 which is now owned by Oracle, MariaDB is designed as a drop-in replacement by
 some of the original MySQL developers / owners.  This will likely continue to
 be a drop-in alternative until there is a major divergence that can not be
@@ -373,33 +373,33 @@ Make sure to setup the correct path to poller.php
 
 ### Security Enhanced Linux (SELinux)
 
-If you are having issues to access the web page, disable selinux temporarily to
-prove that the issues come from the selinux policy. It is NOT recommended to
-disable SELINUX permanently.
+If you are having issues to access the web page, disable SELinux temporarily to
+prove that the issues come from the SELinux policy. It is NOT recommended to
+disable SELinux permanently.
 
 [CentOS](https:////wiki.centos.org/es/HowTos/SELinux) has a lot of
-documentation on how to make your selinux policy right.
+documentation on how to make your SELinux policy right.
 
-1. Check selinux status
+1. Check SELinux status
 
    ```console
    getenforce
    ```
 
-2. Disable selinux temporarily
+2. Disable SELinux temporarily
 
    ```console
    setenforce 0
    ```
 
-3. Enable selinux back
+3. Enable SELinux back
 
    ```console
    setenforce 1
    ```
 
 **Note:** If you installed Cacti out of `/var/www/html` make sure you fix up
-all selinux context and permissions.
+all SELinux context and permissions.
 
 ---
 Copyright (c) 2004-2019 The Cacti Group