CLI documentation update from CI
CI User committed
Jul 8, 2021 at 02:26 UTC
0a1d2dac9b0868c91a092cc09cfd0db087736e9c
3 files changed
+5
-5
content/cli/v6/using-npm/scripts.md
+2
-2
@@ -260,8 +260,8 @@ Scripts are run by passing the line as a script argument to `sh`.
260
If the script exits with a code other than 0, then this will abort the
261
process.
262
263
-Note that these script files don't have to be Node.js or even
264
-JavaScript programs. They just have to be some kind of executable
263
+Note that these script files don't have to be nodejs or even
264
+javascript programs. They just have to be some kind of executable
265
file.
266
267
### Hook Scripts
content/cli/v7/using-npm/scripts.md
+2
-2
@@ -311,8 +311,8 @@ Scripts are run by passing the line as a script argument to `sh`.
311
If the script exits with a code other than 0, then this will abort the
312
process.
313
314
-Note that these script files don't have to be Node.js or even
315
-JavaScript programs. They just have to be some kind of executable
314
+Note that these script files don't have to be nodejs or even
315
+javascript programs. They just have to be some kind of executable
316
file.
317
318
### Best Practices
content/cli/v7/using-npm/workspaces.md
+1
-1
@@ -45,7 +45,7 @@ Workspaces are usually defined via the `workspaces` property of the
45
46
Given the above `package.json` example living at a current working
47
directory `.` that contains a folder named `workspace-a` that itself contains
48
-a `package.json` inside it, defining a Node.js package, e.g:
48
+a `package.json` inside it, defining a nodejs package, e.g:
49
50
```
51
.