Merge #382

382: Fix anchor inside contributing guidelines r=bidoubiwa a=mdubus



Co-authored-by: Morgane Dubus <[email protected]>

Author: bors[bot]

CONTRIBUTING.md

@@ -19,7 +19,7 @@ First of all, thank you for contributing to MeiliSearch! The goal of this docume
 1. Make sure that the contribution you want to make is explained or detailed in a GitHub issue! Find an [existing issue](https://github.com/meilisearch/docs-searchbar.js/issues/) or [open a new one](https://github.com/meilisearch/docs-searchbar.js/issues/new).
 2. Once done, [fork the docs-searchbar.js repository](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) in your own GitHub account. Ask a maintainer if you want your issue to be checked before making a PR.
 3. [Create a new Git branch](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).
-4. Review the [Development Workflow](#workflow) section that describes the steps to maintain the repository.
+4. Review the [Development Workflow](#development-workflow) section that describes the steps to maintain the repository.
 5. Make the changes on your branch.
 6. [Submit the branch as a PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) pointing to the `main` branch of the main docs-searchbar.js repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br>
    We do not enforce a naming convention for the PRs, but **please use something descriptive of your changes**, having in mind that the title of your PR will be automatically added to the next [release changelog](https://github.com/meilisearch/docs-searchbar.js/releases/).