heading-increment

Author: mnocon

.markdownlint-cli2.yaml

@@ -14,34 +14,7 @@ config:
   table-pipe-style:
     style: leading_and_trailing
 
-# table-column-count: true
-  blanks-around-tables: true
-  descriptive-link-text: true
-# table-column-style: aligned
-  link-fragments: true
-  no-alt-text: true
-  single-trailing-newline: true
-# no-emphasis-as-heading: true
-  no-space-in-code: true
-  no-space-in-links: true
-  fenced-code-language: true
-  first-line-heading: true
-  ol-prefix: one_or_ordered
-  list-marker-space: true
-  blanks-around-fences: true
-  blanks-around-lists: true
-  single-title: true
-  no-trailing-punctuation:
-    punctuation: [".", ":", ";",]
-  no-multiple-space-atx: true
-  blanks-around-headings: true
-# heading-increment: true
-  ul-style: dash
-  ul-indent:
-    indent: 4
-  no-trailing-spaces: true
-  no-multiple-blanks: true
-  commands-show-output: true
+  heading-increment: true
 
 ignores:
   - "docs/snippets/**"

docs/administration/configuration/configuration.md

@@ -7,13 +7,13 @@ description: In Ibexa DXP you store and manage configuration in project files, t
 [[= product_name =]] configuration is delivered by means of a number of dedicated configuration files.
 It contains everything from selecting the content repository to SiteAccesses to language settings.
 
-### Configuration format
+## Configuration format
 
 The recommended configuration format is YAML.
 It's used by default in the kernel (and in examples throughout the documentation).
 However, you can also use XML or PHP formats for configuration.
 
-### Configuration files
+## Configuration files
 
 Configuration files are located in the `config` folder.
 Configuration is provided per package in the `config/packages` folder, and routes are defined per package in `config/routes`.
@@ -43,7 +43,7 @@ These files contain additional settings and point to the general (not environmen
 
     Be careful when copy-pasting text from a word processing software or a PDF, because it might contain hidden characters like the [soft hyphen](https://en.wikipedia.org/wiki/Soft_hyphen).
 
-### Configuration handling
+## Configuration handling
 
 !!! note
 

docs/administration/content_organization/sections.md

@@ -35,7 +35,7 @@ Other references to the section remain and thus the system most likely loses con
 Section ID numbers aren't recycled.
 If a section is removed, its ID number cannot be reused when a new section is created.
 
-### Registering users
+## Registering users
 
 Registration form for your website is placed under this address: <yourdomain>/register.
 By default, new users created in this way are placed in the Guest accounts group.

docs/commerce/order_management/order_management.md

@@ -15,6 +15,6 @@ The component exposes the following:
 - [PHP API](order_management_api.md) that allows for managing orders
 - [REST API](/api/rest_api/rest_api_reference/rest_api_reference.html#tag/Orders) that helps get order information over HTTP
 
-### Order management service
+## Order management service
 
 The Order Management package provides the `Ibexa\Contracts\OrderManagement\OrderServiceInterface` service, which is the entrypoint for calling the [backend API](order_management_api.md).

docs/commerce/payment/payment.md

@@ -21,7 +21,7 @@ The component exposes the following APIs:
 - [Payment method REST API](/api/rest_api/rest_api_reference/rest_api_reference.html#tag/Payments) that helps manage payment methods over HTTP
 - [Payment PHP API](payment_api.md) that allows for managing payments
 
-### Services
+## Services
 
 The Payment package provides the following services, which are entry points for calling backend APIs:
 

docs/commerce/shipping_management/shipping_management.md

@@ -19,7 +19,7 @@ The component exposes the following:
 - [Shipping method PHP API](shipping_method_api.md) that allows for managing shipping methods
 - [Shipment PHP API](shipment_api.md) that allows for managing shipments
 
-### Services
+## Services
 
 The Shipping package provides the following services, which are entry points for calling backend APIs:
 

docs/content_management/content_model.md

@@ -22,7 +22,7 @@ A content item consists of:
 - [Fields](#fields), defined by the [content type](content_types.md).
 The fields can cover data ranging from single variables and text lines to media files or blocks of formatted text.
 
-#### Content information
+### Content information
 
 General information about a content item is stored in a [`ContentInfo`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-ContentInfo.html) object.
 `ContentInfo` doesn't include fields. It contains following information:

docs/content_management/field_types/field_type_reference/authorfield.md

@@ -10,7 +10,7 @@ This field type allows the storage and retrieval of one or more authors. For eac
 
 ### Value object
 
-##### Properties
+#### Properties
 
 | Attribute | Type                                     | Description      | Example   |
 |-----------|------------------------------------------|------------------|-----------|
@@ -33,7 +33,7 @@ $authorList = Author\Value([
 ]);
 ```
 
-### Hash format
+#### Hash format
 
 The hash format mostly matches the value object. It has the following key `authors`.
 
@@ -54,7 +54,7 @@ Example
 ]
 ```
 
-##### String representation
+#### String representation
 
 The string contains all the authors with their names and emails.
 

docs/content_management/field_types/field_type_reference/checkboxfield.md

@@ -10,7 +10,7 @@ The Checkbox field type stores the current status for a checkbox input, checked
 
 ### Value object
 
-##### Properties
+#### Properties
 
 The Value class of this field type contains the following properties:
 

docs/content_management/field_types/field_type_reference/countryfield.md

@@ -58,7 +58,7 @@ The format used by the toHash method is the Alpha2 value, however the input is c
 
 ### Value object
 
-##### Properties
+#### Properties
 
 The Value class of this field type contains the following properties: