From f1af61f917e58a0a45d2b15d1e5600988b2c824f Mon Sep 17 00:00:00 2001 From: Maksim Koryukov Date: Tue, 21 Jan 2025 14:24:40 -0400 Subject: [PATCH] docs: fix typos in "package-json" (#8041) This PR fixes small typos in the documentation for "configuring npm/package-json" --- docs/lib/content/configuring-npm/package-json.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/lib/content/configuring-npm/package-json.md b/docs/lib/content/configuring-npm/package-json.md index 06af27f9b2f3e..a92e5a2183b4c 100644 --- a/docs/lib/content/configuring-npm/package-json.md +++ b/docs/lib/content/configuring-npm/package-json.md @@ -121,7 +121,7 @@ SPDX license identifier for the license you're using, like this: ``` You can check [the full list of SPDX license -IDs](https://spdx.org/licenses/). Ideally you should pick one that is +IDs](https://spdx.org/licenses/). Ideally, you should pick one that is [OSI](https://opensource.org/licenses/) approved. If your package is licensed under multiple common licenses, use an [SPDX @@ -623,7 +623,7 @@ See [semver](https://github.com/npm/node-semver#versions) for more details about * `tag` A specific version tagged and published as `tag` See [`npm dist-tag`](/commands/npm-dist-tag) * `path/path/path` See [Local Paths](#local-paths) below -* `npm:@scope/pkg@version` Custom alias for a pacakge See [`package-spec`](/using-npm/package-spec#aliases) +* `npm:@scope/pkg@version` Custom alias for a package See [`package-spec`](/using-npm/package-spec#aliases) For example, these are all valid: