diff --git a/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md b/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md
index c8f35890..508b65d6 100644
--- a/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md
+++ b/docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md
@@ -23,7 +23,7 @@ On the first working day after the detection, our customer will receive a e-mail
 
 The output of the daily scan we perform, is written to `/var/log/mwscan.log`. If the scanner hits on a file, please review the file. In most of the cases, the malware has been uploaded by a unsecure downloader folder or Magmi plugin. Try to find how the file has been uploaded. Replace the file with the originating file distributed by the developer or when it is not used, remove the file.
 
-If you find web shells, malicious files, and/or injected PHP code that are not yet recognised by `mwscan`, please report them by filing an issues on [the Github repository](https://github.com/gwillem/magento-malware-scanner)of this containing the files as described in the [contribution documentation](https://github.com/gwillem/magento-malware-scanner/blob/master/CONTRIBUTING.md)
+If you find web shells, malicious files, and/or injected PHP code that are not yet recognised by `mwscan`, please report them by filing an issues on [the Github repository](https://github.com/gwillem/magento-malware-scanner) of this containing the files as described in the [contribution documentation](https://github.com/gwillem/magento-malware-scanner/blob/master/CONTRIBUTING.md)
 
 ## Scan Your Files for Known Web Shells and Malware Manually
 
diff --git a/docs/best-practices/testing/how-to-check-if-everything-works.md b/docs/best-practices/testing/how-to-check-if-everything-works.md
index be8f351b..d25ebecb 100644
--- a/docs/best-practices/testing/how-to-check-if-everything-works.md
+++ b/docs/best-practices/testing/how-to-check-if-everything-works.md
@@ -18,7 +18,7 @@ Use the steps below to test everything in your shop.
 
 **NB:** When browsing your preview shop, double check that you don’t end up on your production shop by following a hardcoded link.
 
-A bigger checklist is available [on the Github account](https://gist.github.com/peterjaap/10016278)of one of our well appreciated technical partners Peter Jaap (Elgentos).
+A bigger checklist is available [on the Github account](https://gist.github.com/peterjaap/10016278) of one of our well appreciated technical partners Peter Jaap (Elgentos).
 
 - Test all storefronts *(use the storefront view in MageReport Premium (only for Magento 1.x versions)).*
 - Test front pages, categories and product pages.
@@ -51,7 +51,7 @@ grep -Ri memcache /data/web/public/app/etc
 - Test for images, css, js and mixed content warnings.
 - Test if all static content is loaded: View the console in your browser to check if there are javascript errors or 404 errors on stylesheets and js files.
 - Test if [the Magento API is accessible when used](../../ecommerce-applications/magento-2/how-to-enable-the-magento-2-api.md).
-- Test if the sitemap is accessible for [Magento 1](../../ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md)or [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-sitemap-xml-for-magento-2-x.md).
+- Test if the sitemap is accessible for [Magento 1](../../ecommerce-applications/magento-1/how-to-create-a-sitemap-xml-for-magento-1-x.md) or [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-sitemap-xml-for-magento-2-x.md).
 - Test if [you can easily download the robots.txt file](../../ecommerce-applications/magento-1/how-to-create-a-robots-txt-for-your-magento-1-shop.md) (Or for [Magento 2](../../ecommerce-applications/magento-2/how-to-create-a-robots-txt-for-magento-2-x.md)).
 - Test product and price import and export routines.
 - Test product push mechanisms for search engines.
diff --git a/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md b/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md
index 4a044ac9..b678b702 100644
--- a/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md
+++ b/docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md
@@ -103,6 +103,6 @@ After installing and configuring Nginx, you can visit your WordPress at `/blog/`
 
 ## Multisite
 
-It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://codex.wordpress.org/Create_A_Network)and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/).
+It is possible to set up a multisite environment in WordPress. To do this, refer to the [original WordPress documentation about creating multisites](https://codex.wordpress.org/Create_A_Network) and the article [about configuring WordPress on Nginx](https://wordpress.org/support/article/nginx/).
 
 *Please note that it won’t work in all cases due to the fact that certain Nginx configurations cannot be changed. At the moment we are still looking into a solution that will work for everyone.*
diff --git a/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md b/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md
index 3965b836..cafd1375 100644
--- a/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md
+++ b/docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md
@@ -91,7 +91,7 @@ magerun --root-dir=/data/web/staging config:set web/secure/base_url https://$SHO
 magerun --root-dir=/data/web/staging cache:flush
 ```
 
-If you have many storefronts, that all should be changed it's easier to use [our script](https://gist.github.com/hn-support/faf03c5898f5553b7fd9f4059709aef4)to change the base URL's of your staging environment.
+If you have many storefronts, that all should be changed it's easier to use [our script](https://gist.github.com/hn-support/faf03c5898f5553b7fd9f4059709aef4) to change the base URL's of your staging environment.
 
 To use this script:
 
diff --git a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md
index 902698c5..45a57811 100644
--- a/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md
+++ b/docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md
@@ -57,7 +57,7 @@ Syncing a domain to your Hypernode will immediately change the domain's DNS reco
 
 #### The steps:
 
-1. [Log in to your Control Panel](https://my.hypernode.com/)with your customer email and password and select "domains."
+1. [Log in to your Control Panel](https://my.hypernode.com/) with your customer email and password and select "domains."
 1. Here you will find a list of your domain names.
 1. Click on your domain name.
 1. In your next view, you can **link**\* the domain to your Hypernode.
diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md
index e045bb4b..86d3ca52 100644
--- a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md
+++ b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-outgoing-email.md
@@ -36,7 +36,7 @@ To check if your DNS records have been configured correctly, please check our on
 - The second and third records are needed for automatic DKIM signing and DMARC
 - The fourth record is the SPF record. Please make sure you include spf.***example***.hypernode.io in your DNS's SPF record.
 
-Please check our [DNS validato](https://my.hypernode.com/dns/check/)r to confirm email can be sent successfully.
+Please check our [DNS validator](https://my.hypernode.com/dns/check/) to confirm email can be sent successfully.
 
 ## Additional audit options
 
diff --git a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md
index 0a5c503d..e165804e 100644
--- a/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md
+++ b/docs/hypernode-platform/email/how-to-set-up-your-dns-for-using-office365.md
@@ -17,7 +17,7 @@ When you want to use Office365 and your domain is registered with Hypernode or h
 
 ## Validation Record
 
-When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/)and follow the next steps:
+When you add your domain to Office365 they wil provide you with a verification string that you need to add to the DNS for your domain, the string will look something like this \*MS=ms#########.\*You need to add this at a TXT record. To do so login to your [Service Panel](https://my.hypernode.com/) and follow the next steps:
 
 1. Log in to the Service Panel (my.hypernode.com).
 1. Select the domain from the domain overview.
diff --git a/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md b/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md
index 734bf339..c3ef0430 100644
--- a/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md
+++ b/docs/hypernode-platform/tools/how-to-configure-automatic-logfile-rotation.md
@@ -75,7 +75,7 @@ The `hypernode-auto-logrotate` command comes with a sensible out-of-the-box conf
 }
 ```
 
-The [logrotate main page](https://linux.die.net/man/8/logrotate)contains instructions on how to customize this.
+The [logrotate main page](https://linux.die.net/man/8/logrotate) contains instructions on how to customize this.
 
 ## Keeping the configuration up to date
 
diff --git a/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md b/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md
index 4ebc43be..f97061b4 100644
--- a/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md
+++ b/docs/hypernode-platform/tools/how-to-migrate-your-shop-to-hypernode.md
@@ -55,7 +55,7 @@ When you select the maintenance box in the importer tool in the Service Panel, t
 
 \*If your domain is hosted at Hypernode, there is a quick and easy way to switch your DNS to the Hypernode. Login into the [Service Panel](https://service.byte.nl). Make sure your Hypernode is selected in the dropdown menu -> Instellingen -> SSL & DNS instellingen -> Find your domain in the list -> change the 'Beschikbaar' value into 'Koppel domeinnaam aan deze Hypernode'. Repeat these steps for all the domains that should be linked to your Hypernode.
 
-\*If your domain is being hosted externally, you need to change the DNS settings manually. Read [this article](../dns/how-to-manage-your-dns-settings-for-hypernode.md)to see which records you need to modify.
+\*If your domain is being hosted externally, you need to change the DNS settings manually. Read [this article](../dns/how-to-manage-your-dns-settings-for-hypernode.md) to see which records you need to modify.
 
 \*Although the Shop importer is a very easy way to import a shop, please keep in mind that is using the command line is a requirement. So if needed, find yourself an [experienced developer](https://www.byte.nl/partners#specialisms=Hypernode&cms=Magento) that can assist you with these tasks.
 
diff --git a/docs/services/control-panel/how-to-use-the-dns-check.md b/docs/services/control-panel/how-to-use-the-dns-check.md
index 9c0b2298..eb7498b8 100644
--- a/docs/services/control-panel/how-to-use-the-dns-check.md
+++ b/docs/services/control-panel/how-to-use-the-dns-check.md
@@ -104,4 +104,4 @@ The DNS Check verifies whether the Hypernode is reachable via the URL you entere
 
 ## Using Cloudflare or Other CDN
 
-If you are using Cloudflare or another CDN type product, we cannot check your records with our DNS Check. Use our [Support Documentation](../../hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md#option-2-manage-an-external-dns-by-pointing-your-domain-to-hypernode-by-using-cname-and-not-an-a-record)for managing your DNS settings for your Hypernode to make sure you have your DNS settings set up correctly.
+If you are using Cloudflare or another CDN type product, we cannot check your records with our DNS Check. Use our [Support Documentation](../../hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md#option-2-manage-an-external-dns-by-pointing-your-domain-to-hypernode-by-using-cname-and-not-an-a-record) for managing your DNS settings for your Hypernode to make sure you have your DNS settings set up correctly.
diff --git a/docs/services/magereport/magereport-premium.md b/docs/services/magereport/magereport-premium.md
index d2636ecd..f63aa22f 100644
--- a/docs/services/magereport/magereport-premium.md
+++ b/docs/services/magereport/magereport-premium.md
@@ -81,7 +81,7 @@ n98-magerun sys:store:config:base-url:list
 magerun2 sys:store:config:base-url:list
 ```
 
-This tool shows the storefronts configured in your shop and the storecode. In MageReport Premium you can check whether your DNS is configured correctly. See our manual on [configuring DNS](../../hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md)for more information.
+This tool shows the storefronts configured in your shop and the storecode. In MageReport Premium you can check whether your DNS is configured correctly. See our manual on [configuring DNS](../../hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md) for more information.
 
 *If you’re using Cloudflare the check will say your storefronts aren’t configured correctly and your shop is not live. Right now MageReport can’t detect if a shop is using Cloudflare, so you can ignore this.*
 
@@ -111,4 +111,4 @@ A line of 50% or higher in this chart indicates your Hypernode is very busy. If
 
 This chart shows you the percentage of memory in use by Redis and the hitratio (percentage of requests served out of Redis cache). The more data is cached, the more the memory usage increases. The memory usage decreases when expired cache items are removed. Red vertical lines (not always showing), mean your cache was full and Redis deleted the least requested ([LRU](https://en.wikipedia.org/wiki/Cache_algorithms#LRU)) items. You’ll notice this can happen when less than 100% is used according to the graph. This is because the graph shows you the average usage (in %) per week.
 
-We recommend you to upgrade to a bigger node if you're using more memory than your Hypernode offers. If all available memory is in use, Redis will delete cache items to free up memory, which could lead to a reduced hit ratio depending on your configuration. Every Hypernode has access to Redis, starting from 768 MB, depending on the plan. Please [check our website](https://www.hypernode.com/magento-cloud-hosting/#plans)for an overview of the Hypernode plans and their specs.
+We recommend you to upgrade to a bigger node if you're using more memory than your Hypernode offers. If all available memory is in use, Redis will delete cache items to free up memory, which could lead to a reduced hit ratio depending on your configuration. Every Hypernode has access to Redis, starting from 768 MB, depending on the plan. Please [check our website](https://www.hypernode.com/magento-cloud-hosting/#plans) for an overview of the Hypernode plans and their specs.
diff --git a/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md b/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md
index 84296c23..1f291207 100644
--- a/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md
+++ b/docs/troubleshooting/performance/how-to-solve-the-front-controller-reached-100-router-match-iterations-error.md
@@ -19,10 +19,10 @@ We see this error mostly on shops that experience high traffic, causing a rare c
 
 The developers from Convenient and AmpersandHQ fully debugged this issue and came up with a patch that should solve this issue once and for all.
 
-You can find [detailed information](https://github.com/convenient/magento-ce-ee-config-corruption-bug#the-fix)about how to solve this issue on the GitHub page of Convenient.
+You can find [detailed information](https://github.com/convenient/magento-ce-ee-config-corruption-bug#the-fix) about how to solve this issue on the GitHub page of Convenient.
 
 This issue is as far as we know a Magento 1 only issue, although a very small group of developers working on Magento 2 have notified us of having the same issue appear in Magento 2.
 
-**Update:** So it seems it could help [changing the permissions on certain a PHP file](https://stackoverflow.com/questions/6262129/magento-front-controller-reached-100-router-match-iterations-error/33684913#33684913)if the convenient patch does not fix this issue.
+**Update:** So it seems it could help [changing the permissions on certain a PHP file](https://stackoverflow.com/questions/6262129/magento-front-controller-reached-100-router-match-iterations-error/33684913#33684913) if the convenient patch does not fix this issue.
 
 **Update 2:** Adding other suggestions to fix this issue from [Magento explorer](https://magentoexplorer.com/how-to-debug-and-fix-front-controller-reached-100-router-match-iterations-in-magento).