docs: fix typo in file-specifiers and package-lock (#16)

+ specifer => specifiers + relavent => relevant + properities => properties PR-URL: #16 Credit: @watilde Reviewed-By: @zkat
npm · Jul 18, 2018 · 4f39f79 · 4f39f79
1 parent ca03013
commit 4f39f79
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/doc/spec/file-specifiers.md b/doc/spec/file-specifiers.md
@@ -134,7 +134,7 @@ [email protected] /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
@@ -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