Fix typos in links

mnocon · mnocon · commit a7d7a4db27e4 · 2026-05-15T14:49:31.000+02:00
diff --git a/docs/administration/project_organization/bundles.md b/docs/administration/project_organization/bundles.md
@@ -143,4 +143,4 @@ The following packages are optional and can be installed independently.
 |ibexa/cdp|Integration with the [Customer Data Platform](cdp.md)|
 |[ibexa/cloud](https://github.com/ibexa/cloud)|Integration with [[[= product_name_cloud =]]](/ibexa_cloud/ibexa_cloud.md)|
 
-In addition, you can extend the capabitilies of your project by installing additional [LTS Updates](editions.md#lts-updates).
+In addition, you can extend the capabilities of your project by installing additional [LTS Updates](editions.md#lts-updates).
diff --git a/docs/api/notification_channels.md b/docs/api/notification_channels.md
@@ -201,7 +201,7 @@ The `ControllerFeedback` notification is sent in a controller action:
 ```
 
 For the example, the notification is sent in a back office context for all editions and on the front end for Commerce edition.
-An empty template only extending the pagelayout is used for the demonstration.
+An empty template only extending the page layout is used for the demonstration.
 
 `templates/themes/admin/notification-sender-controller.html.twig`:
 ``` twig
diff --git a/docs/commerce/shopping_list/shopping_list_guide.md b/docs/commerce/shopping_list/shopping_list_guide.md
@@ -64,10 +64,10 @@ In the out-of-the-box [storefront](storefront.md), a shopping list user can:
     - products are kept in shopping list while added to the cart
     - products out-of-stock aren't copied and the user is warned
     - product quantities are incremented by 1, the user can adjust quantities in the cart
-  ![Shopping list product list with highligts on "Add to cart" and "Add all to cart" buttons](img/add_to_cart.png "“Add to cart” and “Add all to cart” buttons")
+  ![Shopping list product list with highlights on "Add to cart" and "Add all to cart" buttons](img/add_to_cart.png "“Add to cart” and “Add all to cart” buttons")
 - Move a product from cart to “My Wishlist” (product is removed from cart and added to the default shopping list)
 - Move the whole cart to “My Wishlist” (products are removed from cart and added to the default shopping list)
-  ![Cart's product list with highligts on "Move to My Wishlist" and "Move all to wishlist" buttons](img/move_to_my_wishlist.png "“Move to My Wishlist” and “Move all to wishlist” buttons")
+  ![Cart's product list with highlights on "Move to My Wishlist" and "Move all to wishlist" buttons](img/move_to_my_wishlist.png "“Move to My Wishlist” and “Move all to wishlist” buttons")
 - Delete a shopping list
 
 ## Extensibility
diff --git a/docs/content_management/content_api/creating_content.md b/docs/content_management/content_api/creating_content.md
@@ -49,7 +49,7 @@ Value of the Image field type contains the path to the image file and other basi
 
 ### Creating content with RichText
 
-The RichText field accepts values in a custom flavor of [Docbook](https://github.com/docbook/wiki/wiki) format.
+The RichText field accepts values in a custom flavor of [DocBook](https://github.com/docbook/wiki/wiki) format.
 For example, to add a RichText paragraph, provide the following as input:
 
 ``` xml
diff --git a/docs/content_management/data_migration/importing_data.md b/docs/content_management/data_migration/importing_data.md
@@ -465,7 +465,7 @@ The following example creates an image [content item](#content-items) from a loc
 ```
 
 This migration uses a [reference](managing_migrations.md#references) to store the created image content ID, and then uses it while creating the asset.
-It uses an [expression syntax](#expression-syntax) to [concat (`~`)]([[= symfony_doc =]]/reference/formats/expression_language.html#string-operators)
+It uses an [expression syntax](#expression-syntax) to [concatenate (`~`)]([[= symfony_doc =]]/reference/formats/expression_language.html#string-operators)
 the mandatory scheme `ezcontent://` and the image content ID through the [`reference` function](#built-in-functions) used on the reference's name.
 
 #### Product prices
diff --git a/docs/content_management/field_types/field_type_reference/datefield.md b/docs/content_management/field_types/field_type_reference/datefield.md
@@ -58,7 +58,7 @@ Hash value of this field type is an array with two keys:
 
 | Key         | Type      | Description                                                                                                                                                         | Example                                 |
 |-------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|
-| `timestamp` | `integer` | Time information in [unix format timestamp](https://en.wikipedia.org/wiki/Unix_time).                                                                               | `1400856992`                            |
+| `timestamp` | `integer` | Time information in [Unix format timestamp](https://en.wikipedia.org/wiki/Unix_time).                                                                               | `1400856992`                            |
 | `rfc850`    | `string`  | Time information as a string in [RFC 850 date format](https://datatracker.ietf.org/doc/html/rfc850). As input, this has higher precedence over the timestamp value. | `"Friday, 23-May-14 14:56:14 GMT+0000"` |
 
 ``` php
diff --git a/docs/content_management/images/configure_image_editor.md b/docs/content_management/images/configure_image_editor.md
@@ -4,7 +4,7 @@ description: Configure image editor to crop, flip, and modify images.
 
 # Configure Image Editor
 
-When a content item contains fields of the [ibexa_image](imageassetfield.md) type, users can perform basic image editing functions with the Image Editor.
+When a content item contains fields of the [`ibexa_image`](imageassetfield.md) type, users can perform basic image editing functions with the Image Editor.
 
 For more information, see [User Documentation]([[= user_doc =]]/image_management/edit_images/).
 
diff --git a/docs/discounts/extend_discounts.md b/docs/discounts/extend_discounts.md
@@ -219,7 +219,7 @@ To do it, create a class implementing the [`DiscountValueFormatterInterface`](/a
 You can change the [the default discount priority](discounts_guide.md#discounts-priority) by creating a class implementing the [`DiscountPrioritizationStrategyInterface`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-DiscountPrioritizationStrategyInterface.html) and aliasing to it the default implementation.
 
 The example below decorates the default implementation to prioritize recently updated discounts above all the others.
-It uses one of the existing [discount search criterions](discounts_criteria.md).
+It uses one of the existing [discount search criteria](discounts_criteria.md).
 
 ``` php
 [[= include_file('code_samples/discounts/src/Discounts/RecentDiscountPrioritizationStrategy.php') =]]
diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md
@@ -67,17 +67,17 @@ You can solve this issue in one of the following ways:
 
 Varnish configuration:
 
-- [http_resp_hdr_len](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-resp-hdr-len) (default 8k, change to for example, 32k)
-- [http_max_hdr](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-max-hdr) (default 64, change to for example, 128)
-- [http_resp_size](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-resp-size) (default 23k, change to for example, 96k)
-- [workspace_backend](https://varnish-cache.org/docs/6.0/reference/varnishd.html#workspace-backend) (default 64k, change to for example, 128k)
+- [`http_resp_hdr_len`](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-resp-hdr-len) (default 8k, change to for example, 32k)
+- [`http_max_hdr`](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-max-hdr) (default 64, change to for example, 128)
+- [`http_resp_size`](https://varnish-cache.org/docs/6.0/reference/varnishd.html#http-resp-size) (default 23k, change to for example, 96k)
+- [`workspace_backend`](https://varnish-cache.org/docs/6.0/reference/varnishd.html#workspace-backend) (default 64k, change to for example, 128k)
 
-If you need to see these long headers in `varnishlog`, adapt the [vsl_reclen](https://varnish-cache.org/docs/6.0/reference/varnishd.html#vsl-reclen) setting.
+If you need to see these long headers in `varnishlog`, adapt the [`vsl_reclen`](https://varnish-cache.org/docs/6.0/reference/varnishd.html#vsl-reclen) setting.
 
 Nginx has a default limit of 4k/8k when buffering responses:
 
-- For [PHP-FPM](https://www.php.net/manual/en/install.fpm.php) setup using proxy module, configure [proxy_buffer_size](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size)
-- For FastCGI setup using fastcgi module, configure [fastcgi_buffer_size](https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_buffer_size)
+- For [PHP-FPM](https://www.php.net/manual/en/install.fpm.php) setup using proxy module, configure [`proxy_buffer_size`](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size)
+- For FastCGI setup using fastcgi module, configure [`fastcgi_buffer_size`](https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_buffer_size)
 
 Fastly has a `Surrogate-Key` header limit of 16 kB, and this cannot be changed.
 
diff --git a/docs/infrastructure_and_maintenance/cache/persistence_cache.md b/docs/infrastructure_and_maintenance/cache/persistence_cache.md
@@ -124,7 +124,7 @@ parameters:
 ### Redis/Valkey
 
 [Redis](https://redis.io/), an in-memory data structure store, is one of the supported cache solutions for clustering.
-Redis is used via [Redis pecl extension](https://pecl.php.net/package/redis).
+Redis is used via [Redis PECL extension](https://pecl.php.net/package/redis).
 
 See [Redis Cache Adapter in Symfony documentation]([[= symfony_doc =]]/components/cache/adapters/redis_adapter.html#configure-the-connection for information on how to connect to Redis.
 
diff --git a/docs/infrastructure_and_maintenance/sessions.md b/docs/infrastructure_and_maintenance/sessions.md
@@ -88,7 +88,7 @@ To set it up, you need to:
 Alternatively if you have needs to configure the servers dynamically:
 
 - Set `%ibexa.session.handler_id%` (or `SESSION_HANDLER_ID` env var) to `Ibexa\Bundle\Core\Session\Handler\NativeSessionHandler`
-- Set `%ibexa.session.save_path%` (or `SESSION_SAVE_PATH` env var) to [save_path config for Redis](https://github.com/phpredis/phpredis/#php-session-handler)
+- Set `%ibexa.session.save_path%` (or `SESSION_SAVE_PATH` env var) to [`save_path` config for Redis](https://github.com/phpredis/phpredis/#php-session-handler)
 
 !!! note "[[= product_name_cloud =]]"
 
diff --git a/docs/product_catalog/quable/quable_api.md b/docs/product_catalog/quable/quable_api.md
@@ -34,7 +34,7 @@ The following example shows how you can retrieve a single product:
 
 ### Search for products
 
-Use [`ProductQuery`](product_api.md#getting-product-information) to search for mulitple products:
+Use [`ProductQuery`](product_api.md#getting-product-information) to search for multiple products:
 
 ``` php
 [[= include_file('code_samples/api/product_catalog/src/Command/ProductCommand.php', 58, 68, remove_indent=True) =]]
diff --git a/docs/release_notes/ez_platform_v3.1.md b/docs/release_notes/ez_platform_v3.1.md
@@ -92,7 +92,7 @@ Display of field groups has been improved in content preview and editing.
 
 When editing, field groups are now presented in tabs:
 
-![Field group tabls in content editing](3.1_collapsible_fields_edit.png)
+![Field group tabs in content editing](3.1_collapsible_fields_edit.png)
 
 In Content preview, the group sections are collapsible:
 
diff --git a/docs/resources/new_in_doc.md b/docs/resources/new_in_doc.md
@@ -379,7 +379,7 @@ Documentation examples and [PHP API Reference](https://doc.ibexa.co/en/5.0/api/p
 You can use [`ibexa/rector`](https://github.com/ibexa/rector#readme) package that allows to maintain your custom PHP code quality.
 Consult the [Ibexa DXP v5.0 renames, deprecations and removals](https://doc.ibexa.co/en/5.0/release_notes/ibexa_dxp_v5.0_deprecations/) to learn more about the changes.
 
-Major additions to the PHP API Reference are [`Ibexa\Contracts\Collaboration`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-collaboration.html) and [`Ibexa\Contracts\Share`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-share.html) namespaces, the bulding blocks for the [collaboration framework](https://doc.ibexa.co/en/5.0/release_notes/ibexa_dxp_v5.0/#collaboration).
+Major additions to the PHP API Reference are [`Ibexa\Contracts\Collaboration`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-collaboration.html) and [`Ibexa\Contracts\Share`](https://doc.ibexa.co/en/5.0/api/php_api/php_api_reference/namespaces/ibexa-contracts-share.html) namespaces, the building blocks for the [collaboration framework](https://doc.ibexa.co/en/5.0/release_notes/ibexa_dxp_v5.0/#collaboration).
 
 #### REST API
 
@@ -634,7 +634,7 @@ Enhanced the PHP API with the following new classes and interfaces:
 
 ### Trainings
 
-- The Content Editor Training has been released. Learn more in the [annoucement blogpost](https://www.ibexa.co/blog/constant-development-is-key-so-here-s-a-new-training-for-content-editors)
+- The Content Editor Training has been released. Learn more in the [announcement blog post](https://www.ibexa.co/blog/constant-development-is-key-so-here-s-a-new-training-for-content-editors)
 
 ### Infrastructure and maintenance
 
@@ -684,7 +684,7 @@ Enhanced the PHP API with the following new classes and interfaces:
 ### Search
 
 - New [`IsBookmarked` location criterion](https://doc.ibexa.co/en/4.6/search/criteria_reference/isbookmarked_criterion/)
-- [`IsUserEnabled` is now available on Solr and Elastisearch](https://doc.ibexa.co/en/4.6/search/criteria_reference/isuserenabled_criterion/)
+- [`IsUserEnabled` is now available on Solr and Elasticsearch](https://doc.ibexa.co/en/4.6/search/criteria_reference/isuserenabled_criterion/)
 
 ### Documentation
 
@@ -1080,7 +1080,7 @@ Enhanced the PHP API with the following new classes and interfaces:
 
 ### Storefront
 
-- [Display language name instead of its code in language swticher](https://doc.ibexa.co/en/4.6/templating/twig_function_reference/storefront_twig_functions/#ibexa_storefront_get_language_name_by_code)
+- [Display language name instead of its code in language switcher](https://doc.ibexa.co/en/4.6/templating/twig_function_reference/storefront_twig_functions/#ibexa_storefront_get_language_name_by_code)
 
 ### Templating
 
diff --git a/docs/update_and_migration/from_4.6/update_from_4.6.md b/docs/update_and_migration/from_4.6/update_from_4.6.md
@@ -478,7 +478,7 @@ When you use [[= product_name_cloud =]], see [Elasticsearch service](https://doc
 
 #### Update configuration
 
-Update your configuration in `config/packages/ibexa_elasticsearch.yaml` as decribed below:
+Update your configuration in `config/packages/ibexa_elasticsearch.yaml` as described below:
 
 ##### Replace connection pool settings
 
diff --git a/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md b/docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md
@@ -302,7 +302,7 @@ Run the conversion script on a copy of your production database as the script is
 
 `php -d memory_limit=1536M bin/console ezxmltext:convert-to-richtext --dry-run --export-dir=ezxmltext-export --export-dir-filter=notice,warning,error --concurrency 4 -v`
 
-- `-d memory_limit=1536M` specifies that each conversion process gets 1536MB of memory. This should be more than sufficient for most databases. If you have small `ezxmltext` documents, you may decrease the limit. If you have huge `ezxmltext` documents, you may need to increase it. See PHP documentation for more information about the [memory_limit setting](https://www.php.net/manual/en/ini.core.php#ini.memory-limit).
+- `-d memory_limit=1536M` specifies that each conversion process gets 1536MB of memory. This should be more than sufficient for most databases. If you have small `ezxmltext` documents, you may decrease the limit. If you have huge `ezxmltext` documents, you may need to increase it. See PHP documentation for more information about the [`memory_limit` setting](https://www.php.net/manual/en/ini.core.php#ini.memory-limit).
 - `--dry-run` prevents the conversion script from writing anything back to the database. It just tests if it's able to convert all the `ezxmltext` documents.
 - `--export-dir` specifies a directory where it dumps the `ezxmltext` for content object attributes which the conversion script finds problems with
 - `--export-dir-filter` specifies what severity the problems found needs to be before the script dumps the `ezxmltext`:
