Fix broken links (#2260)

Author: adriendupuis

docs/content_management/content_management_guide.md

@@ -32,7 +32,7 @@ Content management capabilities are available in all [[= product_name =]] editio
 You can set up content structure, define the templates to be filled with content, and assign different areas of the structure to your editors. 
 Next steps would be to create the actual content, and then classify content items, and organize them as necessary.
 
-You can then publish the content directly, by building a website or a web store, or by using external systems together with a [headless CMS](https://developers.ibexa.co/developer-portal/headless-cms) that relies on the [[= product_name =]] technology.
+You can then publish the content directly, by building a website or a web store, or by using external systems together with a [headless CMS](https://developers.ibexa.co/headless-cms) that relies on the [[= product_name =]] technology.
 
 ## Content structure
 
@@ -284,4 +284,4 @@ Extensive content management capabilities would prove themselves in a setting,
 where multiple buyers from different partner companies connect to an industry leader’s trading website, 
 and they expect to find well organized SKU catalogs that contain basic product information. 
 From there they would like to access detailed specifications, white papers and application notes. 
-The same products could come with different brands and at different price points, depending on the customer segment or origin.
+The same products could come with different brands and at different price points, depending on the customer segment or origin.

docs/getting_started/requirements.md

@@ -455,7 +455,7 @@ Recommendation for production setups is to use Varnish/Fastly, Redis/Memcached,
 
     ### Cloud hosting with eZ Platform Cloud and Platform.sh
 
-    In general, eZ Platform Cloud supports all features and services of [Platform.sh](https://platform.sh/hosting/php/ez) that are compatible and supported by the eZ Platform version you use.
+    In general, eZ Platform Cloud supports all features and services of [Platform.sh](https://platform.sh/marketplace/ibexa/) that are compatible and supported by the eZ Platform version you use.
 
     For example:
 

docs/infrastructure_and_maintenance/clustering/clustering_with_aws_s3.md

@@ -14,13 +14,13 @@ meaning AWS S3 will be used to store binary files.
 ## Set up AWS S3 account
 
 1.  Go to <https://aws.amazon.com/> and create an account.
-An [existing Amazon account can be used](http://docs.aws.amazon.com/AmazonS3/latest/gsg/SigningUpforS3.html).
-1.  [Choose a region](http://docs.aws.amazon.com/storagegateway/latest/userguide/available-regions-intro.html).
+An [existing Amazon account can be used](https://docs.aws.amazon.com/AmazonS3/latest/userguide/setting-up-s3.html#sign-up-for-aws).
+1.  [Choose a region](https://docs.aws.amazon.com/storagegateway/latest/vgw/available-regions-intro.html).
 The example below uses EU (Ireland): `eu-west-1`
 1.  Create a bucket in your chosen region and make note of the bucket name:
-<http://docs.aws.amazon.com/AmazonS3/latest/gsg/CreatingABucket.html>.
+<https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html>.
 1.  Go to the [IAM Management Console](https://console.aws.amazon.com/iam/home#/users) and create a user.
-See <http://docs.aws.amazon.com/AmazonS3/latest/dev/s3-access-control.html>.
+See <https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html>.
 1.  Then create a group and assign the user to the group.
 1.  Assign policies to the group. The `AmazonS3FullAccess` policy gives read/write access to your bucket.
 1.  Still in the IAM console, view the user you created. Click the "Security credentials" tab.
@@ -30,7 +30,7 @@ The secret key cannot be retrieved again after the key has been created, so don'
 
 !!! note
 
-    Make sure that your bucket is [configured as Public](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/block-public-access-bucket.html) to avoid facing 403 errors, as the current S3 handler is meant to store files publicly so they can be served directly from S3.
+    Make sure that your bucket is [configured as Public](https://docs.aws.amazon.com/AmazonS3/latest/userguide/configuring-block-public-access-bucket.html) to avoid facing 403 errors, as the current S3 handler is meant to store files publicly so they can be served directly from S3.
 
 ## Set up [[= product_name =]] for AWS S3
 
@@ -76,8 +76,8 @@ ibexa_io:
     `aws_s3` is an arbitrary handler identifier that is used in the config block below.
     You can configure multiple handlers.
 
-    For example, you could configure one called `gcloud_storage` for a third-party (community-supported)
-    [Google Cloud Storage adapter](https://github.com/thephpleague/flysystem#community-supported).
+    For example, you could configure one called `gcloud_storage` for a
+    [Google Cloud Storage adapter](https://github.com/thephpleague/flysystem#officially-supported-adapters).
 
 Under the `ibexa.system.<scope>.io` [configuration key](configuration.md#configuration-files), enable the binary data handler:
 

docs/personalization/api_reference/content_api.md

@@ -61,7 +61,7 @@ The following call attributes are available:
 
 | Parameter name | Description | Value |
 |---|---|---|
-| `customerid` |A customer ID (for example "00000"), as defined when [enabling Personalization](#multiple-website-hosting).| alphanumeric |
+| `customerid` | A customer ID (for example "00000"), as defined when [enabling Personalization](enable_personalization.md#get-authentication-parameters). Can be used to identify a website in installations that [hosts multiple SiteAccesses]([[= user_doc =]]/personalization/use_cases/#multiple-website-hosting). | alphanumeric |
 | `itemid` | A unique ID of the Content item/product. Used to identify the item in the database. | integer |
 | `itemtypeid` | An ID of the type of Content item/product. In most cases, the value is 1 but you might have items/products of more than one type. | integer |
 | `lang` | A [language code](languages.md) of the Content item/product (for example, "ger-DE"). This parameter is optional. | string |

docs/personalization/api_reference/tracking_api.md

@@ -199,7 +199,7 @@ By using the shopping cart products as input for getting recommendations, proble
 with an empty profile or no buy history for the user can be solved.
 The more valuable Basket events instead of recent user clicks can be used to provide
 personalized recommendations.
-It also happens quite often that users "store" products on their shopping [wishlist](#wishlist)
+It also happens quite often that users "store" products on their shopping [wishlist](#wishlist-event)
 and plan to buy them later.
 With the help of this information, personalized shopping cart-based recommendations
 can be provided in the whole shop.

docs/resources/new_in_doc.md

@@ -216,7 +216,7 @@ This page contains recent highlights and notable changes in [[= product_name =]]
 
 ### Personalization
 
-- [Email triggers](https://doc.ibexa.co/en/master/personalization/integrate_recommendation_service/#send-emails-with-recommendations)
+- [Email triggers](https://doc.ibexa.co/en/master/personalization/integrate_recommendation_service/#send-messages-with-recommendations)
 - [Email triggers](https://doc.ibexa.co/projects/userguide/en/master/personalization/triggers/) in user documentation
 
 ### Search

docs/search/search_engines/elastic_search/configure_elastic_search.md

@@ -9,8 +9,8 @@ description: Configure Elasticsearch to use it with Ibexa DXP.
 To configure Elasticsearch, first, you need to configure the connections. 
 
 There are two possibilities of connection:
-- using [cluster of Elasticsearch nodes](#cluster)
-- using [Elasticsearch Cloud](#elasticsearch-cloud)
+- using [cluster of Elasticsearch nodes](#configure-clustering)
+- using [Elasticsearch Cloud](#configure-elasticsearch-cloud)
 
 No matter which option you choose, you have to define the connection settings under the `connections` key. 
 Set a name of the connection:
@@ -35,8 +35,8 @@ ibexa_elasticsearch:
 Now, you need to decide whether to add a cluster that you administer and manage yourself, or use a cloud
 solution from Elastic, as well as configure additional parameters.
 
-If you want to connect by using a cluster, follow the instructions below in the [Cluster](#cluster) section.
-If you want to use Elasticsearch Cloud, skip to [Elasticsearch Cloud](#elasticsearch-cloud) section.
+If you want to connect by using a cluster, follow the instructions below in the [Cluster](#configure-clustering) section.
+If you want to use Elasticsearch Cloud, skip to [Elasticsearch Cloud](#configure-elasticsearch-cloud) section.
 
 ## Configure clustering
 
@@ -149,7 +149,7 @@ If you prefer a different strategy, or have created your own, custom strategy, y
     connection_selector: Elasticsearch\ConnectionPool\Selectors\<selector_name>
 ```
 
-For more information and a list of available choices, see [Selectors](https://www.elastic.co/guide/en/elasticsearch/client/php-api/current/selectors.html).
+For more information and a list of available choices, see [Selectors](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/selectors.html).
 
 ##### Number of retries
 
@@ -166,7 +166,7 @@ By default, `null` is used, which means that the number of retries equals to the
 Depending on the connection pool that you select, [[= product_name =]]'s reaction to reaching the maximum
 number of retries might differ.
 
-For more information, see [Set retries](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/configuration.html#_set_retries).
+For more information, see [Set retries](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/set-retries.html).
 
 ## Configure Elasticsearch Cloud
 
@@ -308,7 +308,7 @@ To do this, pass the following setting under the `ssl` key:
 verification: false
 ```
 
-For more information, see [Elasticsearch: SSL Encryption](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/security.html#_ssl_encryption_2).
+For more information, see [Elasticsearch: SSL Encryption](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/connceting.html#ssl-encryption).
 
 ### Enable debugging
 

docs/search/search_engines/elastic_search/install_elastic_search.md

@@ -64,9 +64,9 @@ All configuration is made in the `/config/packages/ibexa_elasticsearch.yaml` fil
     the Elasticsearch documentation.
 
 First, decide how [[= product_name =]] connects to Elasticsearch and configure other connection settings.
-For more information, see [Configuring connections](configure_elastic_search.md#connections).
+For more information, see [Configuring connections](configure_elastic_search.md#configure-connections).
 
-Then, define a Field Type mappings template that instructs Elasticsearch to interpret [[= product_name =]] fields as specific types. For more information, see [Configuring Field Type mappings](configure_elastic_search.md#field-type-mapping-templates).
+Then, define a Field Type mappings template that instructs Elasticsearch to interpret [[= product_name =]] fields as specific types. For more information, see [Configuring Field Type mappings](configure_elastic_search.md#define-field-type-mapping-templates).
 
 ## Push the templates
 

docs/search/search_engines/legacy_search_engine/legacy_search_overview.md

@@ -8,7 +8,7 @@ Legacy search engine is the default search engine. It is SQL-based and uses Doct
 The connections are defined in the same way as for storage engine, and no further specific configuration is needed.
 Legacy search engine is recommended for basic needs and is not intended in production.
 It allows you to use filtering and fulltext search, but with some limitations.
-For more information, check [search engine comparison](search_engines.md#search-engine-comparison)
+For more information, check [search engine comparison](search_engines.md#search-engines-comparison)
 
 !!! tip
 

docs/search/sort_clause_reference/datetrashed_sort_clause.md

@@ -1,6 +1,6 @@
 # DateTrashed Sort Clause
 
-The [`DateTrashed` Sort Clause](https://github.com/ibexa/core/tree/main/src/contracts/Repository/Values/Content/Query/SortClause/Trash/DateTrashed.php)
+The [`DateTrashed` Sort Clause](https://github.com/ibexa/core/blob/main/src/contracts/Repository/Values/Content/Query/SortClause/Trash/DateTrashed.php)
 sorts the results of searching in Trash by the date and time when the Content item was sent to trash.
 
 ## Arguments