diff --git a/docs/lib/content/configuring-npm/package-lock-json.md b/docs/lib/content/configuring-npm/package-lock-json.md
index 37dc59f3260aa..d540dd0e7228b 100644
--- a/docs/lib/content/configuring-npm/package-lock-json.md
+++ b/docs/lib/content/configuring-npm/package-lock-json.md
@@ -36,7 +36,7 @@ various purposes:
 Both of these files have the same format, and perform similar functions in
 the root of a project.
 
-The difference is that `package-lock.json` cannot be published, and it will 
+The difference is that `package-lock.json` cannot be published, and it will
 be ignored if found in any place other than the root project.
 
 In contrast, [npm-shrinkwrap.json](/configuring-npm/npm-shrinkwrap-json) allows
@@ -114,7 +114,7 @@ the npm registry.  Lockfiles generated by npm v7 will contain
 * `1`: The lockfile version used by npm v5 and v6.
 * `2`: The lockfile version used by npm v7 and v8. Backwards compatible to v1
   lockfiles.
-* `3`: The lockfile version used by npm v9. Backwards compatible to npm v7.
+* `3`: The lockfile version used by npm v9 and above. Backwards compatible to npm v7.
 
 npm will always attempt to get whatever data it can out of a lockfile, even
 if it is not a version that it was designed to support.