lint markdown

Author: guimachiavelli

.markdownlint.jsonc

@@ -1,12 +1,12 @@
 {
+  "MD001": true, // heading-increment/header-increment Heading levels should only increment by one level at a time
   "MD013": false, // line-length Line length [Expected: 80; Actual: 119]
-  "MD001": false, // heading-increment/header-increment Heading levels should only increment by one level at a time
-  "MD026": {"punctuation": ".,;:。，；"}, // no-trailing-punctuation Trailing punctuation in headings except ? and ! 
   "MD014": false, // commands-show-output Dollar signs used before commands without showing output
   "MD024": false, // no-duplicate-heading/no-duplicate-header
   "MD025": {"front_matter_title": "(?!.*)"}, // single-title/single-h1 Accept both h1 and front matter titles
-  "MD040": false, // fenced-code-language Fenced code blocks should have a language specified
   "MD033": false, // no-inline-html Inline HTML
+  "MD034": false, // allow bare URLs
+  "MD040": false, // fenced-code-language Fenced code blocks should have a language specified
   "MD049": { "style": "underscore" }, // enforce use of underscore for em/italics
   "MD050": { "style": "asterisk" }, // enforce use of asterisk for strong/bold
   "MD051": false

.markdownlintignore

@@ -1,4 +1,5 @@
 node_modules
-.vuepress
-public
+scripts
+snippets
+assets
 README.md

.vale/styles/Vocab/word_list/accept.txt

@@ -111,4 +111,5 @@ masterKey
 GCP
 Boolean
 GET
-POST
+POST
+Mintlify

guides/ai/mcp.mdx

@@ -76,7 +76,6 @@ Can you check the connection to my Meilisearch instance and tell me what version
 
 Claude will use the `get-version` and `health-check` tools to verify the connection and provide information about your instance.
 
-
 ## Create an e-commerce index
 
 Now you have configured the MCP to work with Meilisearch, you can use it to manage your indexes.
@@ -157,7 +156,7 @@ Search the "products" index for "chair" where the price is less than 200 and the
 
 ### Important note about LLM limitation
 
-Large Language Models like Claude tend to say "yes" to most requests, even if they can't actually perform them. 
+Large Language Models like Claude tend to say "yes" to most requests, even if they can't actually perform them.
 
 Claude can only perform actions that are exposed through the Meilisearch API and implemented in the MCP server. If you're unsure whether a particular operation is possible, refer to the [Meilisearch documentation](https://docs.meilisearch.com) and the [MCP server README](https://github.com/meilisearch/meilisearch-mcp).
 </Warning>
@@ -197,4 +196,4 @@ npx @modelcontextprotocol/inspector uvx -n meilisearch-mcp
 
 The Meilisearch MCP integration with Claude can transform multiple API calls and configuration tasks into conversational requests. This can help you focus more on building your application and less on implementation details.
 
-For more information about advanced configurations and capabilities, refer to the [Meilisearch documentation](https://docs.meilisearch.com) and the [Meilisearch MCP server repository](https://github.com/meilisearch/meilisearch-mcp).
+For more information about advanced configurations and capabilities, refer to the [Meilisearch documentation](https://docs.meilisearch.com) and the [Meilisearch MCP server repository](https://github.com/meilisearch/meilisearch-mcp).

guides/deployment/aws.mdx

@@ -112,7 +112,7 @@ If you have an existing Key Pair, you can use that. Otherwise, select the option
 
 Once you've downloaded your key pair (and only then), click on "Launch Instances", then on "View Instances".
 
-### 9. Enjoy your Meilisearch instance running on AWS!
+### 9. Enjoy your Meilisearch instance running on AWS
 
 Your instance may take a minute or two to get up and running (see the "Instance state" column).
 

guides/embedders/cohere.mdx

@@ -20,6 +20,7 @@ To follow this guide, you'll need:
 To set up an embedder in Meilisearch, you need to configure it to your settings. You can refer to the [Meilisearch documentation](/reference/api/settings) for more details on updating the embedder settings.
 
 Cohere offers multiple embedding models:
+
 - `embed-english-v3.0` and `embed-multilingual-v3.0`: 1024 dimensions
 - `embed-english-light-v3.0` and `embed-multilingual-light-v3.0`: 384 dimensions
 

guides/front_end/front_end_integration.mdx

@@ -7,8 +7,6 @@ In the [quick start tutorial](/learn/self_hosted/getting_started_with_self_hoste
 
 Using [`instant-meilisearch`](https://github.com/meilisearch/instant-meilisearch) is the easiest way to build a front-end interface for search. `instant-meilisearch` is a plugin that establishes communication between a Meilisearch instance and [InstantSearch](https://github.com/algolia/instantsearch.js). InstantSearch, an open-source project developed by Algolia, renders all the components needed to start searching.
 
-## Let's try it!
-
 1. Create an empty file and name it `index.html`
 2. Open it in a text editor like Notepad, Sublime Text, or Visual Studio Code
 3. Copy-paste one the code sample below

guides/front_end/vue_quick_start.mdx

@@ -69,7 +69,7 @@ The `ais-instant-search` widget is the mandatory wrapper that allows you to conf
 
 ## 5. Add a search bar and list search results
 
-Add the `ais-search-box` and `ais-hits` widgets inside the `ais-instant-search` wrapper widget. 
+Add the `ais-search-box` and `ais-hits` widgets inside the `ais-instant-search` wrapper widget.
 
 Import the CSS library to style the search components.
 
@@ -79,11 +79,11 @@ Import the CSS library to style the search components.
   <ais-search-box />
     <ais-hits>
       <template v-slot:item="{ item }">
-	  <div>
-	    <img :src="item.image" align="left" :alt="item.name"/>
+   <div>
+     <img :src="item.image" align="left" :alt="item.name"/>
           <h2>{{ item.name }}</h2>
-	    <p> {{ item.description }}</p>
-	  </div>
+     <p> {{ item.description }}</p>
+   </div>
       </template>
     </ais-hits>
   </ais-instant-search>
@@ -93,7 +93,6 @@ Import the CSS library to style the search components.
 import { instantMeiliSearch } from "@meilisearch/instant-meilisearch";
 import "instantsearch.css/themes/satellite-min.css";
 
-
 export default {
 data() {
     return {

guides/improve_relevancy_large_documents.mdx

@@ -130,6 +130,6 @@ Users searching this dataset will now be able to find more relevant results acro
 
 ## Conclusion
 
-You have seen how to split large documents to improve search relevancy. You also saw how to configure a distinct attribute to prevent Meilisearch from returning duplicate results. 
+You have seen how to split large documents to improve search relevancy. You also saw how to configure a distinct attribute to prevent Meilisearch from returning duplicate results.
 
 Though this guide used JavaScript, you can replicate the process with any programming language you are comfortable using.

guides/laravel_multitenancy.mdx

@@ -8,6 +8,7 @@ This guide will walk you through implementing search in a multitenant Laravel ap
 ## Requirements
 
 This guide requires:
+
 - A Laravel 10 application with [Laravel Scout](https://laravel.com/docs/10.x/scout) configured to use the `meilisearch` driver
 - A Meilisearch server running — see our [quick start](/learn/getting_started/cloud_quick_start)
 - A search API key — available in your Meilisearch dashboard
@@ -22,6 +23,7 @@ Prefer self-hosting? Read our [installation guide](/learn/self_hosted/install_me
 Our example CRM is a multitenant application, where each user can only access data belonging to their organization.
 
 On a technical level, this means:
+
 - A `User` model that belongs to an `Organization`
 - A `Contact` model that belongs to an `Organization` (can only be accessed by users from the same organization)
 - An `Organization` model that has many `User`s and many `Contact`s