spelling check of docs directory

Author: jaegeral

docs/API_Doc.md

@@ -659,7 +659,7 @@ Simply run a get request on this endpoint to get the relevant log entries for a
 
 # Organisations
 ## Add
-POST an Organisation object in JSON format to this API to create a new organsiation.
+POST an Organisation object in JSON format to this API to create a new organisation.
 ```
 /admin/organisations/add
 ```
@@ -683,7 +683,7 @@ POST an Organisation object in JSON format to this API to create a new organsiat
 | local |integer |If the organisation should have access to this instance, make sure that the Local organisation setting is checked. If you would only like to add a known external organisation for inclusion in sharing groups, uncheck the Local organisation setting. |
 
 ## Edit
-POST an Organisation object in JSON format to this API to create a new organsiation.
+POST an Organisation object in JSON format to this API to create a new organisation.
 ```
 /admin/organisations/edit
 ```
@@ -997,7 +997,7 @@ Untag an event or attribute. Tag can be the id or the name.
 
 
 ## AttachTagToObject
-Attach a Tag to an object, refenced by an UUID. Tag can either be a tag id or a tag name.
+Attach a Tag to an object, referenced by an UUID. Tag can either be a tag id or a tag name.
 ```
 /tags/attachTagToObject
 ```

docs/CONFIG.ApacheSecureAuth.md

@@ -34,7 +34,7 @@ the browser forget these.
 There is no common or properly defined way of "logging out" after logging in with HTTP Basic Auth.
 
 If the user presses the GUI "Log out" link, this can result in a logout-login loop, where the user
-is logged out, but then immediately loggged back in by means of the browsers cached HTTP Basic Auth
+is logged out, but then immediately logged back in by means of the browsers cached HTTP Basic Auth
 credentials. This can be observed when a user presses "Log out", for then to be returned to the 
 events view with two flash messages - one about a successful logout, and one "Welcome back" login-message.
 

docs/UPDATE.md

@@ -5,7 +5,7 @@ It is **very strongly recommended** to upgrade MISP via the web interface. This
 
 # Point release updates
 !!! notice
-    In general, updating MISP between point releases (for exampe 2.4.50 -> 2.4.53) happens with one of the following two options (both are to be executed as root).
+    In general, updating MISP between point releases (for example 2.4.50 -> 2.4.53) happens with one of the following two options (both are to be executed as root).
 
 ## Option 1
 

docs/archive/xINSTALL.debian9-postgresql.md

@@ -60,7 +60,7 @@ psql -U misp -d misp -f /var/www/MISP/INSTALL/POSTGRESQL-data-initial.sql -h loc
 
 
 # ATTENTION: skip this step if you want to migrate from MySQL/MariaDB!
-# perhaps you accidently installed MySQL/MariaDB, too - but you can clean it up like this
+# perhaps you accidentally installed MySQL/MariaDB, too - but you can clean it up like this
 sudo apt-get remove mysql-server mysql-client mariadb-client mariadb-server php5-mysql
 
 

docs/archive/xINSTALL.ubuntu1804.with.webmin.md

@@ -286,7 +286,7 @@ Most of it should have been done when you created the subdomain but add these ch
 
         <Directory /home/misp/public_html/MISP/app/webroot>
 
