ul-indent

Author: mnocon

.markdownlint-cli2.yaml

@@ -37,8 +37,8 @@ config:
   blanks-around-headings: true
 # heading-increment: true
   ul-style: dash
-# ul-indent:
-#   indent: 4
+  ul-indent:
+    indent: 4
   no-trailing-spaces: true
   no-multiple-blanks: true
   commands-show-output: true

docs/content_management/images/images.md

@@ -141,8 +141,8 @@ The [`GenericProvider`](https://github.com/ibexa/core/blob/5.0/src/bundle/Core/I
 
 With the [`RemoteProvider`](https://github.com/ibexa/core/blob/5.0/src/bundle/Core/Imagine/PlaceholderProvider/RemoteProvider.php) you can download placeholders from:
 
- - remote sources, for example, <http://placekitten.com> (see [example 2](#configuration-examples))
- - live version of a site (see [example 3](#configuration-examples))
+- remote sources, for example, <http://placekitten.com> (see [example 2](#configuration-examples))
+- live version of a site (see [example 3](#configuration-examples))
 
 ![Placeholder RemoteProvider - placekitten.com](placeholder_remote_provider.jpg "Remote placeholder images on a page")
 

docs/infrastructure_and_maintenance/clustering/clustering_with_ddev.md

@@ -218,9 +218,9 @@ You can now check whether Solr works.
 
 For example, the `ddev exec curl -s http://solr:SolrRocks@solr:8983/api/cores/` command:
 
- - checks whether the `web` server can access the `solr` server
- - checks whether `collection1` exists and its status
- - displays `collection1`'s `numDocs` that shouldn't be zero if indexing worked correctly
+- checks whether the `web` server can access the `solr` server
+- checks whether `collection1` exists and its status
+- displays `collection1`'s `numDocs` that shouldn't be zero if indexing worked correctly
 
 You can access the Solr admin UI from the host by:
 

docs/personalization/integrate_recommendation_service.md

@@ -170,8 +170,8 @@ To let your visitors receive emails with recommendations:
 Out of many options, it could be an [[= product_name_connect =]] [webhook]([[= connect_doc =]]/tools/webhooks/).
 The endpoint must meet the following requirements:
 
- - must support POST requests
- - must accept JSON objects in a format that resembles the following example:
+- must support POST requests
+- must accept JSON objects in a format that resembles the following example:
 
 ``` json
 {

docs/resources/new_in_doc.md

@@ -134,7 +134,7 @@ This promotes skipping the rebuild of the Symfony container when environment var
 
 ### Infrastructure
 
- - [MariaDB 11.4 is officially supported on v5 and v4.6](requirements.md#dbms)
+- [MariaDB 11.4 is officially supported on v5 and v4.6](requirements.md#dbms)
 
 ### Taxonomy
 

docs/update_and_migration/from_4.6/update_to_5.0.md

@@ -43,8 +43,8 @@ Customize the `rector.php` config file by:
 
 - making it match your directory structure (for example, you may not have the `tests` directory)
 - adding project-specific rules:
-  - specify [PHP rules by using `withPhpSets`](https://getrector.com/documentation/set-lists#content-php-sets)
-  - specify [Symfony, Twig, or Doctrine rules by using `withComposerBased`](https://getrector.com/documentation/composer-based-sets).
+    - specify [PHP rules by using `withPhpSets`](https://getrector.com/documentation/set-lists#content-php-sets)
+    - specify [Symfony, Twig, or Doctrine rules by using `withComposerBased`](https://getrector.com/documentation/composer-based-sets).
 
 It's recommended to activate one rule set at a time and preview the output by running Rector with the `--dry-run` option to decide which rulesets should be used and in which order.