summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/cli-commands/npm-completion.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/cli-commands/npm-completion.md')
-rw-r--r--[-rwxr-xr-x]deps/npm/docs/content/cli-commands/npm-completion.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/deps/npm/docs/content/cli-commands/npm-completion.md b/deps/npm/docs/content/cli-commands/npm-completion.md
index 2331f97581..59bfca503e 100755..100644
--- a/deps/npm/docs/content/cli-commands/npm-completion.md
+++ b/deps/npm/docs/content/cli-commands/npm-completion.md
@@ -1,10 +1,10 @@
---
-section: cli-commands
+section: cli-commands
title: npm-completion
description: Tab Completion for npm
---
-# npm-completion
+# npm-completion(1)
## Tab Completion for npm
@@ -28,8 +28,8 @@ npm completion >> ~/.zshrc
```
You may of course also pipe the output of `npm completion` to a file
-such as `/usr/local/etc/bash_completion.d/npm` or
-`/etc/bash_completion.d/npm` if you have a system that will read
+such as `/usr/local/etc/bash_completion.d/npm` or
+`/etc/bash_completion.d/npm` if you have a system that will read
that file for you.
When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the