-# The rest should't require modifications. Restart Apache
+# The rest shouldn't require modifications. Restart Apache
 
 sudo service apache2 restart
 ```

docs/background-jobs-migration-guide.md

@@ -1,5 +1,5 @@
 # Migration guide to new Background Jobs backend
-As of **MISP** version `2.4.151` we introduced a simpler way to handle background jobs without relying in CakeResque as this library is no longer mantained.
+As of **MISP** version `2.4.151` we introduced a simpler way to handle background jobs without relying in CakeResque as this library is no longer maintained.
 
 For the time being both background jobs backends will be supported, but we plan to phase out the CakeResque one in a near future.
 

docs/correlations.rework.md

@@ -37,7 +37,7 @@ Despite the re-correlation potentially taking a long time, your instance will st
 ### Some precautions you can take to ease the process:
 
 - Make sure that your mysql is able to perform well, it is especially important that the innodb_buffer_size is not using the rather restrictive default value
-- Potentially disalbe query caching as this is one of the situations where it can be quite detrimental due to the alternating high frequency reads/writes to the same table (you can do this by issuing the `SET GLOBAL query_cache_size = 0;` command via your MySQL CLI client)
+- Potentially disable query caching as this is one of the situations where it can be quite detrimental due to the alternating high frequency reads/writes to the same table (you can do this by issuing the `SET GLOBAL query_cache_size = 0;` command via your MySQL CLI client)
 - Run multiple `default` background workers, since the correlation will keep one of the workers monitoring that queue busy for a prolonged period. (Add more via Administration->server settings->workers)
 
 # How is the new engine different than the old one?
@@ -68,7 +68,7 @@ Despite the re-correlation potentially taking a long time, your instance will st
 
 # Switching engines
 
-The following proedure is to be used to switch between the `Default correlation engine` and the `No ACL engine`:
+The following procedure is to be used to switch between the `Default correlation engine` and the `No ACL engine`:
 - Navigate to Administration -> server settings -> correlations
 - Click on `Activate` under the chosen engine's header
 - Once the desired engine becomes active, truncate the table of the previously used engine to regain the disk space
@@ -96,7 +96,7 @@ In addition to the values being blocked based on the threshold the state of this
 
 ![](https://raw.githubusercontent.com/MISP/MISP/2.4/docs/img/2.4.160/over_correlations2.png)
 
-You will be able to see attrbutes as having too many correlations when viewing events, clicking on the magnifying glass will bring up the attribute search for the attribute value.
+You will be able to see attributes as having too many correlations when viewing events, clicking on the magnifying glass will bring up the attribute search for the attribute value.
 
 ### The Correlation exclusions
 

docs/generic/MISP_CAKE_init.md

@@ -1,7 +1,7 @@
 #### Initialize MISP configuration and set some defaults
 ```bash
 # <snippet-begin 2_core-cake.sh>
-# Core cake commands to tweak MISP and aleviate some of the configuration pains
+# Core cake commands to tweak MISP and alleviate some of the configuration pains
 # The ${RUN_PHP} is ONLY set on RHEL installs and can thus be ignored
 # This file is NOT an excuse to NOT read the settings and familiarize ourselves with them ;)
 
@@ -270,7 +270,7 @@ coreCAKE () {
 
 # This updates Galaxies, ObjectTemplates, Warninglists, Noticelists, Templates
 updateGOWNT () {
-  # AUTH_KEY Place holder in case we need to **curl** somehing in the future
+  # AUTH_KEY Place holder in case we need to **curl** something in the future
   # 
   ${SUDO_WWW} ${RUN_MYSQL} -- mysql -h ${DBHOST} -u ${DBUSER_MISP} -p${DBPASSWORD_MISP} misp -e "SELECT authkey FROM users;" | tail -1 > /tmp/auth.key
   AUTH_KEY=$(cat /tmp/auth.key)

docs/generic/hardening.md

@@ -7,7 +7,7 @@ MISP is a web-based **information sharing platform**, by design it is kept rathe
 Bare in mind that neither the MISP documentation efforts or the core MISP project can give you the ultimate guide on how to harden your system.
 This is not the purpose of the MISP Project but the purpose and care of those individuals and organizations deploying MISP Instances.
 
-Nevertheless here is a very rough **food for thoughts** bulletpoint list for you to consider, and a list of some hardening ressources below.
+Nevertheless here is a very rough **food for thoughts** bulletpoint list for you to consider, and a list of some hardening resources below.
 
 - Are we using SSL by default? (Especially when syncing over the internet and exposing the API)
 - How to we access the machine remotely? Via ssh? What is the path to get there? Does a [bastion host](https://en.wikipedia.org/wiki/Bastion_host) make sense?

docs/generic/supportFunctions.md

@@ -438,7 +438,7 @@ preInstall () {
 # Check apache config (Maybe try to talk to the server via api, this would confirm quite a lot)
 # Check if workers are running/installed, maybe kick them if they are not
 # /var/www/MISP/app/Config/[bootstrap,databases,core,config].php exists
-# /var/www/MISP perms are correct (for $SUDO_WWW useage)
+# /var/www/MISP perms are correct (for $SUDO_WWW usage)
 #
 
   # Check if $PATH_TO_MISP exists and is writable by $WWW_USER