summaryrefslogtreecommitdiff
path: root/docs/getting_started/command_line_interface.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/getting_started/command_line_interface.md')
-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`.