ByteInternet · poespas · Jan 23, 2026 · Jan 23, 2026 · Jan 23, 2026 · Jan 23, 2026
diff --git a/docs/best-practices/performance/how-to-improve-your-magento-search.md b/docs/best-practices/performance/how-to-improve-your-magento-search.md
@@ -2,8 +2,7 @@
 myst:
   html_meta:
     description: Improve Magento search speed and relevancy with ElasticSearch or
-      Sphinx Search. Out-of-box integration on Hypernode Pelican, Falcon and Eagle
-      plans.
+      Sphinx Search. Out-of-box integration on Hypernode Falcon and Eagle plans.
     title: How to improve your Magento search? | Hypernode
 redirect_from:
   - /en/best-practices/performance/how-to-improve-your-magento-search/
@@ -14,24 +13,24 @@ redirect_from:
 
 # How to Improve Your Magento Search
 
-The built-in Magento search option is known for it’s non-existent speed and providing irrelevant search results. Both these aspects have a negative effect on your conversion, because if visitors can’t find what they’re looking for, how do you expect them to purchase from your shop? As a developer there are two things you can do;
+The built-in Magento search option is known for it's non-existent speed and providing irrelevant search results. Both these aspects have a negative effect on your conversion, because if visitors can't find what they're looking for, how do you expect them to purchase from your shop? As a developer there are two things you can do;
 
 1. Tweak the built-in Magento search option
 1. Use an external search engine.
 
-We recommend the latter, and specifically: ElasticSearch. If you have a Magento 2 shop, ElasticSearch has one major advantage: you can use this search engine out-of-the-box, without having to install any extension. On all Hypernode Pelican, Falcon and Eagle plans, ElasticSearch is built-in to your Hypernode. If you are on a formerly known plan like Start or Grow, you’ll need to either upgrade, or make use of an external search provider. We have arranged special Hypernode discounts with our partner Bonsai, a specialised managed ElasticSearch provider. Ask our support team for the discount code!
+We recommend the latter, and specifically: ElasticSearch. If you have a Magento 2 shop, ElasticSearch has one major advantage: you can use this search engine out-of-the-box, without having to install any extension. On all Hypernode Falcon and Eagle plans, ElasticSearch is built-in to your Hypernode. If your plan does not include ElasticSearch, you'll need to either upgrade, or make use of an external search provider. We have arranged special Hypernode discounts with our partner Bonsai, a specialised managed ElasticSearch provider. Ask our support team for the discount code!
 
-Another alternative is Sphinx Search. Sphinx is an open source search engine that improves the search function in your Magento. Sphinx is fast and provides you with relevant search results. There are many external search engines, but Sphinx came out as the best option due to it’s usability, documentation and speed. Sphinx is supported on your Hypernode (Pelican, Falcon and Eagle plans). You will, however, need extra (paid) plugins for your Magento to make use of Sphinx.
+Another alternative is Sphinx Search. Sphinx is an open source search engine that improves the search function in your Magento. Sphinx is fast and provides you with relevant search results. There are many external search engines, but Sphinx came out as the best option due to it's usability, documentation and speed. Sphinx is supported on your Hypernode (Falcon and Eagle plans). You will, however, need extra (paid) plugins for your Magento to make use of Sphinx.
 
 ## ElasticSearch
 
-While previously it was already possible to use ElasticSearch with your Hypernode by connecting to an external search provider, we have now made it possible to use ElasticSearch for search in your shop out of the box on Hypernode without requiring any external service or configuration. In [this article](../../hypernode-platform/tools/how-to-use-elasticsearch-on-hypernode.md) we’ll explain a bit more about ElasticSearch and how to enable and configure it.
+While previously it was already possible to use ElasticSearch with your Hypernode by connecting to an external search provider, we have now made it possible to use ElasticSearch for search in your shop out of the box on Hypernode without requiring any external service or configuration. In [this article](../../hypernode-platform/tools/how-to-use-elasticsearch-on-hypernode.md) we'll explain a bit more about ElasticSearch and how to enable and configure it.
 
-Please note that due to the relatively heavy resource requirements for ElasticSearch this feature can only be enabled on every plan except the formerly known Grow plan. If you are on a smaller plan and previously already depended on an external paid ElasticSearch provider now might be a good time to consider simplifying your setup.
+Please note that due to the relatively heavy resource requirements for ElasticSearch this feature can only be enabled on Falcon and Eagle plans. If you are on a smaller plan and previously already depended on an external paid ElasticSearch provider now might be a good time to consider simplifying your setup.
 
 ### ElasticSearch providers
 
