From e8f785b25ef116137f88c64598a40f40eaa3e8e4 Mon Sep 17 00:00:00 2001
From: Francis Charette Migneault <francis.charette.migneault@gmail.com>
Date: Wed, 6 Nov 2024 14:17:08 -0500
Subject: [PATCH] patch markdown linting of special header

---
 README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/README.md b/README.md
index 776268b..32689fa 100644
--- a/README.md
+++ b/README.md
@@ -136,6 +136,10 @@ The fields in the table below can be used in these parts of STAC documents:
 | mlm:output <sup>[\[1\]][1]</sup>          | \[[Model Output Object](#model-output-object)]                | **REQUIRED** Describes each model output and how to interpret it.                                                                                                                                                                                                                           |
 | mlm:hyperparameters <sup>[\[1\]][1]</sup> | [Model Hyperparameters Object](#model-hyperparameters-object) | Additional hyperparameters relevant for the model.                                                                                                                                                                                                                                          |
 
+<!-- different headings and intends are done on purpose to correctly render and redirect on GitHub -->
+<!-- lint disable missing-heading -->
+<!-- lint disable heading-increment -->
+
 [1]: #1-allowed-only-in-item-properties
 
 ##### <sup>[1]</sup> Allowed Only in Item `properties`
@@ -152,6 +156,9 @@ The fields in the table below can be used in these parts of STAC documents:
 > did not override it for their respective reference. For some of the fields, further details are provided in following
 > sections to provide more precisions regarding some potentially ambiguous use cases.
 
+<!-- lint enable missing-heading -->
+<!-- lint enable no-undefined-references -->
+
 In addition, fields from the multiple relevant extensions should be defined as applicable. See
 [Best Practices - Recommended Extensions to Compose with the ML Model Extension](best-practices.md#recommended-extensions-to-compose-with-the-ml-model-extension)
 for more details.