Markdownlint: no-trailing-spaces

Author: mnocon

.markdownlint-cli2.yaml

@@ -39,7 +39,7 @@ config:
 # ul-style: dash
 # ul-indent:
 #   indent: 4
-# no-trailing-spaces: true
+  no-trailing-spaces: true
   no-multiple-blanks: true
   commands-show-output: true
 

docs/administration/back_office/integrated_help.md

@@ -15,7 +15,7 @@ Integrated help is contextual, therefore, apart from user documentation, release
 
 ## Install package
 
-Integrated help is optional. 
+Integrated help is optional.
 To enable it, run the following command:
 
 ```bash

docs/administration/back_office/subitems_list.md

@@ -10,7 +10,7 @@ It provides an interface for listing the sub-items of any location.
 
 ## Create custom sub-items list view
 
-You can extend the Sub-items List module to replace an existing view or add your own. 
+You can extend the Sub-items List module to replace an existing view or add your own.
 The example below adds a new timeline view to highlight the modification date.
 
 ![Sub-items List module using the new Timeline view](img/subitems/timeline_view.png "Sub-items List module using the new Timeline view")

docs/ai_actions/extend_ai_actions.md

@@ -32,7 +32,7 @@ Both `ActionContext` and `RuntimeContext` are passed to the Action Handler (an o
 
 You can pass the Action Handler directly to the `ActionServiceInterface::execute()` method, which overrides all the other ways of selecting the Action Handler.
 You can also specify the Action Handler by including it in the provided [Action Configuration](#action-configurations).
-In other cases, the Action Handler is selected automatically. 
+In other cases, the Action Handler is selected automatically.
 You can affect this choice by creating your own class implementing the [ActionHandlerResolverInterface](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorAi-Action-ActionHandlerResolverInterface.html) or by listening to the [ResolveActionHandlerEvent](/api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorAi-Events-ResolveActionHandlerEvent.html) Event sent by the default implementation.
 
 You can influence the execution of an Action with two events:

docs/content_management/field_types/field_type_reference/field_type_reference.md

@@ -18,7 +18,7 @@ In addition, it's possible to extend the system by creating custom types for spe
 
     For general field type documentation, see [field type](field_types.md).
 
-Custom field types have to be programmed in PHP. 
+Custom field types have to be programmed in PHP.
 However, the built-in field types are usually enough for typical scenarios.
 The following table gives an overview of the supported field types that come with [[= product_name =]].
 

docs/content_management/field_types/field_type_reference/measurementfield.md

@@ -1,6 +1,6 @@
 # Measurement field type
 
-The Measurement field type represents measurement information. 
+The Measurement field type represents measurement information.
 It stores the unit of measure, and either a single measurement value, or a pair of top and bottom values that defines a range.
 
 | Name          | Internal name       | Expected input type                                |
@@ -12,8 +12,8 @@ It stores the unit of measure, and either a single measurement value, or a pair
 ### Input expectations
 
 To create a value, you use a service that implements `Ibexa\Contracts\Measurement\MeasurementServiceInterface`.
-You must inject the service directly with [dependency injection](php_api.md#service-container). 
-The service contains the following API endpoints: 
+You must inject the service directly with [dependency injection](php_api.md#service-container).
+The service contains the following API endpoints:
 
 - `buildSimpleValue` that is used to handle a single value
 - `buildRangeValue` that is used to handle a range
@@ -37,7 +37,7 @@ The Value class of this field type contains the following properties:
 
 ##### Constructor
 
-The `Measurement\Value` constructor for this value object initializes a new value object with the value provided. 
+The `Measurement\Value` constructor for this value object initializes a new value object with the value provided.
 As its first argument it accepts an object of `Ibexa\Contracts\Measurement\Value\ValueInterface` type.
 
 Depending on the selected input type, the object resembles the following examples:

docs/content_management/forms/create_form_attribute.md

@@ -106,7 +106,7 @@ Now, the attribute value can be stored in the new Form.
 
 ## Create submission converter
 
-The new field is based on a checkbox, so to display the submissions of this field, you can use the `BooleanFieldSubmissionConverter`. 
+The new field is based on a checkbox, so to display the submissions of this field, you can use the `BooleanFieldSubmissionConverter`.
 
 Create a `src/FormBuilder/FormSubmission/Converter/RichtextDescriptionFieldSubmissionConverter.php` file.
 

docs/content_management/forms/work_with_forms.md

@@ -44,7 +44,7 @@ For information about available options, see [Gregwar/CaptchaBundle's documentat
 
 ## Form submission purging
 
-You can purge all submissions of a given form. 
+You can purge all submissions of a given form.
 To do this, run the following command, where `form-id` stands for Content ID of the form for which you want to purge data:
 
 ```bash

docs/content_management/images/add_image_asset_from_dam.md

@@ -157,7 +157,7 @@ In this example, the search only uses the main text input.
 The tab and its corresponding panel are a service created by combining existing components, like in the case of other [back office tabs](back_office_tabs.md).
 
 The `commons_search_tab` service uses the `GenericSearchTab` class as a base, and the `GenericSearchType` form for search input.
-It is linked to the `commons` DAM source and uses the identifier `commons`. 
+It is linked to the `commons` DAM source and uses the identifier `commons`.
 The DAM search tab is registered in the `connector-dam-search` [tab group](back_office_tabs.md#tab-groups) using the `ibexa.admin_ui.tab` tag.
 
 ```yaml

docs/content_management/images/images.md

@@ -51,8 +51,8 @@ php bin/console liip:imagine:cache:remove
 With [image variations](image_variations.md) (image aliases) you can define and use different versions of the same image.
 You generate variations based on [filters](image_variations.md#available-variation-filters) that modify aspects such as size and proportions, quality or effects.
 
-Image variations are generated with [LiipImagineBundle](https://github.com/liip/LiipImagineBundle), by using the underlying [Imagine library](https://imagine.readthedocs.io/en/latest/). 
-The LiipImagineBundle bundle supports GD (default), Imagick or Gmagick PHP extensions, and enables you to define flexible filters in PHP. 
+Image variations are generated with [LiipImagineBundle](https://github.com/liip/LiipImagineBundle), by using the underlying [Imagine library](https://imagine.readthedocs.io/en/latest/).
+The LiipImagineBundle bundle supports GD (default), Imagick or Gmagick PHP extensions, and enables you to define flexible filters in PHP.
 Image files are stored by using the `IOService,` and are completely independent from the Image field type.
 They're generated only once and cleared on demand, for example, on content removal).