fix: markdown lint

Signed-off-by: prisis <[email protected]>

Author: prisis

.github/CONTRIBUTING.md

@@ -40,7 +40,7 @@ This project is a code style guide of all basic back- and front end project used
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

README.md

@@ -21,8 +21,8 @@
         "postinstall": "is-ci || husky install",
         "lint:staged": "lint-staged --verbose",
         "lint:styles": "stylelint",
-        "lint:text": "textlint --config=./.textlintrc \"./packages/**/README.md\" ./README.md ./UPGRADE.md --parallel --experimental",
-        "lint:text:fix": "yarn run lint:text --fix",
+        "lint:text": "textlint \"./packages/**/README.md\" ./README.md ./UPGRADE.md --dry-run --parallel --experimental",
+        "lint:text:fix": "textlint \"./packages/**/README.md\" ./README.md ./UPGRADE.md --parallel --experimental --fix",
         "prettier": "prettier --config=.prettierrc.cjs --write '**/*.{js,jsx,cjs,tsx,ts,less,md,json}'",
         "sort-package-json": "sort-package-json packages/**/package.json",
         "test": "jest --config=./jest.config.cjs",

package.json

@@ -328,17 +328,17 @@ You can use the `corejs` option to enable the use of the core-js v3 polyfills:
 ## Optimizations
 
 - [`babel-plugin-annotate-pure-calls`](https://github.com/Andarist/babel-plugin-annotate-pure-calls): Injects for `#__PURE` annotations to enable tree-shaking
-- [`babel-plugin-dev-expressions`](https://github.com/4Catalyzer/babel-plugin-dev-expression): A mirror of Facebook's dev-expression Babel plugin. It reduces or eliminates development checks from production code
+- [`babel-plugin-dev-expressions`](https://github.com/4Catalyzer/babel-plugin-dev-expression): A mirror of Facebook’s dev-expression Babel plugin. It reduces or eliminates development checks from production code
 
 ### Development-only Expressions + Treeshaking
 
-`babel-plugin-annotate-pure-calls` + `babel-plugin-dev-expressions` work together to fully eliminate dead code (aka treeshake) development checks from your production code. Let's look at an example to see how it works.
+`babel-plugin-annotate-pure-calls` + `babel-plugin-dev-expressions` work together to fully eliminate dead code (aka treeshake) development checks from your production code. Let’s look at an example to see how it works.
 
 
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/babel-preset/README.md

@@ -97,7 +97,7 @@ Or when using [babel-preset-env](https://github.com/babel/babel/tree/master/expe
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/browserslist-config-anolilab/README.md

@@ -1,6 +1,6 @@
 # ESLint config
 
-This package provides Anolilab’s .eslintrc.cjs as an extensible shared config, with a range of useful plugins that are often too time-consuming to setup and provides an easy way to install just the plugins you need, based on your project’s dependencies.
+This package provides Anolilab’s .eslintrc.cjs as an extensible shared config, with a range of useful plugins that are often too time-consuming to setup and provides an   install  the plugins you need, based on your project’s dependencies.
 
 ---
 
@@ -297,7 +297,7 @@ Therefore, `@anolilab/eslint-config` also inherits the philosophy of ESLint. It
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/eslint-config/README.md

@@ -55,7 +55,7 @@ module.exports = {
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/prettier-config/README.md

@@ -128,8 +128,8 @@ Add `cz` to your `package.json scripts`
 
 Ensure that your CI configuration has the following environment variables set:
 
-- GITHUB_TOKEN: [A GitHub personal access token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)
-- NPM_TOKEN: [A npm personal access token](https://www.npmjs.com/settings)
+- GITHUB_TOKEN: [A GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
+- NPM_TOKEN: [A npm personal access token](https://www.npmjs.com/package/settings)
 
 You can test your config with a dry run:
 
@@ -252,7 +252,7 @@ jobs:
 
 ## Note on GitHub protected branches
 
-If you’re releasing a [GitHub protected branch](https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) you need to change the git committer to an owner/admin and allow repo admins to bypass the branch protection (make sure "include administrators" is disabled in the branch protection rules.)
+If you’re releasing a [GitHub protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) you need to change the git committer to an owner/admin and allow repo admins to bypass the branch protection (make sure "include administrators" is disabled in the branch protection rules.)
 
 If your repo is under an organisation, you can create a bot account and give it admin rights on the repo. If your repo is under a personal account, you have no choice to make the repo owner the commiter for the release.
 
@@ -263,7 +263,7 @@ Either way, you have to create a GitHub personal access token for the committer
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/semantic-release-preset/README.md

@@ -71,7 +71,7 @@ Add this command to your `package.json` scripts section
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

packages/stylelint-config/README.md

@@ -177,7 +177,7 @@ If you already have a `.textlintrc`, then you can extend the `.textlintrc`, with
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing