doc: fix links in some intra-repository docs · nodejs/node@af18632
@@ -8,7 +8,7 @@
88- [Internal vs. Public API](#internal-vs-public-api)
99- [Breaking Changes](#breaking-changes)
1010- [Deprecations](#deprecations)
11-- [Involving the TSC](#involving-the-TSC)
11+- [Involving the TSC](#involving-the-tsc)
1212* [Landing Pull Requests](#landing-pull-requests)
1313- [Technical HOWTO](#technical-howto)
1414- [I Just Made a Mistake](#i-just-made-a-mistake)
@@ -361,7 +361,7 @@ The TSC should serve as the final arbiter where required.
361361362362## Landing Pull Requests
363363364-* Please never use GitHub's green ["Merge Pull Request"](https://help.github.com/articles/merging-a-pull-request/#merging-a-pull-request-using-the-github-web-interface) button.
364+* Please never use GitHub's green ["Merge Pull Request"](https://help.github.com/articles/merging-a-pull-request/#merging-a-pull-request-on-github) button.
365365* If you do, please force-push removing the merge.
366366* Reasons for not using the web interface button:
367367* The merge method will add an unnecessary merge commit.
@@ -388,8 +388,8 @@ information regarding the change process:
388388- Useful for @mentions / contact list if something goes wrong in the PR.
389389- Protects against the assumption that GitHub will be around forever.
390390391-Review the commit message to ensure that it adheres to the guidelines
392-outlined in the [contributing](./CONTRIBUTING.md#step-3-commit) guide.
391+Review the commit message to ensure that it adheres to the guidelines outlined
392+in the [contributing](./CONTRIBUTING.md#commit-message-guidelines) guide.
393393394394See the commit log for examples such as
395395[this one](https://github.com/nodejs/node/commit/b636ba8186) if unsure
@@ -514,7 +514,7 @@ commit message for that commit. This is a good moment to fix incorrect
514514commit logs, ensure that they are properly formatted, and add
515515`Reviewed-By` lines.
516516* The commit message text must conform to the
517-[commit message guidelines](./CONTRIBUTING.md#step-3-commit).
517+[commit message guidelines](./CONTRIBUTING.md#commit-message-guidelines).
518518519519Run tests (`make -j4 test` or `vcbuild test`). Even though there was a
520520successful continuous integration run, other changes may have landed on master
@@ -588,7 +588,8 @@ commit final.
588588Long Term Support (often referred to as *LTS*) guarantees application developers
589589a 30 month support cycle with specific versions of Node.js.
590590591-You can find more information [in the full LTS plan](https://github.com/nodejs/lts#lts-plan).
591+You can find more information
592+[in the full release plan](https://github.com/nodejs/Release#release-plan).
592593593594#### How does LTS work?
594595@@ -668,5 +669,5 @@ release. This process of making a release will be a collaboration between the
668669LTS working group and the Release team.
669670670671[backporting guide]: doc/guides/backporting-to-release-lines.md
671-[Stability Index]: https://github.com/nodejs/node/pull/doc/api/documentation.md#stability-index
672+[Stability Index]: doc/api/documentation.md#stability-index
672673[Enhancement Proposal]: https://github.com/nodejs/node-eps