Spelling (#1427)

benchmarks/child.bench.js

@@ -45,7 +45,7 @@ const run = bench([
     }
     setImmediate(cb)
   },
-  function benchPinoAssyncChild (cb) {
+  function benchPinoAsyncChild (cb) {
     for (var i = 0; i < max; i++) {
       plogAsync.info({ hello: 'world' })
     }

benchmarks/internal/parent-vs-child.bench.js

@@ -52,19 +52,19 @@ const run = bench([
     }
     setImmediate(cb)
   },
-  function benchPinoBaseSerilalizers (cb) {
+  function benchPinoBaseSerializers (cb) {
     for (var i = 0; i < max; i++) {
       baseSerializers.info({ hello: 'world' })
     }
     setImmediate(cb)
   },
-  function benchPinoBaseSerilalizersChild (cb) {
+  function benchPinoBaseSerializersChild (cb) {
     for (var i = 0; i < max; i++) {
       baseSerializersChild.info({ hello: 'world' })
     }
     setImmediate(cb)
   },
-  function benchPinoBaseSerilalizersChildSeriazliers (cb) {
+  function benchPinoBaseSerializersChildSerializers (cb) {
     for (var i = 0; i < max; i++) {
       baseSerializersChildSerializers.info({ hello: 'world' })
     }

docs/api.md

@@ -983,7 +983,7 @@ The listener is passed four arguments:
 * `levelLabel` – the new level string, e.g `trace`
 * `levelValue` – the new level number, e.g `10`
 * `previousLevelLabel` – the prior level string, e.g `info`
-* `previousLevelValue` – the prior level numbebr, e.g `30`
+* `previousLevelValue` – the prior level number, e.g `30`
 
 ```js
 const logger = require('pino')()

docs/bundling.md

@@ -12,7 +12,7 @@ In particular, a bundler must ensure that the following files are also bundle se
 
 Once the files above have been generated, the bundler must also add information about the files above by injecting a code which sets `__bundlerPathsOverrides` in the `globalThis` object.
 
-The variable is a object whose keys are identifier for the files and the the values are the paths of files relative to the currently bundle files.
+The variable is a object whose keys are identifier for the files and the values are the paths of files relative to the currently bundle files.
 
 Example:
 

docs/ecosystem.md

@@ -69,7 +69,7 @@ MongoDB and many [others](https://www.fluentd.org/dataoutputs) via Fluentd.
 prettifier inspired by the [logrus](https://github.com/sirupsen/logrus) logger.
 + [`pino-rotating-file`](https://github.com/homeaway/pino-rotating-file): a hapi-pino log transport for splitting logs into separate, automatically rotating files.
 + [`cls-proxify`](https://github.com/keenondrums/cls-proxify): integration of pino and [CLS](https://github.com/jeff-lewis/cls-hooked). Useful for creating dynamically configured child loggers (e.g. with added trace ID) for each request.
-+ [`pino-tiny`](https://github.com/holmok/pino-tiny): a tiny (and exentsible?) little log formatter for pino.
++ [`pino-tiny`](https://github.com/holmok/pino-tiny): a tiny (and extensible?) little log formatter for pino.
 + [`pino-dev`](https://github.com/dnjstrom/pino-dev): simple prettifier for pino with built-in support for common ecosystem packages.
 + [`@newrelic/pino-enricher`](https://github.com/newrelic/newrelic-node-log-extensions/blob/main/packages/pino-log-enricher): a log customization to add New Relic context to use [Logs In Context](https://docs.newrelic.com/docs/logs/logs-context/logs-in-context/)
-+ [`pino-lamdba`](https://github.com/FormidableLabs/pino-lambda): log transport for cloudwatch support inside aws-lambda 
++ [`pino-lambda`](https://github.com/FormidableLabs/pino-lambda): log transport for cloudwatch support inside aws-lambda 

docs/help.md

@@ -10,7 +10,7 @@
 * [Log levels as labels instead of numbers](#level-string)
 * [Pino with `debug`](#debug)
 * [Unicode and Windows terminal](#windows)
-* [Mapping Pino Log Levels to Google Cloud Logging (Stackdriver) Serverity Levels](#stackdriver)
+* [Mapping Pino Log Levels to Google Cloud Logging (Stackdriver) Severity Levels](#stackdriver)
 * [Avoid Message Conflict](#avoid-message-conflict)
 * [Exit logging](#exit-logging)
 
@@ -201,12 +201,12 @@ executing in the terminal `chcp 65001`. This is a known limitation of
 Node.js.
 
 <a id="stackdriver"></a>
-## Mapping Pino Log Levels to Google Cloud Logging (Stackdriver) Serverity Levels
+## Mapping Pino Log Levels to Google Cloud Logging (Stackdriver) Severity Levels
 
 Google Cloud Logging uses `severity` levels instead log levels. As a result, all logs may show as INFO
 level logs while completely ignoring the level set in the pino log. Google Cloud Logging also prefers that
 log data is present inside a `message` key instead of the default `msg` key that Pino uses. Use a technique
-similar to the one below to retain log levels in Google Clould Logging
+similar to the one below to retain log levels in Google Cloud Logging
 
 ```js
 const pino = require('pino')

docs/redaction.md

@@ -3,7 +3,7 @@
 > Redaction is not supported in the browser [#670](https://github.com/pinojs/pino/issues/670)
 
 To redact sensitive information, supply paths to keys that hold sensitive data
-using the `redact` option. Note that paths which contain hypens need to use
+using the `redact` option. Note that paths which contain hyphens need to use
 brackets in order to access the hyphenated property:
 
 ```js

test/multistream.test.js

@@ -256,7 +256,7 @@ test('children support custom levels', function (t) {
   child.foo('bar')
 })
 
-test('levelVal ovverides level', function (t) {
+test('levelVal overrides level', function (t) {
   let messageCount = 0
   const stream = writeStream(function (data, enc, cb) {
     messageCount += 1

test/redact.test.js

@@ -732,7 +732,7 @@ test('supports leading bracket notation (single-segment path)', async ({ equal }
   equal(o['a.a'], '[Redacted]')
 })
 
-test('supports leading bracket notation (single-segment path, wilcard)', async ({ equal }) => {
+test('supports leading bracket notation (single-segment path, wildcard)', async ({ equal }) => {
   const stream = sink()
   const instance = pino({ redact: ['[*]'] }, stream)
   const obj = {

test/transport/big.test.js

@@ -19,7 +19,7 @@ test('eight million lines', async ({ equal, comment }) => {
 
   if (process.platform !== 'win32') {
     try {
-      await execa('sync') // Wait for the file to be writen to disk
+      await execa('sync') // Wait for the file to be written to disk
     } catch {
       // Just a fallback, this should be unreachable
     }

test/transport/bundlers-support.test.js

@@ -10,7 +10,7 @@ const pino = require('../../pino')
 const { pid } = process
 const hostname = os.hostname()
 
-test('pino.transport with destination overriden by bundler', async ({ same, teardown }) => {
+test('pino.transport with destination overridden by bundler', async ({ same, teardown }) => {
   globalThis.__bundlerPathsOverrides = {
     foobar: join(__dirname, '..', 'fixtures', 'to-file-transport.js')
   }
@@ -36,7 +36,7 @@ test('pino.transport with destination overriden by bundler', async ({ same, tear
   globalThis.__bundlerPathsOverrides = undefined
 })
 
-test('pino.transport with worker destination overriden by bundler', async ({ same, teardown }) => {
+test('pino.transport with worker destination overridden by bundler', async ({ same, teardown }) => {
   globalThis.__bundlerPathsOverrides = {
     'pino-worker': join(__dirname, '..', '..', 'lib/worker.js')
   }
@@ -66,7 +66,7 @@ test('pino.transport with worker destination overriden by bundler', async ({ sam
   globalThis.__bundlerPathsOverrides = undefined
 })
 
-test('pino.transport with worker-pipeline destination overriden by bundler', async ({ same, teardown }) => {
+test('pino.transport with worker-pipeline destination overridden by bundler', async ({ same, teardown }) => {
   globalThis.__bundlerPathsOverrides = {
     'pino-pipeline-worker': join(__dirname, '..', '..', 'lib/worker-pipeline.js')
   }