From e6f60d2adda7d4ebf6631eb8166572c3706d52a3 Mon Sep 17 00:00:00 2001 From: 180909 Date: Mon, 15 Nov 2021 23:58:21 +0800 Subject: [PATCH] fix typos (#22715) --- packages/react-dom/src/__tests__/CSSPropertyOperations-test.js | 2 +- packages/react-reconciler/src/ReactFiberCompleteWork.new.js | 2 +- packages/react-reconciler/src/ReactFiberCompleteWork.old.js | 2 +- packages/react-reconciler/src/ReactFiberTreeContext.new.js | 2 +- packages/react-reconciler/src/ReactFiberTreeContext.old.js | 2 +- packages/react-reconciler/src/ReactFiberWorkLoop.new.js | 2 +- packages/react-reconciler/src/ReactFiberWorkLoop.old.js | 2 +- packages/react-server/src/ReactFizzTreeContext.js | 2 +- scripts/release/README.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/packages/react-dom/src/__tests__/CSSPropertyOperations-test.js b/packages/react-dom/src/__tests__/CSSPropertyOperations-test.js index 53d0903c7e9a2..5f177b17202a6 100644 --- a/packages/react-dom/src/__tests__/CSSPropertyOperations-test.js +++ b/packages/react-dom/src/__tests__/CSSPropertyOperations-test.js @@ -224,7 +224,7 @@ describe('CSSPropertyOperations', () => { ReactDOM.render(, root); }); - it('should warn about style containing a Infinity value', () => { + it('should warn about style containing an Infinity value', () => { class Comp extends React.Component { static displayName = 'Comp'; diff --git a/packages/react-reconciler/src/ReactFiberCompleteWork.new.js b/packages/react-reconciler/src/ReactFiberCompleteWork.new.js index feb38f00461a0..5805ffe8da769 100644 --- a/packages/react-reconciler/src/ReactFiberCompleteWork.new.js +++ b/packages/react-reconciler/src/ReactFiberCompleteWork.new.js @@ -884,7 +884,7 @@ function completeWork( // Schedule an effect to clear this container at the start of the next commit. // This handles the case of React rendering into a container with previous children. // It's also safe to do for updates too, because current.child would only be null - // if the previous render was null (so the the container would already be empty). + // if the previous render was null (so the container would already be empty). workInProgress.flags |= Snapshot; } } diff --git a/packages/react-reconciler/src/ReactFiberCompleteWork.old.js b/packages/react-reconciler/src/ReactFiberCompleteWork.old.js index ea4d71e8ba371..c5eb5f70f48d6 100644 --- a/packages/react-reconciler/src/ReactFiberCompleteWork.old.js +++ b/packages/react-reconciler/src/ReactFiberCompleteWork.old.js @@ -884,7 +884,7 @@ function completeWork( // Schedule an effect to clear this container at the start of the next commit. // This handles the case of React rendering into a container with previous children. // It's also safe to do for updates too, because current.child would only be null - // if the previous render was null (so the the container would already be empty). + // if the previous render was null (so the container would already be empty). workInProgress.flags |= Snapshot; } } diff --git a/packages/react-reconciler/src/ReactFiberTreeContext.new.js b/packages/react-reconciler/src/ReactFiberTreeContext.new.js index 968e66155d3fa..f9c5104ed6b13 100644 --- a/packages/react-reconciler/src/ReactFiberTreeContext.new.js +++ b/packages/react-reconciler/src/ReactFiberTreeContext.new.js @@ -50,7 +50,7 @@ // new level with a single slot. You can think of this as a fork with only one // prong, or an array of children with length 1. // -// It's possible for the the size of the sequence to exceed 32 bits, the max +// It's possible for the size of the sequence to exceed 32 bits, the max // size for bitwise operations. When this happens, we make more room by // converting the right part of the id to a string and storing it in an overflow // variable. We use a base 32 string representation, because 32 is the largest diff --git a/packages/react-reconciler/src/ReactFiberTreeContext.old.js b/packages/react-reconciler/src/ReactFiberTreeContext.old.js index 82990b22f983d..840335d00c4e4 100644 --- a/packages/react-reconciler/src/ReactFiberTreeContext.old.js +++ b/packages/react-reconciler/src/ReactFiberTreeContext.old.js @@ -50,7 +50,7 @@ // new level with a single slot. You can think of this as a fork with only one // prong, or an array of children with length 1. // -// It's possible for the the size of the sequence to exceed 32 bits, the max +// It's possible for the size of the sequence to exceed 32 bits, the max // size for bitwise operations. When this happens, we make more room by // converting the right part of the id to a string and storing it in an overflow // variable. We use a base 32 string representation, because 32 is the largest diff --git a/packages/react-reconciler/src/ReactFiberWorkLoop.new.js b/packages/react-reconciler/src/ReactFiberWorkLoop.new.js index 71bf8175105d6..f0f5eab4a99f5 100644 --- a/packages/react-reconciler/src/ReactFiberWorkLoop.new.js +++ b/packages/react-reconciler/src/ReactFiberWorkLoop.new.js @@ -1025,7 +1025,7 @@ function finishConcurrentRender(root, exitStatus, lanes) { function isRenderConsistentWithExternalStores(finishedWork: Fiber): boolean { // Search the rendered tree for external store reads, and check whether the - // stores were mutated in a concurrent event. Intentionally using a iterative + // stores were mutated in a concurrent event. Intentionally using an iterative // loop instead of recursion so we can exit early. let node: Fiber = finishedWork; while (true) { diff --git a/packages/react-reconciler/src/ReactFiberWorkLoop.old.js b/packages/react-reconciler/src/ReactFiberWorkLoop.old.js index 8be4630dc079d..353de50e1585a 100644 --- a/packages/react-reconciler/src/ReactFiberWorkLoop.old.js +++ b/packages/react-reconciler/src/ReactFiberWorkLoop.old.js @@ -1025,7 +1025,7 @@ function finishConcurrentRender(root, exitStatus, lanes) { function isRenderConsistentWithExternalStores(finishedWork: Fiber): boolean { // Search the rendered tree for external store reads, and check whether the - // stores were mutated in a concurrent event. Intentionally using a iterative + // stores were mutated in a concurrent event. Intentionally using an iterative // loop instead of recursion so we can exit early. let node: Fiber = finishedWork; while (true) { diff --git a/packages/react-server/src/ReactFizzTreeContext.js b/packages/react-server/src/ReactFizzTreeContext.js index c9a47e5af72a6..3b924cf8eb3af 100644 --- a/packages/react-server/src/ReactFizzTreeContext.js +++ b/packages/react-server/src/ReactFizzTreeContext.js @@ -50,7 +50,7 @@ // new level with a single slot. You can think of this as a fork with only one // prong, or an array of children with length 1. // -// It's possible for the the size of the sequence to exceed 32 bits, the max +// It's possible for the size of the sequence to exceed 32 bits, the max // size for bitwise operations. When this happens, we make more room by // converting the right part of the id to a string and storing it in an overflow // variable. We use a base 32 string representation, because 32 is the largest diff --git a/scripts/release/README.md b/scripts/release/README.md index 1737c3cf18800..04900c296d0cb 100644 --- a/scripts/release/README.md +++ b/scripts/release/README.md @@ -21,7 +21,7 @@ A typical release cycle goes like this: 1. When a commit is pushed to the React repo, [Circle CI](https://circleci.com/gh/facebook/react/) will build all release bundles and run unit tests against both the source code and the built bundles. 2. Each weekday, an automated CI cron job publishes prereleases to the `next` and `experimental` channels, from tip of the main branch. 1. You can also [trigger an automated prerelease via the command line](#trigger-an-automated-prerelease), instead of waiting until the next time the cron job runs. - 2. For advanced cases, you can [**manually prepare and publish to the `next` channel**](#publishing-release) using the [`prepare-release-from-ci`](#prepare-release-from-ci) and [`publish`](#publish) scripts; or to the [**`experimental` channel**](#publishing-an-experimental-release) using the the same scripts (but different build artifacts). + 2. For advanced cases, you can [**manually prepare and publish to the `next` channel**](#publishing-release) using the [`prepare-release-from-ci`](#prepare-release-from-ci) and [`publish`](#publish) scripts; or to the [**`experimental` channel**](#publishing-an-experimental-release) using the same scripts (but different build artifacts). 3. Finally, a "next" release can be [**promoted to stable**](#publishing-a-stable-release)1 using the [`prepare-release-from-npm`](#prepare-release-from-npm) and [`publish`](#publish) scripts. (This process is always manual.) The high level process of creating releases is [documented below](#process). Individual scripts are documented as well: