diff --git a/doc/spec/file-specifiers.md b/doc/spec/file-specifiers.md
index 226f6d0136728..95029677f5f45 100644
--- a/doc/spec/file-specifiers.md
+++ b/doc/spec/file-specifiers.md
@@ -14,7 +14,7 @@ URLs and URL-like strings for other types.
   slashes on a file specifier will be removed, that is 'file://../foo/bar`
   references the same package as same as `file:../foo/bar`.  The latter is
   considered canonical.
-* Attempting to install a specifer that has a windows drive letter will
+* Attempting to install a specifier that has a windows drive letter will
   produce an error on non-Windows systems.
 * A valid `file:` specifier points is:
   * a valid package file. That is, a `.tar`, `.tar.gz` or `.tgz` containing
@@ -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