From 1da5cf0ace30d89edf05833b91ce80467c7864bd Mon Sep 17 00:00:00 2001
From: Uiolee <22849383+uiolee@users.noreply.github.com>
Date: Wed, 27 Mar 2024 03:17:23 +0800
Subject: [PATCH] docs: add link to engines section (#7198)

---
 docs/lib/content/configuring-npm/package-json.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/lib/content/configuring-npm/package-json.md b/docs/lib/content/configuring-npm/package-json.md
index 111d13445044f..51c516d5f37e8 100644
--- a/docs/lib/content/configuring-npm/package-json.md
+++ b/docs/lib/content/configuring-npm/package-json.md
@@ -40,7 +40,7 @@ Some tips:
 * Don't use the same name as a core Node module.
 * Don't put "js" or "node" in the name.  It's assumed that it's js, since
   you're writing a package.json file, and you can specify the engine using
-  the "engines" field.  (See below.)
+  the "[engines](#engines)" field.  (See below.)
 * The name will probably be passed as an argument to require(), so it
   should be something short, but also reasonably descriptive.
 * You may want to check the npm registry to see if there's something by