From 0f02cfe4dfd63ea65ff126b2f0e660c9464410b9 Mon Sep 17 00:00:00 2001 From: mdn-bot <108879845+mdn-bot@users.noreply.github.com> Date: Wed, 26 Jul 2023 00:30:49 +0000 Subject: [PATCH] chore: auto-fix Markdownlint issues --- CONTRIBUTING.md | 2 +- .../server-side/express_nodejs/forms/create_genre_form/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index edbc6b53478b3f8..95ba16c0ae0a053 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -223,7 +223,7 @@ To ensure that all MDN documents follow the same formatting, we use both [Pretti If you have a [local checkout](#forking-and-cloning-the-repository) of the repository and have [installed the dependencies](#preparing-the-project), or you are using [github.dev](https://github.dev), a pre-commit hook will be installed which automatically runs while making a commit. To save some headache and improve your work flow while authoring, you may wish to [configure your editor to automatically run Prettier](https://prettier.io/docs/en/editors.html). Alternatively, you may run `yarn fix:md` in the command line to manually format all Markdown files. -> **Note:** Automatically formatting changes does not work for pull requests opened using the GitHub Web UI as described in the ["Simple changes" section](#simple-changes). This may result in failed status checks on pull requests. If you're not sure about how to fix this, [get in touch with us](https://developer.mozilla.org/en-US/docs/MDN/Community/Communication_channels) for help. +> **Note:** Automatically formatting changes does not work for pull requests opened using the GitHub Web UI as described in the ["Simple changes" section](#simple-changes). This may result in failed status checks on pull requests. If you're not sure about how to fix this, [get in touch with us](/en-US/docs/MDN/Community/Communication_channels) for help. ### Adding a new document diff --git a/files/en-us/learn/server-side/express_nodejs/forms/create_genre_form/index.md b/files/en-us/learn/server-side/express_nodejs/forms/create_genre_form/index.md index 2e92113039107b0..00170f1e0079b31 100644 --- a/files/en-us/learn/server-side/express_nodejs/forms/create_genre_form/index.md +++ b/files/en-us/learn/server-side/express_nodejs/forms/create_genre_form/index.md @@ -130,7 +130,7 @@ asyncHandler(async (req, res, next) => { ``` If the genre name data is valid then we perform a case-insensitive search to see if a `Genre` with the same name already exists (as we don't want to create duplicate or near duplicate records that vary only in letter case, such as: "Fantasy", "fantasy", "FaNtAsY", and so on). -To ignore letter case and accents when searching we chain the [`collation()`](https://mongoosejs.com/docs/api/query.html#Query.prototype.collation()) method, specifying the locale of 'en' and strength of 2 (for more information see the MongoDb [Collation](https://www.mongodb.com/docs/manual/reference/collation/) topic). +To ignore letter case and accents when searching we chain the [`collation()`]() method, specifying the locale of 'en' and strength of 2 (for more information see the MongoDb [Collation](https://www.mongodb.com/docs/manual/reference/collation/) topic). If a `Genre` with a matching name already exists we redirect to its detail page. If not, we save the new `Genre` and redirect to its detail page.