3
3
<!-- introduced_in=v0.10.0-->
4
4
<!-- type=misc -->
5
5
6
- The goal of this documentation is to comprehensively explain the Node.js
6
+ The goal of this documentation is to explain the Node.js
7
7
API, both from a reference as well as a conceptual point of view. Each
8
8
section describes a built-in module or high-level concept.
9
9
@@ -30,7 +30,7 @@ stability. The Node.js API is still somewhat changing, and as it
30
30
matures, certain parts are more reliable than others. Some are so
31
31
proven, and so relied upon, that they are unlikely to ever change at
32
32
all. Others are brand new and experimental, or known to be hazardous
33
- and in the process of being redesigned.
33
+ and being redesigned.
34
34
35
35
The stability indices are as follows:
36
36
@@ -50,13 +50,13 @@ The stability indices are as follows:
50
50
> Stability: 2 - Stable. Compatibility with the npm ecosystem is a high
51
51
> priority.
52
52
53
- Caution must be used when making use of ` Experimental ` features, particularly
54
- within modules that may be used as dependencies (or dependencies of
53
+ Use caution when making use of ` Experimental ` features, particularly
54
+ within modules that are dependencies (or dependencies of
55
55
dependencies) within a Node.js application. End users may not be aware that
56
- experimental features are being used, and therefore may experience unexpected
56
+ experimental features are being used, and may experience unexpected
57
57
failures or behavior changes when API modifications occur. To help avoid such
58
58
surprises, ` Experimental ` features may require a command-line flag to
59
- explicitly enable them, or may cause a process warning to be emitted .
59
+ enable them, or may emit a process warning.
60
60
By default, such warnings are printed to [ ` stderr ` ] [ ] and may be handled by
61
61
attaching a listener to the [ ` 'warning' ` ] [ ] event.
62
62
@@ -76,7 +76,7 @@ wish to do programmatic things with the documentation.
76
76
77
77
System calls like open(2) and read(2) define the interface between user programs
78
78
and the underlying operating system. Node.js functions
79
- which simply wrap a syscall,
79
+ which wrap a syscall,
80
80
like [ ` fs.open() ` ] [ ] , will document that. The docs link to the corresponding man
81
81
pages (short for manual pages) which describe how the syscalls work.
82
82
0 commit comments