chore/fix-more-links

Author: Isengo1989

concepts/commerce/catalog/products.md

@@ -9,7 +9,7 @@ nav:
 
 Products are sellable entities (physical and digital products) within your shop.
 
-Depending on your setup, Shopware can easily handle thousands of products. However, an upsurge in the product quantity (in millions) needs some tweaks for robust running of the environment as it depends on factors like the number of [categories](../../../concepts/commerce/catalog/categories), [sales channels](../../../concepts/commerce/catalog/sales-channels), [product properties](../../../concepts/commerce/catalog/products#property-groups--options), etc. Every product added to your shop can be made available on one or more [sales channels](../../../concepts/commerce/catalog/sales-channels).
+Depending on your setup, Shopware can easily handle thousands of products. However, an upsurge in the product quantity (in millions) needs some tweaks for robust running of the environment as it depends on factors like the number of [categories](../../../concepts/commerce/catalog/categories), [sales channels](../../../concepts/commerce/catalog/sales-channels), [product properties](../../../concepts/commerce/catalog/products), etc. Every product added to your shop can be made available on one or more [sales channels](../../../concepts/commerce/catalog/sales-channels).
 
 Let's delve into a more detailed understanding of products using the example of garments:
 
@@ -52,8 +52,8 @@ erDiagram
         uuid product_id
     }
     ProductCategory {
-        uuid product_id 
-        uuid category_id 
+        uuid product_id
+        uuid category_id
     }
     Category {
         uuid category_id

guides/hosting/infrastructure/elasticsearch/elasticsearch-debugging.md

@@ -44,7 +44,7 @@ bin/console es:index // Creates only the index for ES
 `es:create:alias`  will create an alias linking to the index after `es:index` is done. Normally this is done automatically. In the older version, this has to be done.
 
 ```bash
-bin/console es:create:alias 
+bin/console es:create:alias
 ```
 
 **> No Output**
@@ -205,9 +205,9 @@ curl -X DELETE 'elasticsearch:9200/_all'
 Returns the status of your indexing:
 
 ```sql
-select * from message_queue_stats mqs ; 
-select count(*) from enqueue e ; 
-select count(*) from dead_message dm ; 
+select * from message_queue_stats mqs ;
+select count(*) from enqueue e ;
+select count(*) from dead_message dm ;
 ```
 
 The number of entries in the enqueue should match the sum of the size values in the `message_queue_stats`. As long as there are entries in your `enqueue`, the indexing is in process and your message consumer has to work those messages.
@@ -218,7 +218,7 @@ Sometimes you want to reset the indexing in your database because your indexing
 If the database queue is used, third-party services will differ. You can do so with the following queries.
 
 ```sql
-truncate enqueue ; 
+truncate enqueue ;
 truncate dead_message ;
 truncate message_queue_stats ;
 update scheduled_task set status = 'scheduled' where status = 'queued';
@@ -230,7 +230,7 @@ This is mainly for debugging purposes and is only meant for testing and staging
 First, execute the database reset (only working for the database queue):
 
 ```sql
-truncate enqueue ; 
+truncate enqueue ;
 truncate dead_message ;
 truncate message_queue_stats ;
 update scheduled_task set status = 'scheduled' where status = 'queued';

guides/hosting/infrastructure/elasticsearch/elasticsearch-setup.md

@@ -170,7 +170,7 @@ For additional support with common Elasticsearch errors and more tips please ref
 ### Indexing the whole shop
 
 Sometimes you want to reindex your whole shop, including Elasticsearch, SEO-URLs, product index, and more.
-For a reindex of the whole shop, you can use the command `bin/console dal:refresh:index --use-queue`. Use the `--use-queue` option because you will have too many products to index without the [message queue](/docs/guides/hosting/infrastructure/message-queue) involved.
+For a reindex of the whole shop, you can use the command `bin/console dal:refresh:index --use-queue`. Use the `--use-queue` option because you will have too many products to index without the [message queue](../message-queue) involved.
 
 ### Alias creation
 
@@ -184,10 +184,10 @@ If a messenger process is active, the entries of that table are processed one by
 In case a message runs into an error, it is written into the `dead_messages` table and will be processed again after a specific time frame.
 
 You can start multiple messenger consumer processes by using the command `bin/console messenger:consume` and also add output to the processed messages by adding the parameter `bin/console messenger:consume -vv`.
-In a production environment, you want to deactivate the admin messenger which is started automatically when opening a session in your Administration view by following this [documentation](/docs/guides/plugins/plugins/framework/message-queue/add-message-handler#the-admin-worker).
+In a production environment, you want to deactivate the admin messenger which is started automatically when opening a session in your Administration view by following this [documentation](../../../../guides/hosting/infrastructure/message-queue#admin-worker).
 
 Our experience has shown that up to three worker processes are normal and useful for a production environment.
-If you want more than that, a tool like [RabbitMQ](/docs/guides/hosting/infrastructure/message-queue#transport-rabbitmq-example) to handle the queue is needed so your database will not become a bottleneck.
+If you want more than that, a tool like [RabbitMQ](../message-queue#message-queue-on-production-systems) to handle the queue is needed so your database will not become a bottleneck.
 
 ## Configuration
 

guides/plugins/apps/starter/starter-admin-extension.md

@@ -161,4 +161,4 @@ This example showed end-to-end how to create a local dev environment and connect
 
 * Did you know, you can add [new sections](/resources/admin-extension-sdk/api-reference/ui/component-section) to the UI or even [entire modules](/resources/admin-extension-sdk/api-reference/ui/mainModule)?
 * The Meteor Admin SDK also offers [TypeScript support](/resources/admin-extension-sdk/getting-started/installation#using-npm-require-bundling) (including autocompletion)
-* Don't want to extend the admin panel? Have a look at [App Scripts](/docs/guides/plugins/apps/app-scripts/index.md)
+* Don't want to extend the admin panel? Have a look at [App Scripts](../../../../guides/plugins/apps/app-scripts/index.md)