Fix various markdown linting errors

Signed-off-by: George Steel <george@net-glue.co.uk>
laminas · Nov 21, 2024 · 2b511f1 · 2b511f1
1 parent d5f6f5f
commit 2b511f1
Show file tree

Hide file tree

Showing 8 changed files with 17 additions and 17 deletions.
diff --git a/docs/book/v3/helpers/escape.md b/docs/book/v3/helpers/escape.md
@@ -14,7 +14,7 @@ More information to the operation and the background of security can be found
 in the
 [documentation of laminas-escaper](https://docs.laminas.dev/laminas-escaper/configuration/).
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### Installation Requirements
 >
 > The escape helpers depends on the laminas-escaper component, so be sure to have

diff --git a/docs/book/v3/helpers/head-meta.md b/docs/book/v3/helpers/head-meta.md
@@ -31,7 +31,7 @@ whether or not to autoescape values used in meta tags:
 
 - `setAutoEscape(bool $autoEscape = true)` (enabled by default)
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### AutoEscape
 >
 > **Disable this flag at your own risk.** The one documented case where it is

diff --git a/docs/book/v3/helpers/head-script.md b/docs/book/v3/helpers/head-script.md
@@ -20,7 +20,7 @@ script to load; this is usually in the form of a URL or a path. For the
 `*Script()` methods, `$script` is the client-side scripting directives you wish
 to use in the element.
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### Setting Conditional Comments
 >
 > `HeadScript` allows you to wrap the script tag in conditional comments, which

diff --git a/docs/book/v3/helpers/head-style.md b/docs/book/v3/helpers/head-style.md
@@ -3,7 +3,7 @@
 The HTML `<style>` element is used to include CSS stylesheets inline in the HTML
 `<head>` element.
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### Use HeadLink to link CSS files
 >
 > [HeadLink](head-link.md) should be used to create `<link>` elements for

diff --git a/docs/book/v3/helpers/inline-script.md b/docs/book/v3/helpers/inline-script.md
@@ -6,7 +6,7 @@ code. The `InlineScript` helper allows you to manage both. It is derived from
 [HeadScript](head-script.md), and any method of that helper is available;
 replace the usage of `headScript()` in those examples with `inlineScript()`.
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### Use InlineScript for HTML body scripts
 >
 > `InlineScript` should be used when you wish to include scripts inline in the

diff --git a/docs/book/v3/helpers/intro.md b/docs/book/v3/helpers/intro.md
@@ -11,7 +11,7 @@ used to retrieve that instance.  `Laminas\View\Renderer\PhpRenderer` composes a
 *plugin manager*, allowing you to retrieve helpers, and also provides some
 method overloading capabilities that allow proxying method calls to helpers.
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### Callable Helpers
 >
 > Starting in version 2.7.0, if your helper does not need access to the view,

diff --git a/docs/book/v3/helpers/partial.md b/docs/book/v3/helpers/partial.md
@@ -7,7 +7,7 @@ you do not need to worry about variable name clashes.
 A sibling to the `Partial`, the `PartialLoop` view helper allows you to pass
 iterable data, and render a partial for each item.
 
-<!-- markdownlint-disable-next-line header-increment -->
+<!-- markdownlint-disable-next-line heading-increment -->
 > ### PartialLoop Counter
 >
 > The `PartialLoop` view helper gives access to the current position of the

diff --git a/docs/book/v3/helpers/placeholder.md b/docs/book/v3/helpers/placeholder.md
@@ -90,16 +90,16 @@ easiest to template; the `Placeholder` view helper allows you to capture
 arbitrary content for later rendering using the following API.
 
 - `captureStart($type, $key)` begins capturing content.
-  - `$type` should be one of the `Placeholder` constants `APPEND` or `SET`. If
-    `APPEND`, captured content is appended to the list of current content in the
-    placeholder; if `SET`, captured content is used as the sole value of the
-    placeholder (potentially replacing any previous content). By default,
-    `$type` is `APPEND`.
-  - `$key` can be used to specify a specific key in the placeholder container to
-    which you want content captured.
-  - `captureStart()` locks capturing until `captureEnd()` is called; you cannot
-    nest capturing with the same placeholder container. Doing so will raise an
-    exception.
+    - `$type` should be one of the `Placeholder` constants `APPEND` or `SET`. If
+      `APPEND`, captured content is appended to the list of current content in the
+      placeholder; if `SET`, captured content is used as the sole value of the
+      placeholder (potentially replacing any previous content). By default,
+      `$type` is `APPEND`.
+    - `$key` can be used to specify a specific key in the placeholder container to
+      which you want content captured.
+    - `captureStart()` locks capturing until `captureEnd()` is called; you cannot
+      nest capturing with the same placeholder container. Doing so will raise an
+      exception.
 - `captureEnd()` stops capturing content, and places it in the container object
   according to how `captureStart()` was called.