Skip to content

Commit 01b04a0

Browse files
author
Jonathan Visser
committed
Add more spaces after links
1 parent 841a2af commit 01b04a0

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

docs/best-practices/security/how-to-scan-your-hypernode-for-malware.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ On the first working day after the detection, our customer will receive a e-mail
2323

2424
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.
2525

26-
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)
26+
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)
2727

2828
## Scan Your Files for Known Web Shells and Malware Manually
2929

docs/best-practices/testing/how-to-check-if-everything-works.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Use the steps below to test everything in your shop.
1818

1919
**NB:** When browsing your preview shop, double check that you don’t end up on your production shop by following a hardcoded link.
2020

21-
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).
21+
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).
2222

2323
- Test all storefronts *(use the storefront view in MageReport Premium (only for Magento 1.x versions)).*
2424
- Test front pages, categories and product pages.
@@ -51,7 +51,7 @@ grep -Ri memcache /data/web/public/app/etc
5151
- Test for images, css, js and mixed content warnings.
5252
- 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.
5353
- Test if [the Magento API is accessible when used](../../ecommerce-applications/magento-2/how-to-enable-the-magento-2-api.md).
54-
- 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).
54+
- 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).
5555
- 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)).
5656
- Test product and price import and export routines.
5757
- Test product push mechanisms for search engines.

docs/best-practices/usage/how-to-install-wordpress-next-to-your-magento-installation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,6 @@ After installing and configuring Nginx, you can visit your WordPress at `/blog/`
103103

104104
## Multisite
105105

106-
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/).
106+
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/).
107107

108108
*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.*

docs/ecommerce-applications/magento-1/how-to-set-up-a-staging-environment-for-magento-1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ magerun --root-dir=/data/web/staging config:set web/secure/base_url https://$SHO
9191
magerun --root-dir=/data/web/staging cache:flush
9292
```
9393

94-
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.
94+
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.
9595

9696
To use this script:
9797

docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Syncing a domain to your Hypernode will immediately change the domain's DNS reco
5757

5858
#### The steps:
5959

60-
1. [Log in to your Control Panel](https://my.hypernode.com/)with your customer email and password and select "domains."
60+
1. [Log in to your Control Panel](https://my.hypernode.com/) with your customer email and password and select "domains."
6161
1. Here you will find a list of your domain names.
6262
1. Click on your domain name.
6363
1. In your next view, you can **link**\* the domain to your Hypernode.

0 commit comments

Comments
 (0)