| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 3df001f commit 84859c4
10 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1003,7 +1003,7 @@ prints the current version of CoffeeScript per the module at the URL in | |||
| 1003 | 1003 | ||
| 1004 | 1004 | Sources that are in formats Node.js doesn’t understand can be converted into | |
| 1005 | 1005 | JavaScript using the [`load` hook][load hook]. Before that hook gets called, | |
| 1006 | - however, a [`resolve` hook][resolve hook] hook needs to tell Node.js not to | ||
| 1006 | + however, a [`resolve` hook][resolve hook] needs to tell Node.js not to | ||
| 1007 | 1007 | throw an error on unknown file types. | |
| 1008 | 1008 | ||
| 1009 | 1009 | This is less performant than transpiling source files before running | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1058,7 +1058,7 @@ Returns the value at the given percentile. | |||
| 1058 | 1058 | added: v17.4.0 | |
| 1059 | 1059 | --> | |
| 1060 | 1060 | ||
| 1061 | - * `percentile` {number} A percentile value in the range (0, 100). | ||
| 1061 | + * `percentile` {number} A percentile value in the range (0, 100]. | ||
| 1062 | 1062 | * Returns: {bigint} | |
| 1063 | 1063 | ||
| 1064 | 1064 | Returns the value at the given percentile. | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3533,7 +3533,7 @@ Synchronous writes avoid problems such as output written with `console.log()` or | |||
| 3533 | 3533 | _**Warning**_: Synchronous writes block the event loop until the write has | |
| 3534 | 3534 | completed. This can be near instantaneous in the case of output to a file, but | |
| 3535 | 3535 | under high system load, pipes that are not being read at the receiving end, or | |
| 3536 | - with slow terminals or file systems, its possible for the event loop to be | ||
| 3536 | + with slow terminals or file systems, it's possible for the event loop to be | ||
| 3537 | 3537 | blocked often enough and long enough to have severe negative performance | |
| 3538 | 3538 | impacts. This may not be a problem when writing to an interactive terminal | |
| 3539 | 3539 | session, but consider this particularly careful when doing production logging to | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1323,7 +1323,7 @@ const { createInterface } = require('readline'); | |||
| 1323 | 1323 | </tr> | |
| 1324 | 1324 | <tr> | |
| 1325 | 1325 | <td><kbd>Ctrl</kbd>+<kbd>E</kbd></td> | |
| 1326 | - <td>Go to to end of line</td> | ||
| 1326 | + <td>Go to end of line</td> | ||
| 1327 | 1327 | <td></td> | |
| 1328 | 1328 | </tr> | |
| 1329 | 1329 | <tr> | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -228,7 +228,7 @@ To use session tickets across server restarts or load balancers, servers must | |||
| 228 | 228 | all have the same ticket keys. There are three 16-byte keys internally, but the | |
| 229 | 229 | tls API exposes them as a single 48-byte buffer for convenience. | |
| 230 | 230 | ||
| 231 | - Its possible to get the ticket keys by calling [`server.getTicketKeys()`][] on | ||
| 231 | + It's possible to get the ticket keys by calling [`server.getTicketKeys()`][] on | ||
| 232 | 232 | one server instance and then distribute them, but it is more reasonable to | |
| 233 | 233 | securely generate 48 bytes of secure random data and set them with the | |
| 234 | 234 | `ticketKeys` option of [`tls.createServer()`][]. The keys should be regularly | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1047,7 +1047,7 @@ current V8 isolate, or the main context. | |||
| 1047 | 1047 | * `options` {Object} Optional. | |
| 1048 | 1048 | * `mode` {string} Either `'summary'` or `'detailed'`. In summary mode, | |
| 1049 | 1049 | only the memory measured for the main context will be returned. In | |
| 1050 | - detailed mode, the measure measured for all contexts known to the | ||
| 1050 | + detailed mode, the memory measured for all contexts known to the | ||
| 1051 | 1051 | current V8 isolate will be returned. | |
| 1052 | 1052 | **Default:** `'summary'` | |
| 1053 | 1053 | * `execution` {string} Either `'default'` or `'eager'`. With default | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -117,7 +117,7 @@ for (let i = 0; i < 30000; ++i) { | |||
| 117 | 117 | ||
| 118 | 118 | In the preceding example, 30,000 deflate instances are created concurrently. | |
| 119 | 119 | Because of how some operating systems handle memory allocation and | |
| 120 | - deallocation, this may lead to to significant memory fragmentation. | ||
| 120 | + deallocation, this may lead to significant memory fragmentation. | ||
| 121 | 121 | ||
| 122 | 122 | It is strongly recommended that the results of compression | |
| 123 | 123 | operations be cached to avoid duplication of effort. | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -25,7 +25,7 @@ Details on the fork, as well as the latest sources, can be found at | |||
| 25 | 25 | <https://github.com/quictls/openssl>. | |
| 26 | 26 | ||
| 27 | 27 | Branches are used per OpenSSL version (for instance, | |
| 28 | - <https://github.com/quictls/openssl/tree/OpenSSL_1_1_1j+quic)>. | ||
| 28 | + <https://github.com/quictls/openssl/tree/OpenSSL_1_1_1j+quic>). | ||
| 29 | 29 | ||
| 30 | 30 | ## Requirements | |
| 31 | 31 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -437,7 +437,7 @@ check with the contributor to see if they intend to continue the work before | |||
| 437 | 437 | checking if they would mind if you took it over (especially if it just has | |
| 438 | 438 | nits left). When doing so, it is courteous to give the original contributor | |
| 439 | 439 | credit for the work they started (either by preserving their name and email | |
| 440 | - address in the commit log, or by using an `Author:` meta-data tag in the | ||
| 440 | + address) in the commit log, or by using an `Author:` meta-data tag in the | ||
| 441 | 441 | commit. | |
| 442 | 442 | ||
| 443 | 443 | ### Approving a change | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -13,4 +13,4 @@ titled `Please add me to coverity`. A member of the build WG with admin | |||
| 13 | 13 | access will verify that the requestor is an existing collaborator as listed in | |
| 14 | 14 | the [collaborators section](https://github.com/nodejs/node#collaborators) | |
| 15 | 15 | on the nodejs/node project repo. Once validated the requestor will added | |
| 16 | - to to the coverity project. | ||
| 16 | + to the coverity project. | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments