Add space after links to fix syntax

Author: poespas

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
 

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.

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
 

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.
 

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.

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.

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).