chore: fix some comments

Signed-off-by: clonemycode <[email protected]>

__tests__/base.js

@@ -490,7 +490,7 @@ function runBaseTest(name, autoFreeze, useStrictShallowCopy, useListener) {
 				expect(nextState.get(key)).toEqual(true)
 			})
 
-			it("state stays the same if the the same item is assigned by key", () => {
+			it("state stays the same if the same item is assigned by key", () => {
 				const nextState = produce(baseState, s => {
 					s.aMap.set("jediTotal", 42)
 				})

__tests__/produce.ts

@@ -736,7 +736,7 @@ it("infers curried", () => {
 		assert(n, _ as State)
 	}
 	{
-		// explictly use generic
+		// explicitly use generic
 		const f = produce<ROState>(draft => {
 			draft.count++
 		})

website/docs/typescript.mdx

@@ -109,7 +109,7 @@ Note that we did wrap the `Todo` type of the `draft` argument with `Draft`, beca
 
 For the returned curried function, `toggler`, We will _narrow_ the _input_ type to `Immutable<Todo>`, so that even though `Todo` is a mutable type, we will still accept an immutable todo as input argument to `toggler`.
 
-In contrast, Immer will _widen_ the _output_ type of the curried function to `Writable<Todo>`, to make sure it's output state is also assignable to variables that are not explictly typed to be immutable.
+In contrast, Immer will _widen_ the _output_ type of the curried function to `Writable<Todo>`, to make sure it's output state is also assignable to variables that are not explicitly typed to be immutable.
 
 This type narrowing / widening behavior might be unwelcome, maybe even for the simple reason that it results in quite noisy types. So we recommend to specify the generic state type for curried producers instead, in cases where it cannot be inferred directly, like `toggler` above. By doing so the automatic output widening / input narrowing will be skipped. However, the `draft` argument itself will still be inferred to be a writable `Draft<Todo>`: