Skip to content

Commit 22c9153

Browse files
csmit195Chris
andauthored
docs: fix typo and grammar in README (#8985)
- Fixed spelling of "backronymic" (from "bacronymic"). - Improved sentence structure in the branding FAQ to be more concise. - Corrected "if the project was" to "if the project were" (subjunctive mood). - Removed redundant "in fact" and "to ever have been." --------- Co-authored-by: Chris <[email protected]>
1 parent 21c3f02 commit 22c9153

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,4 +50,4 @@ npm <command>
5050

5151
#### Is "npm" an acronym for "Node Package Manager"?
5252

53-
Contrary to popular belief, **`npm`** **is not** in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for **"npm is not an acronym"** (if the project was named "ninaa", then it would be an acronym). The precursor to **`npm`** was actually a bash utility named **"pm"**, which was the shortform name of **"pkgmakeinst"** - a bash function that installed various things on various platforms. If **`npm`** were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".
53+
Contrary to popular belief, **`npm`** **is not** an acronym for "Node Package Manager." It is a recursive backronymic abbreviation for **"npm is not an acronym"** (if the project were named "ninaa," then it would be an acronym). The precursor to **`npm`** was actually a bash utility named **"pm"**, which was the shortform name of **"pkgmakeinst"** - a bash function that installed various things on various platforms. If **`npm`** were ever considered an acronym, it would be as "node pm" or, potentially, "new pm".

0 commit comments

Comments
 (0)