summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKitson Kelly <me@kitsonkelly.com>2021-05-19 14:06:14 +1000
committerGitHub <noreply@github.com>2021-05-19 14:06:14 +1000
commit7cf674d4111b0c9e21f2dcba0dcfd8213573fa5f (patch)
tree1a00be7ca187cda8dcacac58ec4f58800ac444c3
parent7d79d86e55a3c287455c6c8652184d9bc46330e1 (diff)
docs: update getting started for clarity (#10694)
Co-authored-by: RobyCigar <69680330+RobyCigar@users.noreply.github.com>
-rw-r--r--docs/getting_started/command_line_interface.md8
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/getting_started/command_line_interface.md b/docs/getting_started/command_line_interface.md
index 617278579..191c1e756 100644
--- a/docs/getting_started/command_line_interface.md
+++ b/docs/getting_started/command_line_interface.md
@@ -73,11 +73,9 @@ Some see it as unconventional that:
However:
-1. This is the most logical way of distinguishing between runtime flags and
- script arguments.
-2. This is the most ergonomic way of distinguishing between runtime flags and
- script arguments.
-3. This is, in fact, the same behaviour as that of any other popular runtime.
+1. This is the most logical and ergonomic way of distinguishing between runtime
+ flags and script arguments.
+2. This is, in fact, the same behaviour as that of any other popular runtime.
- Try `node -c index.js` and `node index.js -c`. The first will only do a
syntax check on `index.js` as per Node's `-c` flag. The second will
_execute_ `index.js` with `-c` passed to `require("process").argv`.