From 7d8e5b99c4ef8c394cffa7fc845f54a25ff37e3a Mon Sep 17 00:00:00 2001
From: John Kennedy <john.kennedy.9147@gmail.com>
Date: Sat, 1 Feb 2020 15:38:05 +0000
Subject: [PATCH] docs:correction to npm update -g behaviour

PR-URL: https://github.com/npm/cli/pull/755
Credit: @
Close: #755
Reviewed-by: @darcyclarke
---
 docs/content/cli-commands/npm-update.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/content/cli-commands/npm-update.md b/docs/content/cli-commands/npm-update.md
index b57bfe78c8faf..706d8acf208f9 100644
--- a/docs/content/cli-commands/npm-update.md
+++ b/docs/content/cli-commands/npm-update.md
@@ -122,7 +122,9 @@ version that satisfies `^0.4.0` (`>= 0.4.0 <0.5.0`)
 
 `npm update -g` will apply the `update` action to each globally installed
 package that is `outdated` -- that is, has a version that is different from
-`latest`.
+`wanted`.
+
+Note: Globally installed packages are treated as if they are installed with a caret semver range specified. So if you require to update to `latest` you may need to run `npm install -g [<pkg>...]`
 
 NOTE: If a package has been upgraded to a version newer than `latest`, it will
 be _downgraded_.