summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-unpublish.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-unpublish.1')
-rw-r--r--deps/npm/man/man1/npm-unpublish.16
1 files changed, 3 insertions, 3 deletions
diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1
index 8094933ab..d773cde02 100644
--- a/deps/npm/man/man1/npm-unpublish.1
+++ b/deps/npm/man/man1/npm-unpublish.1
@@ -1,4 +1,4 @@
-.TH "NPM\-UNPUBLISH" "1" "June 2015" "" ""
+.TH "NPM\-UNPUBLISH" "1" "August 2015" "" ""
.SH "NAME"
\fBnpm-unpublish\fR \- Remove a package from the registry
.SH SYNOPSIS
@@ -13,7 +13,7 @@ npm unpublish [@<scope>/]<name>[@<version>]
\fBIt is generally considered bad behavior to remove versions of a library
that others are depending on!\fR
.P
-Consider using the \fBdeprecate\fR command
+Consider using the \fBdeprecate\fP command
instead, if your intent is to encourage users to upgrade\.
.P
There is plenty of room on the registry\.
@@ -29,7 +29,7 @@ Even if a package version is unpublished, that specific name and
version combination can never be reused\. In order to publish the
package again, a new version number must be used\.
.P
-The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fR\|\.
+The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\.
.SH SEE ALSO
.RS 0
.IP \(bu 2