Markdownlint: added no-space-in-code

Author: mnocon

.markdownlint-cli2.yaml

@@ -22,7 +22,7 @@ config:
 # no-alt-text: true
 # single-trailing-newline: true
 # no-emphasis-as-heading: true
-# no-space-in-code: true
+  no-space-in-code: true
 # no-space-in-links: true
 # fenced-code-language: true
 # first-line-heading: true

docs/api/event_reference/discounts_events.md

@@ -47,7 +47,7 @@ The following events are dispatched when rendering each step of the discount wiz
 |[`CreateFormDataEvent`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Event-Step-CreateFormDataEvent.html)| `ibexa.discounts.form_mapper.<step_identifier>.create_form_data`|
 |[`MapCreateDataToStructEvent`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Event-Step-MapCreateDataToStructEvent.html)|`ibexa.discounts.form_mapper.<step_identifier>.map_create_data_to_struct`|
 |[`MapDiscountToFormDataEvent`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Event-Step-MapDiscountToFormDataEvent.html)| `ibexa.discounts.form_mapper.<step_identifier>.map_discount_to_form_data`|
-|[`MapUpdateDataToStructEvent`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Event-Step-MapUpdateDataToStructEvent.html)|`ibexa.discounts.form_mapper.<step_identifier>.map_update_data_to_struct `|
+|[`MapUpdateDataToStructEvent`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Discounts-Event-Step-MapUpdateDataToStructEvent.html)|`ibexa.discounts.form_mapper.<step_identifier>.map_update_data_to_struct`|
 
 The event classes are shared between steps, but they are dispatched with different names.
 Each step form mapper dispatches its own set of events.

docs/content_management/field_types/field_type_reference/authorfield.md

@@ -14,7 +14,7 @@ This field type allows the storage and retrieval of one or more authors. For eac
 
 | Attribute | Type                                     | Description      | Example   |
 |-----------|------------------------------------------|------------------|-----------|
-| `authors` | `\Ibexa\Core\FieldType\Author\Author[] ` | List of authors. | See below |
+| `authors` | `\Ibexa\Core\FieldType\Author\Author[]` | List of authors. | See below |
 
 Example:
 

docs/content_management/rich_text/extend_online_editor.md

