fix: varous typos (#2513)

nschonni · jakebailey · web-flow · commit 7a686ece189c · 2023-05-18T21:12:28.000Z
Co-authored-by: Jake Bailey &lt;5341706+jakebailey@users.noreply.github.com&gt;
diff --git a/docs/Deprecating a page.md b/docs/Deprecating a page.md
@@ -1,6 +1,6 @@
 ## Deprecating a documentation page
 
-Start with this question: are you deprecating or deleting? Ideally you're never deleting because [Cool URIs Dont Change](https://www.w3.org/Provider/Style/URI.html) but for something which intentionally had a limited self-life, that's OK.
+Start with this question: are you deprecating or deleting? Ideally you're never deleting because [Cool URIs Don't Change](https://www.w3.org/Provider/Style/URI.html) but for something which intentionally had a limited self-life, that's OK.
 
 ### Keep or Redirect?
 
diff --git a/packages/ata/README.md b/packages/ata/README.md
@@ -53,7 +53,7 @@ The library will
 - Recurse though their dependencies too.
 - Once those are done, trigger `finished` with a Map of the `vfs` if you prefer to set them in bulk.
 
-### Nicities
+### Niceties
 
 Users can give a specific npm version or tag to work from instead of the default "latest":
 
diff --git a/packages/community-meta/README.md b/packages/community-meta/README.md
@@ -35,7 +35,7 @@ All localizations live inside the `copy` folder:
 - Any examples not copied over fall back to the english version
 - You can change the name of an example for your language by having `//// { "title": 'c0d3 fl0w', ... }` in the first line of the example
 
-Languages are compiled to TOC JSON files in [`generated`](./generated), one per lanaguge.
+Languages are compiled to TOC JSON files in [`generated`](./generated), one per language.
 
 # Deployment
 
diff --git a/packages/documentation/copy/en/get-started/TS for the New Programmer.md b/packages/documentation/copy/en/get-started/TS for the New Programmer.md
@@ -183,7 +183,7 @@ This was a brief overview of the syntax and tools used in everyday TypeScript. F
       * Types implicitly define what operations make sense on them
       * Lots of different kinds, not just primitives
       * We can make descriptions for all kinds of values
-      * The `any` type -- a quick desctiption, what it is, and why it's bad
+      * The `any` type -- a quick description, what it is, and why it's bad
     * Inference 101
       * Examples
       * TypeScript can figure out types most of the time
diff --git a/packages/documentation/copy/en/reference/ESM Support for Node.md b/packages/documentation/copy/en/reference/ESM Support for Node.md
@@ -207,7 +207,7 @@ A package author could override this by specifying a separate field called `"typ
 
 The new support works similarly with [import conditions](https://nodejs.org/api/packages.html).
 By default, TypeScript overlays the same rules with import conditions - if you write an `import` from an ES module, it will look up the `import` field, and from a CommonJS module, it will look at the `require` field.
-If it finds them, it will look for a colocated declaration file.
+If it finds them, it will look for a co-located declaration file.
 If you need to point to a different location for your type declarations, you can add a `"types"` import condition.
 
 ```json5
diff --git a/packages/documentation/copy/en/reference/Iterators and Generators.md b/packages/documentation/copy/en/reference/Iterators and Generators.md
@@ -97,4 +97,4 @@ for (var _i = 0; _i < numbers.length; _i++) {
 
 #### Targeting ECMAScript 2015 and higher
 
-When targeting an ECMAScipt 2015-compliant engine, the compiler will generate `for..of` loops to target the built-in iterator implementation in the engine.
+When targeting an ECMAScript 2015-compliant engine, the compiler will generate `for..of` loops to target the built-in iterator implementation in the engine.
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 1.6.md b/packages/documentation/copy/en/release-notes/TypeScript 1.6.md
@@ -45,7 +45,7 @@ class MyComponent extends React.Component<Props, {}> {
 <MyComponent name={0} />; // error, `name` is not a number
 ```
 
-#### Using other JSX framworks
+#### Using other JSX frameworks
 
 JSX element names and properties are validated against the `JSX` namespace.
 Please see the [[JSX]] wiki page for defining the `JSX` namespace for your framework.
@@ -454,7 +454,7 @@ For example:
 }
 ```
 
-The [`exclude`](/tsconfig#exclude) list does not support wilcards. It must simply be a list of files and/or directories.
+The [`exclude`](/tsconfig#exclude) list does not support wildcards. It must simply be a list of files and/or directories.
 
 ## `--init` command line option
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 1.8.md b/packages/documentation/copy/en/release-notes/TypeScript 1.8.md
@@ -466,7 +466,7 @@ var div = jsxFactory_1.jsxFactory.createElement("div", null, "Hello JSX!");
 TypeScript 1.8 extends [user-defined type guard functions](./typescript-1.6.html#user-defined-type-guard-functions) to class and interface methods.
 
 `this is T` is now valid return type annotation for methods in classes and interfaces.
-When used in a type narowing position (e.g. `if` statement), the type of the call expression target object would be narrowed to `T`.
+When used in a type narrowing position (e.g. `if` statement), the type of the call expression target object would be narrowed to `T`.
 
 ##### Example
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 2.3.md b/packages/documentation/copy/en/release-notes/TypeScript 2.3.md
@@ -24,7 +24,7 @@ interface Iterator<T> {
 This kind of iterator is useful for iterating over synchronously available values, such as the elements of an Array or the keys of a Map.
 An object that supports iteration is said to be "iterable" if it has a `Symbol.iterator` method that returns an `Iterator` object.
 
-The Iterator protocol also defines the target of some of the ES2015 features like `for..of` and spread operator and the array rest in destructuring assignmnets.
+The Iterator protocol also defines the target of some of the ES2015 features like `for..of` and spread operator and the array rest in destructuring assignments.
 
 ##### Generators
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 2.9.md b/packages/documentation/copy/en/release-notes/TypeScript 2.9.md
@@ -237,7 +237,7 @@ function walk(p) {
 }
 ```
 
-## Relaxing declaration emit visiblity rules
+## Relaxing declaration emit visibility rules
 
 With `import` types available, many of the visibility errors reported during declaration file generation can be handled by the compiler without the need to change the input.
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 3.2.md b/packages/documentation/copy/en/release-notes/TypeScript 3.2.md
@@ -14,7 +14,7 @@ function foo(a: number, b: string): string {
   return a + b;
 }
 
-let a = foo.apply(undefined, [10]); // error: too few argumnts
+let a = foo.apply(undefined, [10]); // error: too few arguments
 let b = foo.apply(undefined, [10, 20]); // error: 2nd argument is a number
 let c = foo.apply(undefined, [10, "hello", 30]); // error: too many arguments
 let d = foo.apply(undefined, [10, "hello"]); // okay! returns a string
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 3.3.md b/packages/documentation/copy/en/release-notes/TypeScript 3.3.md
@@ -113,6 +113,6 @@ Prior to 3.3, building composite projects using `--build --watch` actually didn'
 An update in one project under `--build --watch` mode would force a full build of that project, rather than determining which files within that project were affected.
 
 In TypeScript 3.3, `--build` mode's `--watch` flag _does_ leverage incremental file watching as well.
-That can mean signficantly faster builds under `--build --watch`.
+That can mean significantly faster builds under `--build --watch`.
 In our testing, this functionality has resulted in **a reduction of 50% to 75% in build times** of the original `--build --watch` times.
 [You can read more on the original pull request for the change](https://github.com/Microsoft/TypeScript/pull/29161) to see specific numbers, but we believe most composite project users will see significant wins here.
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 3.7.md b/packages/documentation/copy/en/release-notes/TypeScript 3.7.md
@@ -736,7 +736,7 @@ function doAdminThing(user: User) {
 }
 ```
 
-Here, we forgot to call `isAdministrator`, and the code incorrectly allows non-adminstrator users to edit the configuration!
+Here, we forgot to call `isAdministrator`, and the code incorrectly allows non-administrator users to edit the configuration!
 
 In TypeScript 3.7, this is identified as a likely error:
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 3.9.md b/packages/documentation/copy/en/release-notes/TypeScript 3.9.md
@@ -368,7 +368,7 @@ foo?.bar!.baz;
 ### `}` and `>` are Now Invalid JSX Text Characters
 
 The JSX Specification forbids the use of the `}` and `>` characters in text positions.
-TypeScript and Babel have both decided to enforce this rule to be more comformant.
+TypeScript and Babel have both decided to enforce this rule to be more conformant.
 The new way to insert these characters is to use an HTML escape code (e.g. `<span> 2 &gt 1 </span>`) or insert an expression with a string literal (e.g. `<span> 2 {">"} 1 </span>`).
 
 Luckily, thanks to the [pull request](https://github.com/microsoft/TypeScript/pull/36636) enforcing this from [Brad Zacher](https://github.com/bradzacher), you'll get an error message along the lines of
diff --git a/packages/documentation/copy/en/tutorials/ASP.NET Core.md b/packages/documentation/copy/en/tutorials/ASP.NET Core.md
@@ -89,7 +89,7 @@ _Configure the TypeScript compiler_
 
 First we need to tell TypeScript how to build. Right click on `scripts` and click **New Item**. Then choose **TypeScript Configuration File** and use the default name of `tsconfig.json`
 
-![A screenshot showing the new file diaglogue with TypeScript JSON Config selected](/images/tutorials/aspnet/tsconfig.png)
+![A screenshot showing the new file dialogue with TypeScript JSON Config selected](/images/tutorials/aspnet/tsconfig.png)
 
 Replace the contents of the `tsconfig.json` file with:
 
@@ -168,7 +168,7 @@ The first line tells Visual Studio to run the task ‘default’ after the build
 
 Now right-click on `gulpfile.js` and click Task Runner Explorer.
 
-![Screenshot of right clicking on the "Gulpfile.js" with 'Task Runner Exploere' selected](/images/tutorials/aspnet/taskrunner.png)
+![Screenshot of right clicking on the "Gulpfile.js" with 'Task Runner Explorer' selected](/images/tutorials/aspnet/taskrunner.png)
 
 If ‘default’ and ‘clean’ tasks don’t show up, refresh the explorer:
 
diff --git a/packages/documentation/scripts/generateDocsNavigationPerLanguage.js b/packages/documentation/scripts/generateDocsNavigationPerLanguage.js
@@ -236,7 +236,7 @@ for (const lang of langs) {
 
     /** @param {{ items?: HandbookNavSubItem[] }} itemable */
     function addItems(itemable) {
-      // Lots of 2nd level navs dont have subnav, bail for them
+      // Lots of 2nd level navs don't have subnav, bail for them
       if ("items" in itemable === false) return;
 
       codeForTheHandbook.push("items: [");
diff --git a/packages/playground-examples/README.md b/packages/playground-examples/README.md
@@ -35,7 +35,7 @@ All localizations live inside the `copy` folder:
 - Any examples not copied over fall back to the english version
 - You can change the name of an example for your language by having `//// { "title": 'c0d3 fl0w', ... }` in the first line of the example
 
-Languages are compiled to TOC JSON files in [`generated`](./generated), one per lanaguge.
+Languages are compiled to TOC JSON files in [`generated`](./generated), one per language.
 
 # Deployment
 
diff --git a/packages/playground-examples/copy/en/4-0/New TS Features/Variadic Tuples.ts b/packages/playground-examples/copy/en/4-0/New TS Features/Variadic Tuples.ts
@@ -48,6 +48,6 @@ const a = curry(sum, 1, 2)
 const b = curry(sum, 1)(2)
 const c = curry(sum)(1, 2)
 
-// You can find a more indepth explanation, with more code samples in
+// You can find a more in-depth explanation, with more code samples in
 // https://github.com/microsoft/TypeScript/pull/39094
 
diff --git a/packages/playground-handbook/README.md b/packages/playground-handbook/README.md
@@ -1,3 +1,3 @@
-### Plyground Handbook
+### Playground Handbook
 
 This package is structured similar to the main documentation section of the repo, and handles the content for the Playground documentation.
diff --git a/packages/playground-handbook/copy/en/Localization.md b/packages/playground-handbook/copy/en/Localization.md
@@ -1,6 +1,6 @@
 ## Localization
 
-Like the rest of this website, the TypeScript Playground is localized. As of 2021, the current list of supported lanaguges are:
+Like the rest of this website, the TypeScript Playground is localized. As of 2021, the current list of supported languages are:
 
 - [`es`](/es/play)
 - [`fr`](/fr/play)
diff --git a/packages/playground-worker/types.d.ts b/packages/playground-worker/types.d.ts
@@ -76,7 +76,7 @@ export declare class TypeScriptWorker implements ts.LanguageServiceHost {
     ): Promise<ts.TextChange[]>
     getFormattingEditsAfterKeystroke(
         fileName: string,
-        postion: number,
+        position: number,
         ch: string,
         options: ts.FormatCodeOptions
     ): Promise<ts.TextChange[]>
diff --git a/packages/playground/src/ds/createDesignSystem.ts b/packages/playground/src/ds/createDesignSystem.ts
@@ -331,21 +331,21 @@ export const createDesignSystem = (sandbox: Sandbox) => {
       }
 
       const renderManyChildren = (key: string, nodes: Node[], depth: number) => {
-        const childers = document.createElement("div")
-        childers.classList.add("ast-children")
+        const children = document.createElement("div")
+        children.classList.add("ast-children")
 
         const li = document.createElement("li")
         li.innerHTML = `${key}: [<br/>`
-        childers.appendChild(li)
+        children.appendChild(li)
 
         nodes.forEach(node => {
-          renderItem(childers, node, depth + 1)
+          renderItem(children, node, depth + 1)
         })
 
         const liEnd = document.createElement("li")
         liEnd.innerHTML += "]"
-        childers.appendChild(liEnd)
-        return childers
+        children.appendChild(liEnd)
+        return children
       }
 
       const renderItem = (parentElement: Element, node: Node, depth: number) => {
diff --git a/packages/sandbox/src/tsWorker.ts b/packages/sandbox/src/tsWorker.ts
@@ -41,18 +41,18 @@ export declare class TypeScriptWorker implements ts.LanguageServiceHost {
   ): Promise<ts.TextChange[]>
   getFormattingEditsAfterKeystroke(
     fileName: string,
-    postion: number,
+    position: number,
     ch: string,
     options: ts.FormatCodeOptions
   ): Promise<ts.TextChange[]>
   findRenameLocations(
     fileName: string,
-    positon: number,
+    position: number,
     findInStrings: boolean,
     findInComments: boolean,
     providePrefixAndSuffixTextForRename: boolean
   ): Promise<readonly ts.RenameLocation[] | undefined>
-  getRenameInfo(fileName: string, positon: number, options: ts.RenameInfoOptions): Promise<ts.RenameInfo>
+  getRenameInfo(fileName: string, position: number, options: ts.RenameInfoOptions): Promise<ts.RenameInfo>
   getEmitOutput(fileName: string): Promise<ts.EmitOutput>
   getCodeFixesAtPosition(
     fileName: string,
diff --git a/packages/sandbox/test/defaultCompilerOptions.test.ts b/packages/sandbox/test/defaultCompilerOptions.test.ts
@@ -14,7 +14,7 @@ const fauxMonaco: any = {
 
 describe(getCompilerOptionsFromParams, () => {
   it("ignores compiler flags which are the same as the defaults", () => {
-    // noImplicitReturns=true is the default, and shouldnt be in the object
+    // noImplicitReturns=true is the default, and shouldn't be in the object
     const params = new URLSearchParams("?noImplicitThis=false&noImplicitReturns=true#code/JYOw")
     const defaults = getDefaultSandboxCompilerOptions({ filetype: "js" } as any, fauxMonaco, {
       versionMajorMinor: "4.9",
diff --git a/packages/ts-twoslasher/README.md b/packages/ts-twoslasher/README.md
@@ -370,7 +370,7 @@ Turns to:
 > }
 > ```
 
-#### `cuts_out_unneccessary_code.ts`
+#### `cuts_out_unnecessary_code.ts`
 
 ```ts
 interface IdLabel {
diff --git a/packages/ts-twoslasher/test/fixtures/cuts_out_unnecessary_code.ts b/packages/ts-twoslasher/test/fixtures/cuts_out_unnecessary_code.ts
diff --git a/packages/ts-twoslasher/test/results/cuts_out_unnecessary_code.json b/packages/ts-twoslasher/test/results/cuts_out_unnecessary_code.json
diff --git a/packages/tsconfig-reference/copy/en/options/lib.md b/packages/tsconfig-reference/copy/en/options/lib.md
@@ -12,7 +12,7 @@ You may want to change these for a few reasons:
 - Your runtime platform provides certain JavaScript API objects (maybe through polyfills), but doesn't yet support the full syntax of a given ECMAScript version
 - You have polyfills or native implementations for some, but not all, of a higher level ECMAScript version
 
-In TypeScript 4.5, lib files can be overriden by npm modules, find out more [in the blog](https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/#supporting-lib-from-node_modules).
+In TypeScript 4.5, lib files can be overridden by npm modules, find out more [in the blog](https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/#supporting-lib-from-node_modules).
 
 ### High Level libraries
 
@@ -64,7 +64,7 @@ In TypeScript 4.5, lib files can be overriden by npm modules, find out more [in
 | `ES2020.Symbol.wellknown` |
 | `ES2021.Promise`          |
 | `ES2021.String`           |
-| `ES2021.Weakref`          |
+| `ES2021.WeakRef`          |
 | `ESNext.AsyncIterable`    |
 | `ESNext.Array`            |
 | `ESNext.Intl`             |
diff --git a/packages/typescriptlang-org/src/components/layout/SiteFooter-Customize.tsx b/packages/typescriptlang-org/src/components/layout/SiteFooter-Customize.tsx
@@ -31,7 +31,7 @@ export const Customize = () => {
   const customFontOverride = hasLocalStorage && localStorage.getItem("force-font") || "cascadia"
   const [fontValue, setFont] = useState(customFontOverride)
 
-  // Localstorage: force-dark, force-light, undefined 
+  // LocalStorage: force-dark, force-light, undefined 
   // ->
   // CSS Body class: theme-dark, theme-light, theme-dark | theme-light 
 
@@ -52,7 +52,7 @@ export const Customize = () => {
   }
 
 
-  // Localstorage: undefined, cascadia, cascadia-ligatures, consolas, ...
+  // LocalStorage: undefined, cascadia, cascadia-ligatures, consolas, ...
   // ->
   // CSS Body class: font-cascadia, font-cascadia, font-cascadia-ligatures | font-consolas, ...
 
diff --git a/packages/typescriptlang-org/src/dom.d.ts b/packages/typescriptlang-org/src/dom.d.ts
@@ -6846,7 +6846,7 @@ interface HTMLIFrameElement extends HTMLElement {
      */
     src: string;
     /**
-     * Sets or retrives the content of the page that is to contain.
+     * Sets or retrieves the content of the page that is to contain.
      */
     srcdoc: string;
     /**

Original file line number	Diff line number	Diff line change
`@@ -97,4 +97,4 @@ for (var _i = 0; _i < numbers.length; _i++) {`
`97`	`97`
`98`	`98`	`#### Targeting ECMAScript 2015 and higher`
`99`	`99`
`100`		-When targeting an ECMAScipt 2015-compliant engine, the compiler will generate `for..of` loops to target the built-in iterator implementation in the engine.
	`100`	+When targeting an ECMAScript 2015-compliant engine, the compiler will generate `for..of` loops to target the built-in iterator implementation in the engine.
Original file line number	Diff line number	Diff line change
`@@ -237,7 +237,7 @@ function walk(p) {`
`237`	`237`	`}`
`238`	`238`	```
`239`	`239`
`240`		`-## Relaxing declaration emit visiblity rules`
	`240`	`+## Relaxing declaration emit visibility rules`
`241`	`241`
`242`	`242`	With `import` types available, many of the visibility errors reported during declaration file generation can be handled by the compiler without the need to change the input.
`243`	`243`