From 642267f6848869a64861c3176eb5a6d5980639c6 Mon Sep 17 00:00:00 2001 From: Stanley Ume Date: Mon, 21 Aug 2023 20:27:46 +0200 Subject: [PATCH] docs: Minor grammar correction in ManualMocks.md (#14424) --- docs/ManualMocks.md | 4 ++-- website/versioned_docs/version-29.4/ManualMocks.md | 4 ++-- website/versioned_docs/version-29.5/ManualMocks.md | 4 ++-- website/versioned_docs/version-29.6/ManualMocks.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/ManualMocks.md b/docs/ManualMocks.md index d166114387eb..7d7e9ab8f1d1 100644 --- a/docs/ManualMocks.md +++ b/docs/ManualMocks.md @@ -29,7 +29,7 @@ Scoped modules (also known as [scoped packages](https://docs.npmjs.com/cli/v6/us :::caution -If we want to mock Node's build-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because build-in modules are not mocked by default. +If we want to mock Node's built-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because built-in modules are not mocked by default. ::: @@ -110,7 +110,7 @@ fs.readdirSync = readdirSync; module.exports = fs; ``` -Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s build-in module: +Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s built-in module: ```javascript title="__tests__/FileSummarizer-test.js" 'use strict'; diff --git a/website/versioned_docs/version-29.4/ManualMocks.md b/website/versioned_docs/version-29.4/ManualMocks.md index d166114387eb..7d7e9ab8f1d1 100644 --- a/website/versioned_docs/version-29.4/ManualMocks.md +++ b/website/versioned_docs/version-29.4/ManualMocks.md @@ -29,7 +29,7 @@ Scoped modules (also known as [scoped packages](https://docs.npmjs.com/cli/v6/us :::caution -If we want to mock Node's build-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because build-in modules are not mocked by default. +If we want to mock Node's built-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because built-in modules are not mocked by default. ::: @@ -110,7 +110,7 @@ fs.readdirSync = readdirSync; module.exports = fs; ``` -Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s build-in module: +Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s built-in module: ```javascript title="__tests__/FileSummarizer-test.js" 'use strict'; diff --git a/website/versioned_docs/version-29.5/ManualMocks.md b/website/versioned_docs/version-29.5/ManualMocks.md index d166114387eb..7d7e9ab8f1d1 100644 --- a/website/versioned_docs/version-29.5/ManualMocks.md +++ b/website/versioned_docs/version-29.5/ManualMocks.md @@ -29,7 +29,7 @@ Scoped modules (also known as [scoped packages](https://docs.npmjs.com/cli/v6/us :::caution -If we want to mock Node's build-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because build-in modules are not mocked by default. +If we want to mock Node's built-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because built-in modules are not mocked by default. ::: @@ -110,7 +110,7 @@ fs.readdirSync = readdirSync; module.exports = fs; ``` -Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s build-in module: +Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s built-in module: ```javascript title="__tests__/FileSummarizer-test.js" 'use strict'; diff --git a/website/versioned_docs/version-29.6/ManualMocks.md b/website/versioned_docs/version-29.6/ManualMocks.md index d166114387eb..7d7e9ab8f1d1 100644 --- a/website/versioned_docs/version-29.6/ManualMocks.md +++ b/website/versioned_docs/version-29.6/ManualMocks.md @@ -29,7 +29,7 @@ Scoped modules (also known as [scoped packages](https://docs.npmjs.com/cli/v6/us :::caution -If we want to mock Node's build-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because build-in modules are not mocked by default. +If we want to mock Node's built-in modules (e.g.: `fs` or `path`), then explicitly calling e.g. `jest.mock('path')` is **required**, because built-in modules are not mocked by default. ::: @@ -110,7 +110,7 @@ fs.readdirSync = readdirSync; module.exports = fs; ``` -Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s build-in module: +Now we write our test. In this case `jest.mock('fs')` must be called explicitly, because `fs` is Node’s built-in module: ```javascript title="__tests__/FileSummarizer-test.js" 'use strict';