-If you are on a lower plan, you’ll need to either upgrade, or make use of an external search provider. There a several companies you can choose for a monthly subscription:
+If you are on a lower plan, you'll need to either upgrade, or make use of an external search provider. There a several companies you can choose for a monthly subscription:
 
 - [Bonsai.io](https://bonsai.io/)
 - [Elastic.co](https://www.elastic.co/cloud/as-a-service)
@@ -42,9 +41,9 @@ If you are on a lower plan, you’ll need to either upgrade, or make use of an e
 
 Sphinx indexes up to 10-15 MB of text per second per single CPU core 60+ MB/sec per server. Technically, Sphinx is a standalone software package that provides fast and relevant full-text search functionality to client applications. It was specially designed to integrate well with SQL databases storing the data, and to be easily accessed by scripting languages. However, Sphinx does not depend on – or requires – any specific database to function.
 
-We added support for the Sphinx search indexer on Hypernode Pelican, Falcon and Excellent nodes. Using Sphinx requires the `Mirasvit Sphinx Search Ultimate extension`. This paid extension can be purchased through the [Mirasvit website](https://mirasvit.com/magento-extensions/sphinx-search-ultimate.html). If you have a Magento 2 shop, make sure to use the [specific Magento 2 extension](https://mirasvit.com/magento-2-extensions/sphinx-search-ultimate.html).
+We added support for the Sphinx search indexer on Hypernode Falcon and Eagle nodes. Using Sphinx requires the `Mirasvit Sphinx Search Ultimate extension`. This paid extension can be purchased through the [Mirasvit website](https://mirasvit.com/magento-extensions/sphinx-search-ultimate.html). If you have a Magento 2 shop, make sure to use the [specific Magento 2 extension](https://mirasvit.com/magento-2-extensions/sphinx-search-ultimate.html).
 
-More information about using Sphinx can be found in [their documentation](http://sphinxsearch.com/docs/). Can’t find an answer to your question? Please contact Mirasvit through their [Support Portal](https://mirasvit.com/contact/).
+More information about using Sphinx can be found in [their documentation](http://sphinxsearch.com/docs/). Can't find an answer to your question? Please contact Mirasvit through their [Support Portal](https://mirasvit.com/contact/).
 
 ### Configuring Sphinx on Hypernode
 
@@ -68,7 +67,7 @@ When adjusting the Sphinx settings, you should make use the following informatio
 
 - When using the Mirasvit extension, Magento periodically restarts the Sphinx engine. If this happens too fast, the reload of Sphinx can be ratelimited causing the daemon to stop or to hang. To resolve this issue, whitelist the `Zend_Http_Client` as explained in [the instructions how to prevent a user agent from being rate limited](../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md#rate-limiting-for-bots-and-crawlers).
 - If your shop is using too much memory, the `searchd` daemon can crash due to OOM. To resolve this upgrade to a bigger Hypernode, or improve the memory print of your webshop.
-- The `searchd`daemon is started from the Magento backend, but in case of a server reboot, memory issues or an otherwise very busy server the process kan be killed, causing an interruption in your search functionality. To circumvent these issues, add a cron that checks if the daemon is running and starts it if it’s not:
+- The `searchd`daemon is started from the Magento backend, but in case of a server reboot, memory issues or an otherwise very busy server the process kan be killed, causing an interruption in your search functionality. To circumvent these issues, add a cron that checks if the daemon is running and starts it if it's not:
   - For Magento 1:
   ```text
   @reboot chronic flock -E 0 -n ~/.sphinx.lock /usr/bin/searchd --config /data/web/public/var/sphinx/sphinx.conf --nodetach 2>&1 >> /tmp/search.log
@@ -89,4 +88,4 @@ location = /shell/filename.php {
 
 ## SOLR
 
-A third option is SOLR. We don’t offer SOLR anymore due to low demand. If you want to use SOLR, we recommend using [WebSOLR](https://www.websolr.com/) as a hosted third party service.
+A third option is SOLR. We don't offer SOLR anymore due to low demand. If you want to use SOLR, we recommend using [WebSOLR](https://www.websolr.com/) as a hosted third party service.
diff --git a/...t-practices/performance/how-to-optimize-the-performance-of-your-magento-shop.md b/...t-practices/performance/how-to-optimize-the-performance-of-your-magento-shop.md
@@ -190,7 +190,7 @@ This happens faster when the Magento shop is not well optimized and it takes a l
 
 To make sure a small set of IP addresses can’t take your shop down we use rate limiting based on IP address. A single IP might use up to 80% of the total PHP-FPM worker capacity available.
 
-On smaller nodes (mostly on Hypernode Start and Grow plans) this can cause errors when working in the Magento admin. To resolve these errors, you can whitelist IP’s to make sure they will not be rate limited when working in the Magento admin backend. If you use nightly product imports through the Magento SOAP API, sometimes you need to whitelist the remote ip of the import tool as well.
+On smaller nodes this can cause errors when working in the Magento admin. To resolve these errors, you can whitelist IP’s to make sure they will not be rate limited when working in the Magento admin backend. If you use nightly product imports through the Magento SOAP API, sometimes you need to whitelist the remote ip of the import tool as well.
 
 [To whitelist these IP’s have a look at our article about rate limiting](../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md).
 

diff --git a/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md b/docs/best-practices/testing/how-to-go-live-with-your-hypernode.md
@@ -133,7 +133,7 @@ Note that the time on Hypernode is configured to UTC, so the times used in the c
 
 ## Step 11: Configure Backups on Hypernode (Optional)
 
-For Hypernode Pelican, Falcon S (or up) and Eagle hosting plans free backups are available. If you need a backup, contact us via support@hypernode.com. Hypernode Pelican S and Falcon XS (used to be Grow) plans do not have free backups included, but we can make one available for 25 euros excl VAT per backup.
+For Hypernode Falcon S (or up) and Eagle hosting plans free backups are available. If you need a backup, contact us via support@hypernode.com.
 
 ## Downgrade or Cancel Your Previous Plan
 

diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-3-on-hypernode.md
@@ -12,7 +12,7 @@ redirect_from:
 
 # How to Install Akeneo 3 on Hypernode
 
-Akeneo 3 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 5.7, PHP 7.2 and Elasticsearch 6.x**, so it won’t affect your shop negatively. Installing Akeneo version 3.x may take up to 15 minutes.
+Akeneo 3 preferably requires a Hypernode Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 5.7, PHP 7.2 and Elasticsearch 6.x**, so it won’t affect your shop negatively. Installing Akeneo version 3.x may take up to 15 minutes.
 
 ## Managed Vhosts
 

diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-4-on-hypernode.md
@@ -13,7 +13,7 @@ redirect_from:
 
 # How to Install Akeneo 4 on Hypernode
 
-Akeneo 4 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.3 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 4.x may take up to 15 minutes.
+Akeneo 4 preferably requires a Hypernode Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.3 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 4.x may take up to 15 minutes.
 
 ## Managed Vhosts
 

diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-5-on-hypernode.md
@@ -12,7 +12,7 @@ redirect_from:
 
 # How to install Akeneo 5 on Hypernode
 
-Akeneo 5 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.4 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 5.x may take up to 15 minutes.
+Akeneo 5 preferably requires a Hypernode Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 7.4 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 5.x may take up to 15 minutes.
 
 ## Managed Vhosts
 

diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-6-on-hypernode.md
@@ -12,7 +12,7 @@ redirect_from:
 
 # How to Install Akeneo 6 on Hypernode
 
-Akeneo 6 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.0 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 6.x may take up to 15 minutes.
+Akeneo 6 preferably requires a Hypernode Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.0 and Elasticsearch 7.x**, so it won’t affect your shop negatively. Installing Akeneo version 6.x may take up to 15 minutes.
 
 ## Managed Vhosts
 

diff --git a/docs/ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md b/docs/ecommerce-applications/akeneo/how-to-install-akeneo-7-on-hypernode.md
@@ -12,7 +12,7 @@ redirect_from:
 
 # How to Install Akeneo 7 on Hypernode
 
-Akeneo 7 preferably requires a Hypernode Pelican L, Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.1 and OpenSearch 2.x**, so it won’t affect your shop negatively. Installing Akeneo version 7.x may take up to 15 minutes.\
+Akeneo 7 preferably requires a Hypernode Falcon M, Eagle M hosting plan or larger. You can either choose to install it on a seperate Hypernode instance or on the same Hypernode as your Magento or Shopware installation. If you choose the latter you have to make sure that you have enough resources (disk space, memory and CPU) left. Furthermore you need to make sure that you are already using **MySQL 8.0, PHP 8.1 and OpenSearch 2.x**, so it won’t affect your shop negatively. Installing Akeneo version 7.x may take up to 15 minutes.\
 **Important note: Akeneo 7.x requires MySQL 8.0.30, which is only available on Debian Bookworm.**
 
 ## Managed Vhosts

diff --git a/docs/ecommerce-applications/magento-1/how-to-configure-redis-for-magento-1.md b/docs/ecommerce-applications/magento-1/how-to-configure-redis-for-magento-1.md
@@ -125,7 +125,7 @@ In order to use the compression library Snappy for your Redis cache you need to
 
 You can use Redis for storing sessions too!
 
-Hypernode plans bigger than Magento Grow, often have enough memory to store the session data in Redis.
+Larger Hypernode plans often have enough memory to store the session data in Redis.
 This way sessions are stored in-memory, making the shop faster and use less IO than when using MySQL or files as session store.
 
 ### Install `Cm_RedisSession`

diff --git a/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md b/docs/ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md
@@ -14,7 +14,7 @@ redirect_from:
 
 # How to Configure Varnish for Magento 1.x
 
-Customers with Hypernode Pelican, Falcon (formerly known as Professional) and Eagle (formerly known as Excellence) plans can use Varnish to boost their Magento shop. To manage and configure Varnish for Magento 1.x you’ll need Turpentine. This article explains how you can configure Varnish for your Hypernode. Do you have a Magento 2.x shop, please check [this article](../../ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md)
+Customers with Hypernode Falcon and Eagle plans can use Varnish to boost their Magento shop. To manage and configure Varnish for Magento 1.x you’ll need Turpentine. This article explains how you can configure Varnish for your Hypernode. Do you have a Magento 2.x shop, please check [this article](../../ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md)
 
 Although Varnish is extremely awesome when it get's to speeding up websites, Varnish is a complex technique that needs some experience to set it up. Don't implement Varnish on production nodes while still under development but use [development node](../../hypernode-platform/tools/how-to-use-hypernode-development-plans.md) or a local staging environment like the [Hypernode Docker](../../best-practices/testing/hypernode-docker.md) instead.
 

diff --git a/...ce-applications/magento-1/how-to-create-a-robots-txt-for-your-magento-1-shop.md b/...ce-applications/magento-1/how-to-create-a-robots-txt-for-your-magento-1-shop.md
@@ -147,4 +147,4 @@ This will create a location `/robots.txt` which returns the same data on all sto
 
 ### Create a single robots.txt
 
-If you want to serve just one single storefront (for example on a Hypernode Start plan), all you have to do is place a `robots.txt` file in `/data/web/public` and you're done. :-)
+If you want to serve just one single storefront, all you have to do is place a `robots.txt` file in `/data/web/public` and you're done. :-)
diff --git a/docs/ecommerce-applications/magento-2/how-to-configure-redis-for-magento-2.md b/docs/ecommerce-applications/magento-2/how-to-configure-redis-for-magento-2.md
@@ -100,7 +100,7 @@ $ bin/magento setup:config:set --page-cache-redis-compression-lib=snappy
 
 You can use Redis for storing sessions too!
 
-Hypernodes bigger than a Grow plan, often have enough memory to store the session data in Redis. This way sessions are stored in-memory, making the shop faster and use less IO than when using MySQL or files as session store.
+Larger Hypernode plans often have enough memory to store the session data in Redis. This way sessions are stored in-memory, making the shop faster and use less IO than when using MySQL or files as session store.
 
 ### Configure Magento 2 to Store Sessions in Redis
Original file line number	Diff line number	Diff line change
Expand Up		@@ -147,4 +147,4 @@ This will create a location `/robots.txt` which returns the same data on all sto

		### Create a single robots.txt

		If you want to serve just one single storefront (for example on a Hypernode Start plan), all you have to do is place a `robots.txt` file in `/data/web/public` and you're done. :-)
		If you want to serve just one single storefront, all you have to do is place a `robots.txt` file in `/data/web/public` and you're done. :-)