From 4f39f79bcacef11bf2f98d09730bc94d0379789b Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 11:57:38 +0900 Subject: [PATCH] docs: fix typo in file-specifiers and package-lock (#16) + specifer => specifiers + relavent => relevant + properities => properties PR-URL: https://github.com/npm/cli/pull/16 Credit: @watilde Reviewed-By: @zkat --- doc/spec/file-specifiers.md | 2 +- doc/spec/package-lock.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/spec/file-specifiers.md b/doc/spec/file-specifiers.md index 8e9e73d4dfa61..de294045e7c90 100644 --- a/doc/spec/file-specifiers.md +++ b/doc/spec/file-specifiers.md @@ -134,7 +134,7 @@ example-package@1.0.0 /path/to/example-package +-- a -> file:../a ``` -Of note here: No version is included as the relavent detail is WHERE the +Of note here: No version is included as the relevant detail is WHERE the package came from, not what version happened to be in that path. ### Outdated diff --git a/doc/spec/package-lock.md b/doc/spec/package-lock.md index e1cc6941aee3e..9da5d8c03b45a 100644 --- a/doc/spec/package-lock.md +++ b/doc/spec/package-lock.md @@ -269,7 +269,7 @@ nothing requires it any more. ## Additional fields / Adding new fields Installers should ignore any field they aren't aware of. It's not an error -to have additional properities in the package-lock or lock file. +to have additional properties in the package-lock or lock file. Installers that want to add new fields should either have one added via RFC in the npm issue tracker and an accompanying documentation PR, or should prefix