docs: fix broken link of new comments path (vercel#71674)

# Summary
Add missing comments path to which vercel#61416 changed.

### Improving Documentation

- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

Co-authored-by: JJ Kasper <jj@jjsweb.site>

Author: マルコメ

contributing/repository/triaging.md

@@ -14,7 +14,7 @@ Issues are opened with one of these labels:
 
 ### Automated triaging
 
-In case of a bug report, **if the reproduction is missing or insufficient, the issue is automatically closed**, and a comment is added with a correct course of action. The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/invalid-link.md). We also add an `invalid link` label to mark the issue. To avoid your issue being closed, please follow the [bug report template](https://github.com/vercel/next.js/blob/canary/.github/ISSUE_TEMPLATE/1.bug_report.yml) carefully.
+In case of a bug report, **if the reproduction is missing or insufficient, the issue is automatically closed**, and a comment is added with a correct course of action. The issue will receive [this comment](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-link.md). We also add an `invalid link` label to mark the issue. To avoid your issue being closed, please follow the [bug report template](https://github.com/vercel/next.js/blob/canary/.github/ISSUE_TEMPLATE/1.bug_report.yml) carefully.
 
 If you fill out the "Which area(s) are affected? (Select all that apply)" section of the bug report template, we will add the corresponding [label(s)](https://github.com/vercel/next.js/labels).
 

errors/opening-an-issue.mdx

@@ -29,6 +29,6 @@ And go through the prepared reproduction steps once again, and check if the issu
 - [Video: How to Contribute to Open Source (Next.js)](https://www.youtube.com/watch?v=cuoNzXFLitc)
 - [Contributing to Next.js](https://github.com/vercel/next.js/blob/canary/contributing.md)
 - [Triaging issues](https://github.com/vercel/next.js/blob/canary/contributing/repository/triaging.md)
-- [Verifying canary](https://github.com/vercel/next.js/blob/canary/.github/verify-canary.md)
-- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/invalid-reproduction.md)
-- [Simplifying a reproduction](https://github.com/vercel/next.js/blob/canary/.github/simplify-reproduction.md)
+- [Verifying canary](https://github.com/vercel/next.js/blob/canary/.github/comments/verify-canary.md)
+- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-reproduction.md)
+- [Simplifying a reproduction](https://github.com/vercel/next.js/blob/canary/.github/comments/simplify-reproduction.md)

errors/version-staleness.mdx

@@ -58,6 +58,6 @@ If you want to report a bug on GitHub, you should upgrade to the newest canary r
 - [Video: How to Contribute to Open Source (Next.js)](https://www.youtube.com/watch?v=cuoNzXFLitc)
 - [Contributing to Next.js](https://github.com/vercel/next.js/blob/canary/contributing.md)
 - [Triaging issues](https://github.com/vercel/next.js/blob/canary/contributing/repository/triaging.md)
-- [Verifying canary](https://github.com/vercel/next.js/blob/canary/.github/verify-canary.md)
-- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/invalid-reproduction.md)
-- [Simplifying a reproduction](https://github.com/vercel/next.js/blob/canary/.github/simplify-reproduction.md)
+- [Verifying canary](https://github.com/vercel/next.js/blob/canary/.github/comments/verify-canary.md)
+- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/comments/invalid-reproduction.md)
+- [Simplifying a reproduction](https://github.com/vercel/next.js/blob/canary/.github/comments/simplify-reproduction.md)