From d7f097543f8c222b1ec52bc9bddf3a60c40d59ce Mon Sep 17 00:00:00 2001 From: Simen Bekkhus Date: Mon, 13 Sep 2021 10:58:27 +0200 Subject: [PATCH] chore: fix typo in docs This is mostly to trigger a deploy of the site --- docs/MockFunctionAPI.md | 2 +- website/versioned_docs/version-25.x/MockFunctionAPI.md | 2 +- website/versioned_docs/version-26.x/MockFunctionAPI.md | 2 +- website/versioned_docs/version-27.0/MockFunctionAPI.md | 2 +- website/versioned_docs/version-27.1/MockFunctionAPI.md | 2 +- website/versioned_docs/version-27.2/MockFunctionAPI.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/MockFunctionAPI.md b/docs/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/docs/MockFunctionAPI.md +++ b/docs/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data. diff --git a/website/versioned_docs/version-25.x/MockFunctionAPI.md b/website/versioned_docs/version-25.x/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/website/versioned_docs/version-25.x/MockFunctionAPI.md +++ b/website/versioned_docs/version-25.x/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data. diff --git a/website/versioned_docs/version-26.x/MockFunctionAPI.md b/website/versioned_docs/version-26.x/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/website/versioned_docs/version-26.x/MockFunctionAPI.md +++ b/website/versioned_docs/version-26.x/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data. diff --git a/website/versioned_docs/version-27.0/MockFunctionAPI.md b/website/versioned_docs/version-27.0/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/website/versioned_docs/version-27.0/MockFunctionAPI.md +++ b/website/versioned_docs/version-27.0/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data. diff --git a/website/versioned_docs/version-27.1/MockFunctionAPI.md b/website/versioned_docs/version-27.1/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/website/versioned_docs/version-27.1/MockFunctionAPI.md +++ b/website/versioned_docs/version-27.1/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data. diff --git a/website/versioned_docs/version-27.2/MockFunctionAPI.md b/website/versioned_docs/version-27.2/MockFunctionAPI.md index 3cc228fd7880..6010aaf573f6 100644 --- a/website/versioned_docs/version-27.2/MockFunctionAPI.md +++ b/website/versioned_docs/version-27.2/MockFunctionAPI.md @@ -83,7 +83,7 @@ mockFn.mock.instances[1] === b; // true Resets all information stored in the [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances) arrays. -Often this is useful when you want to clean up a mock's usage data between two assertions. +Often this is useful when you want to clean up a mocks usage data between two assertions. Beware that `mockClear` will replace `mockFn.mock`, not just [`mockFn.mock.calls`](#mockfnmockcalls) and [`mockFn.mock.instances`](#mockfnmockinstances). You should, therefore, avoid assigning `mockFn.mock` to other variables, temporary or not, to make sure you don't access stale data.