@@ -386,7 +386,7 @@ For a full list of standard buttons, see the RichText module's [configuration fi
 Regular CKEditor plugins can be added to the Online Editor.
 This procedure is illustrated with the addition of the [Special characters plugin](https://ckeditor.com/docs/ckeditor5/latest/features/special-characters.html).
 
-You can install a CKEditor plugin locally by using `yarn add ` or `npm install`, and deploy it by committing the `yarn.lock` file.
+You can install a CKEditor plugin locally by using `yarn add` or `npm install`, and deploy it by committing the `yarn.lock` file.
 A local installation looks like:
 
 ```bash

docs/content_management/workflow/workflow.md

@@ -165,7 +165,7 @@ However, during the publish action, the sent form is validated in the service.
 Therefore, if there are any errors in the form, you return to the edit page but errors aren't triggered, which can be confusing when you have two or more tabs.
 
 To enable form validation in UI before sending it to the next stage of the workflow, add `validate: true` to the transitions of the stage.
-In the example below the form is validated in two stages:` to_legal` and `done`:
+In the example below the form is validated in two stages: `to_legal` and `done`:
 
 ``` yaml hl_lines="15 28"
 [[= include_file('code_samples/workflow/custom_workflow/config/packages/workflows.yaml', 23, 43) =]][[= include_file('code_samples/workflow/custom_workflow/config/packages/workflows.yaml', 55, 63) =]]

docs/personalization/tracking_with_ibexa-tracker.md

@@ -26,7 +26,7 @@ To use this mechanism on your pages, copy the code snippet below, and replace:
 - `<USER_ID>` with an empty string for cookie based anonymous user or with the value generated by your user identifier system for logged-in user. In case user activity should not be tracked, 'not_defined' value should be used to still have an event stored without a link to the user.
 
 All identifiers can be any form of string.
-Paste this snippet into your website template page so that it appears before the closing `</head>` tag.
+Paste this snippet into your website template page so that it appears before the closing `</head>` tag.
 
 ``` js
 <script type="text/javascript">
@@ -48,9 +48,9 @@ Paste this snippet into your website template page so that it appears before the
 
 ## Asynchronous syntax
 
-The `_ycq` object is what makes the asynchronous syntax possible.
-It acts as a queue, which is a "first-in, first-out" (FIFO) data structure that collects API calls until `ibexa-tracker.js` is ready to run them.
-To add to the queue, use the `_ycq.push` method.
+The `_ycq` object is what makes the asynchronous syntax possible.
+It acts as a queue, which is a "first-in, first-out" (FIFO) data structure that collects API calls until `ibexa-tracker.js` is ready to run them.
+To add to the queue, use the `_ycq.push` method.
 
 To push an API call into the queue, you must convert it from the traditional JavaScript syntax to a command array.
 Command arrays are JavaScript arrays that conform to a certain format.
@@ -60,7 +60,7 @@ These can be any JavaScript value.
 
 ## Tracking code
 
-The `_ycq` global object can be used directly for asynchronous page tracking with the `push(...)` method. 
+The `_ycq` global object can be used directly for asynchronous page tracking with the `push(...)` method. 
 
 ### `_ycq` object methods
 
@@ -84,9 +84,9 @@ _ycq.push(['_trackEvent', '1', 'click', '10', '']);
 
 | Object          | Description   | Example |
 | --------------- | ------------- | ------ |
-| `_setMandator ` | - Executed with one additional parameter: `MandatorId` | `_ycq.push (['_setMandator' , '<YOUR_MANDATOR_ID>']);` |
+| `_setMandator` | - Executed with one additional parameter: `MandatorId` | `_ycq.push(['_setMandator' , '<YOUR_MANDATOR_ID>']);` |
 | `_trackEvent` | - Executed with four additional parameters: `ItemType`, `EventType`, `ItemId`, `UserId`.<br /> - `EventType` can be any of the [described types]([[= user_doc =]]/personalization/event_types/) | capturing an event: `_ycq.push(['_trackEvent', '1', 'buy', '10', '']);` |
-| `_trackTimedEvent` | - Executed with five additional parameters: `ItemType`, `EventType`, `ItemId`, `Timeout`, `UserId`.<br /> - `EventType` can be any of the [described types]([[= user_doc =]]/personalization/event_types/).<br /> - `Timeout` can be any integer greater than 0 representing time in ms | consume event sent after 20s: `_ycq.push(['_trackTimedEvent', '1', 'consume', '10', '20000', '']);` |
+| `_trackTimedEvent` | - Executed with five additional parameters:`ItemType`, `EventType`, `ItemId`, `Timeout`, `UserId`.<br /> - `EventType` can be any of the [described types]([[= user_doc =]]/personalization/event_types/).<br /> - `Timeout` can be any integer greater than 0 representing time in ms | consume event sent after 20s: `_ycq.push(['_trackTimedEvent', '1', 'consume', '10', '20000', '']);` |
 | `_login` | - Executed with two additional parameters: anonymous userId, pseudonymous userId.<br /> - It is to be triggered when a user logs in and the tracking identity is changed.<br /> | - |
 | `ycreco=true` | - If you want to send a click recommended event you can append the following parameter to the recommended item URLs: | [https://mydomain.com/mypage.html?ycreco=true](https://mydomain.com/mypage.html?ycreco=true) or <br />[https://mydomain.com/mypage.html?myparameter=x&ycreco=true](https://mydomain.com/mypage.html?myparameter=x&ycreco=true) |
 
@@ -99,4 +99,4 @@ For example, the following button generates an event when it's clicked:
 <button onclick = "_ycq.push(['_trackEvent', '2', 'click', 'itemId1', ''])"/><button>
 ```
 
-Even if this button is clicked before the browser has finished loading `ibexa-tracker.js`, the event is captured and eventually executed.
+Even if this button is clicked before the browser has finished loading `ibexa-tracker.js`, the event is captured and eventually executed.

docs/release_notes/ez_platform_v1.7.0_lts.md

@@ -53,7 +53,7 @@ Community members are more than welcome to contribute to the translation process
     -    QueryType's now support using alias when being used as service so you can define several services with same  QueryType class
         -    Example: Generic location child QueryType being reused several times for specific services for article or blog post listings 
 -   API:
-    -   New method:` Location->getSortClauses()` to get Sort Clauses based on what kind of sorting has been set on the Location
+    -   New method: `Location->getSortClauses()` to get Sort Clauses based on what kind of sorting has been set on the Location
     -   Add Content Version archives limit by configuration & enforce on publish
 -   Debug:
     -   ez-support-tools:dump-info command now able to dump system info in several formats, and default is now json