@@ -1631,10 +1631,10 @@ important ways: |
1631 | 1631 | 2. They cannot be closed ([`end()`][] will throw). |
1632 | 1632 | 3. They will never emit the [`'finish'`][] event. |
1633 | 1633 | 4. Writes may be synchronous depending on the what the stream is connected to |
1634 | | - and whether the system is Windows or Unix: |
1635 | | - - Files: *synchronous* on Windows and Linux |
1636 | | - - TTYs (Terminals): *asynchronous* on Windows, *synchronous* on Unix |
1637 | | - - Pipes (and sockets): *synchronous* on Windows, *asynchronous* on Unix |
| 1634 | + and whether the system is Windows or POSIX: |
| 1635 | + - Files: *synchronous* on Windows and POSIX |
| 1636 | + - TTYs (Terminals): *asynchronous* on Windows, *synchronous* on POSIX |
| 1637 | + - Pipes (and sockets): *synchronous* on Windows, *asynchronous* on POSIX |
1638 | 1638 |
|
1639 | 1639 | These behaviors are partly for historical reasons, as changing them would |
1640 | 1640 | create backwards incompatibility, but they are also expected by some users. |
@@ -1817,7 +1817,7 @@ cases: |
1817 | 1817 | options were set, but the port number chosen was invalid or unavailable. |
1818 | 1818 | * `>128` **Signal Exits** - If Node.js receives a fatal signal such as |
1819 | 1819 | `SIGKILL` or `SIGHUP`, then its exit code will be `128` plus the |
1820 | | - value of the signal code. This is a standard Unix practice, since |
| 1820 | + value of the signal code. This is a standard POSIX practice, since |
1821 | 1821 | exit codes are defined to be 7-bit integers, and signal exits set |
1822 | 1822 | the high-order bit, and then contain the value of the signal code. |
1823 | 1823 |
|
|