Use allow/deny list in docs

Lucio Martinez · ruyadorno · commit 5837a4843ab1 · 2020-09-22T12:40:59.000-04:00
PR-URL: #1699 Credit: @luciomartinez Close: #1699 Reviewed-by: @ruyadorno
diff --git a/docs/content/configuring-npm/package-json.md b/docs/content/configuring-npm/package-json.md
@@ -825,16 +825,16 @@ module will run on:
 "os" : [ "darwin", "linux" ]
 ```
 
-You can also blacklist instead of whitelist operating systems,
-just prepend the blacklisted os with a '!':
+You can also block instead of allowing operating systems,
+just prepend the blocked os with a '!':
 
 ```json
 "os" : [ "!win32" ]
 ```
 
 The host operating system is determined by `process.platform`
 
-It is allowed to both blacklist, and whitelist, although there isn't any
+It is allowed to both block and allow an item, although there isn't any
 good reason to do this.
 
 ### cpu
@@ -846,7 +846,7 @@ you can specify which ones.
 "cpu" : [ "x64", "ia32" ]
 ```
 
-Like the `os` option, you can also blacklist architectures:
+Like the `os` option, you can also block architectures:
 
 ```json
 "cpu" : [ "!arm", "!mips" ]
diff --git a/docs/content/using-npm/developers.md b/docs/content/using-npm/developers.md
@@ -152,8 +152,8 @@ The following paths and files are never ignored, so adding them to
 If, given the structure of your project, you find `.npmignore` to be a
 maintenance headache, you might instead try populating the `files`
 property of `package.json`, which is an array of file or directory names
-that should be included in your package. Sometimes a whitelist is easier
-to manage than a blacklist.
+that should be included in your package. Sometimes manually picking
+which items to allow is easier to manage than building a block list.
 
 #### Testing whether your `.npmignore` or `files` config works
 
