typos

Author: Linegod

Cacti-Log.md

@@ -6,10 +6,10 @@ The Cacti Log is where all Cacti statistics, warnings, errors and other log mess
 are sent to. Cacti can optionally log some information to your syslog or event log
 depending on your OS type.
 
-The Cacti Log is by default ordered from newest event to oldest event, a
-nd the Cacti Log is rotated by Cacti itself once a day.
+The Cacti Log is by default ordered from newest event to oldest event, and
+the Cacti Log is rotated by Cacti itself once a day.
 
-If you have the User Level permission, you can view any available Cacti Stadard
+If you have the User Level permission, you can view any available Cacti Standard
 Output or Standard Error log. If you have the Administrative level access,
 you may additionally purge information from the logs.
 

Data-Queries.md

@@ -231,7 +231,7 @@ shell> vi /etc/cron.d/cacti
 ```
 
 This will produce a file `/var/local/log/poller.log`, which includes some
-additional informations from each poller's run, such as RRDtool errors. It
+additional information from each poller's run, such as RRDtool errors. It
 occupies only some few bytes and will be overwritten each time.
 
 If you're using the crontab of user "cactiuser" instead, this will look like

Debugging.md

@@ -59,7 +59,7 @@ They include:
   Instance OID
 - **Ping** - Either ICMP, TCP at a port, or UDP as a port
 - **Ping or SNMP Uptime** - Only one needs to be working for Cacti to collect data
-- **SNMP Desc** - Query the SNMP sysDecription in cases where the SNMP Uptime OID
+- **SNMP Desc** - Query the SNMP sysDescription in cases where the SNMP Uptime OID
   is not available
 - **SNMP GetNext** - Query the first available OID in the OID tree for the **Device**
   Used for certain devices that have limited SNMP support.

Devices.md

@@ -255,7 +255,7 @@ is fine
 
 **A:** Check that the network connection between the Remote poller and Main
 poller is working ok if the link has very high latency this can cause the
-polling times to increase as the data being transfered from the remote poller
+polling times to increase as the data being transferred from the remote poller
 will be slowed causing the poll not to finish in time
 
 ---

Frequently-Asked-Questions.md

@@ -92,7 +92,7 @@ The following modules are optional, but preferred to be installed.
 ### A special note for systems using PHP-FPM
 
 Prior to starting the setup process of Cacti you should restart the PHP-FPM
-Daemon to rebuild the Cache or you may recive a HTTP 500 Error
+Daemon to rebuild the Cache or you may receive a HTTP 500 Error
 
 ```console
 systemctl restart php-fpm
@@ -364,7 +364,7 @@ the downloaded directory following commands
 shell>./bootstrap
 ```
 
-If the `boostrap` script is successful, you then will follow the instructions it
+If the `bootstrap` script is successful, you then will follow the instructions it
 provides to compile and install.
 
 Assuming, you've managed to install spine correctly, you will have to configure

General-Installing-Instructions.md

@@ -126,7 +126,7 @@ for a long time, selecting this option can really slow the **Graph** creation pr
  that you create using the **Device Template**.
 
 Under the *Common Options*, for each **Graph Template** you will specify patterns
-for the *Graph Name*, assign it's *Veritcal Label*, specify the *Width* and *Height*,
+for the *Graph Name*, assign it's *Vertical Label*, specify the *Width* and *Height*,
 and *Image Format* for the resulting **Graph**.  The *Base Value* is important
 as some units of measure can be for example: MB (for Mega Bytes - 1024) and MiB (for
 Mega integer Bytes - 1000).  Lastly, the *Slope Mode* gives the resulting

Graph-Templates.md

@@ -48,7 +48,7 @@ So, based upon your specific OID that you are graphing, You will need to fill
 out these fields before the new graph can be created properly.
 
 When finished filling in values for these fields, click the Create button. Your
-new **Graph** can now be accessed through the `Cosole > Management > Graphs`
+new **Graph** can now be accessed through the `Console > Management > Graphs`
 menu pick.
 
 > **NOTE**: When comparing the Table above, to the image, you will see that the

Graph-a-Single-SNMP-OID.md

@@ -7,13 +7,13 @@ the administrator to view the graphs that are attached to a specific device. You
 can also search by type of graph. Below we search for graphs that are
 associated with the local linux server
 
-![graph management](images/graph-managment.png)
+![graph management](images/graph-management.png)
 
 Clicking on one of the graphs in the list shows the below menu. From this menu
 you can enable debugging on the specific graph you can also change the template
 of the graph amongst other things
 
-![Graph management click](images/graph-managment-graph.png)
+![Graph management click](images/graph-management-graph.png)
 
 ### Modifying the graph template
 

Graphs.md

@@ -10,7 +10,7 @@ apt-get install -y apache2 rrdtool mariadb-server snmp snmpd php8.0 php8.0-mysql
 ### A special note for systems using PHP-FPM
 
  Prior to starting the setup process of Cacti you should restart the PHP-FPM
- Daemon to rebuild the Cache or you may recived a HTTP 500 Error
+ Daemon to rebuild the Cache or you may received a HTTP 500 Error
 
 ```console
 systemctl restart php-fpm

Installing-Under-Ubuntu-Debian.md

@@ -9,7 +9,7 @@ The best place to go for discovering what Bugs or Issue exist in Cacti is
 to goto [GitHub](https://www.github.com/Cacti/cacti).  From there, you can
 view not only the Cacti repo, but a collection of Cacti Group mainteined
 **Plugins**.  For the Core Cacti and for every Plugin, there is an issue
-tracker site the coresponds to it.  Issues are generally broken into
+tracker site the corresponds to it.  Issues are generally broken into
 [Enhancements](https://github.com/Cacti/cacti/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement)
 and [Bugs](https://github.com/Cacti/cacti/issues?q=is%3Aopen+is%3Aissue+label%3Abug).
 

Known-Issues.md

@@ -40,7 +40,7 @@ setting | description
 *compat* | The minimum version of Cacti that is required to use this plugin.
 *depends* | A space delimited list of plugins:version that are required to use this plugin.
 *capabilities* | A comma delimited list of capabilities for define what capabilities the plugin has primarily remotely.
-*nosync* | A comma delimited list of relative paths that should not be syncronized with the remote data collectors, for example transient folders that may contain quite a bit of data that changes often.
+*nosync* | A comma delimited list of relative paths that should not be synchronized with the remote data collectors, for example transient folders that may contain quite a bit of data that changes often.
 
 ## Functions