no-emphasis-as-heading

Author: mnocon

.markdownlint-cli2.yaml

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

docs/administration/admin_panel/roles_admin_panel.md

@@ -10,7 +10,7 @@ To give users an access to your website you need to assign them roles in the **A
 
 Each role consists of:
 
-**Policies**
+## Policies
 
 ![Policies](admin_panel_policies.png "Policies")
 
@@ -27,7 +27,7 @@ See [example use case](permission_use_cases.md#restrict-editing-to-part-of-the-t
 
     For more information, see [Limitation reference](limitation_reference.md).
 
-**Assignments**
+## Assignments
 
 ![Assignments](admin_panel_assignments.png "Assignments")
 

docs/api/rest_api/rest_api_authentication.md

@@ -353,7 +353,7 @@ For details, see [RFC 2617](https://datatracker.ietf.org/doc/html/rfc2617).
 Most HTTP client libraries and REST libraries support this method.
 [Creating content with binary attachments](rest_requests.md#creating-content-with-binary-attachments) is an example of using basic authentication with [cURL](https://www.php.net/manual/en/book.curl.php) and its `CURLOPT_USERPWD`.
 
-**Raw HTTP request with basic authentication**
+See the following raw HTTP request with basic authentication example:
 
 ```http
 GET / HTTP/1.1

docs/content_management/images/images.md

@@ -168,19 +168,19 @@ If there is no configuration assigned to the `binary_handler`, the placeholder g
 
 #### Configuration examples
 
-**Example 1 - placeholders with basic information about original image**
+##### Example 1 - placeholders with basic information about original image
 
 ```yaml
 [[= include_file('code_samples/back_office/images/config/packages/images_basic.yaml') =]]
 ```
 
-**Example 2 - placeholders from remote source**
+##### Example 2 - placeholders from remote source
 
 ```yaml
 [[= include_file('code_samples/back_office/images/config/packages/images_remote.yaml') =]]
 ```
 
-**Example 3 - placeholders from live version of a site**
+##### Example 3 - placeholders from live version of a site
 
 ```yaml
 [[= include_file('code_samples/back_office/images/config/packages/images_live.yaml') =]]

docs/infrastructure_and_maintenance/cache/persistence_cache.md

@@ -54,7 +54,7 @@ Use of Redis as shared cache back end is a requirement for use in clustering set
 For an overview of this feature, see [Clustering](clustering.md).
 Filesystem adapters, for example, are **not** intended to be used over a shared filesystem.
 
-**Cache service**
+### Cache service
 
 The underlying cache system is exposed as an `ibexa.cache_pool` service, and can be reused by any other service as described in the [Using Cache service](#using-cache-service) section.
 

docs/search/search_engines/elasticsearch/elasticsearch_overview.md

@@ -17,7 +17,7 @@ Thanks to this mechanism, it's able to achieve fast response.
 For a detailed description of advanced settings that you might require in a specific production environment, see the documentation provided by Elastic.
 Start with the [Set up Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/8.19/setup.html) section.
 
-**Prerequisite**
+## Prerequisite
 
 To proceed you need to be familiar with how indexing, filtering and queries work.
 

docs/update_and_migration/migrate_to_ibexa_dxp/migrating_from_ez_publish_platform.md

@@ -410,9 +410,11 @@ Once you have fixed all the dump files in `ezxmltext-export/`, you may skip the
 
 `php -d memory_limit=1536M bin/console ezxmltext:import-xml --export-dir=ezxmltext-export -v`
 
+##### Typical problems
+
 Typical problems that needs manual fixing:
 
-**Duplicate XHTML IDs**
+###### Duplicate XHTML ID
 
 XHTML IDs needs to be unique. The following `ezxmltext` results in a warning:
 
@@ -428,7 +430,7 @@ XHTML IDs needs to be unique. The following `ezxmltext` results in a warning:
 The conversion tool replaces the duplicate id (`inv5`) with a random value. If you need the ID value to match your CSS, you need to change it manually.
 The conversion tool also complains about IDs which contain invalid characters.
 
-**Links with non-existing `object_remote_id` or `node_remote_id`.**
+###### Links with non-existing `object_remote_id` or `node_remote_id`
 
 In `ezxmltext` you may have links which refer to other objects by their remote ID. This isn't supported in `richtext`, so the conversion tool must look up such remote IDs and replace them with the `object_id` or `node_id`. If the conversion tool cannot find the object by its remote id, it issues a warning about it.
 
@@ -440,15 +442,15 @@ In older eZ Publish databases you may also have invalid links due to lack of ref
 
 When the conversion tool detects links with no reference it issues a warning and rewrite the URL to point to current page (`href="#"`).
 
-**`<literal>`**
+###### `<literal>`
 
 The `<literal>` tag isn't yet supported in eZ Platform.
 
 When you're ready to migrate your eZ Publish XmlText content to the eZ Platform RichText format and start using pure eZ Platform setup, start the conversion script without the `--dry-run` option. Execute the following from &lt;new-ez-root&gt;:
 
 `php -d memory_limit=1536M bin/console ezxmltext:convert-to-richtext --export-dir=ezxmltext-export --export-dir-filter=notice,warning,error --concurrency 4 -v`
 
-**Custom tags and attributes**
+###### Custom tags and attributes
 
 eZ Platform now supports custom tags, including inline custom tags, and limited use of custom tag attributes.
 After migrating to RichText, you need to adapt your custom tag config for eZ Platform and rewrite the custom tags in Twig.
@@ -574,18 +576,16 @@ new EzSystems\EzFlowMigrationToolkitBundle\EzSystemsEzFlowMigrationToolkitBundle
 bin/console cache:clear
 ```
 
-**4.** Run the script with the following parameters:
+**4.** Run the script below with the following parameters:
 
 - absolute path of your legacy application
 - list of .ini files which define your legacy blocks
 
-**Script command**
-
 ``` bash
 bin/console ezflow:migrate <legacy path> —ini=<block definitions> [—ini=<another block definition> ...]
 ```
 
-**Example of the migration script command**
+Example usage:
 
 ``` bash
 bin/console ezflow:migrate /var/www/legacy.application.com/ —ini=extension/myapplication/settings/block.ini.append.php