docs: update commit-ish default branch (#5205)

* docs: update commit-ish default branch To match with https://github.com/npm/cli/blob/latest/docs/content/using-npm/developers.md#what-is-a-package
npm · Jul 21, 2022 · f9abee7 · f9abee7
1 parent 9905d0e
commit f9abee7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/content/commands/npm-install.md b/docs/content/commands/npm-install.md
@@ -311,7 +311,7 @@ into a tarball (b).
     can be any valid semver range or exact version, and npm will look for
     any tags or refs matching that range in the remote repository, much as
     it would for a registry dependency. If neither `#<commit-ish>` or
-    `#semver:<semver>` is specified, then `master` is used.
+    `#semver:<semver>` is specified, then the default branch is used.
 
     As with regular git dependencies, `dependencies` and `devDependencies`
     will be installed if the package has a `prepare` script before the

diff --git a/docs/content/configuring-npm/package-json.md b/docs/content/configuring-npm/package-json.md
@@ -632,7 +632,7 @@ commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can
 be any valid semver range or exact version, and npm will look for any tags
 or refs matching that range in the remote repository, much as it would for
 a registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is
-specified, then `master` is used.
+specified, then the default branch is used.
 
 Examples: