Skip to content

Commit

Permalink
docs: fix typo in file-specifiers and package-lock (#16)
Browse files Browse the repository at this point in the history
+ specifer => specifiers
+ relavent => relevant
+ properities => properties

PR-URL: #16
Credit: @watilde
Reviewed-By: @zkat
  • Loading branch information
watilde authored and zkat committed Jul 18, 2018
1 parent ca03013 commit 4f39f79
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion doc/spec/file-specifiers.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion doc/spec/package-lock.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 4f39f79

Please sign in to comment.