refactor: fix a number of typos throughout the codebase (#55018)

ranma42 · dylhunn · commit f3b624553a44 · 2024-03-27T10:54:31.000-07:00
Fix some typos detected using spellchecking tools, both in documentation and in code (comments, identifiers). PR Close #55018
diff --git a/adev/src/app/editor/README.md b/adev/src/app/editor/README.md
@@ -115,7 +115,7 @@ The following steps are executed on project change:
 5. The previous project dependencies are compared with the new project dependencies.
    1. If there are differences, a `npm install` is triggered, hiding the preview and going to the install loading step.
    2. If there are no differences, the project is ready.
-6. Some states are resetted, for example the "reveal answer" state if the previous project was in the "reveal answer" state.
+6. Some states are reset, for example the "reveal answer" state if the previous project was in the "reveal answer" state.
 
 ## Components and services
 
@@ -200,7 +200,7 @@ Responsible for handling the download button in the embedded editor, fetching th
 
 #### [`AlertManager`](./alert-manager.service.ts)
 
-Manage the alerts displayed in the embedded editor, being the out of memory alert when multiple tabs are opened, and unsupported enviroments alerts.
+Manage the alerts displayed in the embedded editor, being the out of memory alert when multiple tabs are opened, and unsupported environments alerts.
 
 #### [`TypingsLoader`](./typings-loader.service.ts)
 
diff --git a/adev/src/app/features/tutorial/tutorial.component.spec.ts b/adev/src/app/features/tutorial/tutorial.component.spec.ts
@@ -41,7 +41,7 @@ class FakeDocViewer {
   @Input('documentFilePath') documentFilePath: string | undefined;
 }
 
-// TODO: export this class, it's a helpfull mock we could you on other tests.
+// TODO: export this class, it's a helpful mock we could you on other tests.
 class FakeNodeRuntimeSandbox {
   loadingStep = signal(0);
   previewUrl$ = of();
diff --git a/adev/src/content/reference/migrations/control-flow.md b/adev/src/content/reference/migrations/control-flow.md
@@ -3,7 +3,7 @@
 
 [Control flow syntax](guide/templates/control-flow) is available from Angular 17 and simplified way to use the control-flow directives like *ngFor, *ngIf and *ngSwitch. 
 
-The new syntax is baked into the template, so you don't need to import `CommonModule` anymore. But wait there is more to it, there is an migration availble for migrating all your old code to use new Control Flow Syntax with Angular 17 release. Run the schematic with the following command:
+The new syntax is baked into the template, so you don't need to import `CommonModule` anymore. But wait there is more to it, there is an migration available for migrating all your old code to use new Control Flow Syntax with Angular 17 release. Run the schematic with the following command:
 
 <docs-code language="shell">
 
diff --git a/aio/content/examples/rx-library/e2e/src/app.e2e-spec.ts b/aio/content/examples/rx-library/e2e/src/app.e2e-spec.ts
@@ -1,6 +1,6 @@
 /*
  * This example project is special in that it is not a cli app. To run tests appropriate for this
- * project, the test command is overwritten in `aio/content/examples/rx-libary/example-config.json`.
+ * project, the test command is overwritten in `aio/content/examples/rx-library/example-config.json`.
  *
  * This is an empty placeholder file to ensure that `aio/tools/examples/run-example-e2e.mjs` runs
  * tests for this project.
diff --git a/aio/content/guide/devtools.md b/aio/content/guide/devtools.md
@@ -259,7 +259,7 @@ Then, import the file in the initial view of the profiler by clicking the **Choo
 
 ### View the injector hierarchy of your application
 
-The **Injector Tree** tab lets you explore the structure of the Injectors configured in your application. Here you will see two trees representing the [injector hiearchy](guide/hierarchical-dependency-injection) of your application. One tree is your environment hierarchy, the other is your element hierachy.
+The **Injector Tree** tab lets you explore the structure of the Injectors configured in your application. Here you will see two trees representing the [injector hierarchy](guide/hierarchical-dependency-injection) of your application. One tree is your environment hierarchy, the other is your element hierarchy.
 
 <div class="lightbox">
 
@@ -269,7 +269,7 @@ The **Injector Tree** tab lets you explore the structure of the Injectors config
 
 ### Visualize resolution paths
 
-When a specific injector is selected, the path that Angular's depenedency injection algorithm traverses from that injector to the root is highlighted. For element injectors, this includes highlighting the environment injectors that the dependency injection algorithm jumps to when a dependency cannot be resolved in the element hierarchy. See [resolution rules](guide/hierarchical-dependency-injection#resolution-rules) for more details about how Angular resolves resolution paths.
+When a specific injector is selected, the path that Angular's dependency injection algorithm traverses from that injector to the root is highlighted. For element injectors, this includes highlighting the environment injectors that the dependency injection algorithm jumps to when a dependency cannot be resolved in the element hierarchy. See [resolution rules](guide/hierarchical-dependency-injection#resolution-rules) for more details about how Angular resolves resolution paths.
 
 <div class="lightbox">
 
diff --git a/aio/content/guide/esbuild.md b/aio/content/guide/esbuild.md
@@ -41,7 +41,7 @@ If the `application` builder is difficult for your project to adopt, `browser-es
 
 A builder named `browser-esbuild` is available within the `@angular-devkit/build-angular` package that is present in an Angular CLI generated application. The builder is a drop-in replacement for the existing `browser` builder that provides the preexisting browser application build system.
 
-The compatiblity option was implemented to minimize the amount of changes necessary to initially migrate your applications.
+The compatibility option was implemented to minimize the amount of changes necessary to initially migrate your applications.
 This is provided via an alternate builder (`browser-esbuild`).
 You can update the `build` target for any application target to migrate to the new build system.
 
diff --git a/packages/common/http/test/fetch_spec.ts b/packages/common/http/test/fetch_spec.ts
@@ -233,7 +233,7 @@ describe('FetchBackend', async () => {
 
   it('handles a blob with a mime type', async () => {
     const promise = trackEvents(backend.handle(TEST_POST.clone({responseType: 'blob'})));
-    const type = 'aplication/pdf';
+    const type = 'application/pdf';
     fetchMock.mockFlush(HttpStatusCode.Ok, 'OK', new Blob(), {'Content-Type': type});
     const events = await promise;
     expect(events.length).toBe(2);
diff --git a/packages/compiler-cli/src/ngtsc/typecheck/src/type_check_block.ts b/packages/compiler-cli/src/ngtsc/typecheck/src/type_check_block.ts
@@ -1445,7 +1445,7 @@ class TcbIfOp extends TcbOp {
         expression = expressionScope.resolve(branch.expressionAlias);
       }
 
-      // The expressions of the preceeding branches have to be negated
+      // The expressions of the preceding branches have to be negated
       // (e.g. `expr` becomes `!(expr)`) when comparing in the guard, except
       // for the branch's own expression which is preserved as is.
       const comparisonExpression = i === index ?
@@ -1486,7 +1486,7 @@ class TcbSwitchOp extends TcbOp {
     const comparisonExpression = tcbExpression(this.block.expression, this.tcb, this.scope);
     markIgnoreDiagnostics(comparisonExpression);
 
-    // Wrap the comparisson expression in parentheses so we don't ignore
+    // Wrap the comparison expression in parentheses so we don't ignore
     // diagnostics when comparing incompatible types (see #52315).
     const expression = ts.factory.createParenthesizedExpression(comparisonExpression);
     const root = this.generateCase(0, expression, null);
@@ -2326,13 +2326,13 @@ class TcbExpressionTranslator {
    * context). This method assists in resolving those.
    */
   protected resolve(ast: AST): ts.Expression|null {
-    // TODO: this is actually a bug, because `ImpliticReceiver` extends `ThisReceiver`. Consider a
+    // TODO: this is actually a bug, because `ImplicitReceiver` extends `ThisReceiver`. Consider a
     // case when the explicit `this` read is inside a template with a context that also provides the
     // variable name being read:
     // ```
     // <ng-template let-a>{{this.a}}</ng-template>
     // ```
-    // Clearly, `this.a` should refer to the class property `a`. However, becuase of this code,
+    // Clearly, `this.a` should refer to the class property `a`. However, because of this code,
     // `this.a` will refer to `let-a` on the template context.
     //
     // Note that the generated code is actually consistent with this bug. To fix it, we have to:
diff --git a/packages/compiler-cli/test/ngtsc/ngtsc_spec.ts b/packages/compiler-cli/test/ngtsc/ngtsc_spec.ts
@@ -9328,8 +9328,8 @@ function allTests(os: string) {
                 kind: ts.SyntaxKind.MultiLineCommentTrivia,
                 text: `*
                     * @fileoverview Closure comment
-                    * @supress bla1
-                    * @supress bla2
+                    * @suppress bla1
+                    * @suppress bla2
                   `,
                 pos: -1,
                 end: -1,
diff --git a/packages/compiler/src/render3/view/t2_binder.ts b/packages/compiler/src/render3/view/t2_binder.ts
@@ -908,9 +908,9 @@ export class R3BoundTarget<DirectiveT extends DirectiveMeta> implements BoundTar
   private findEntityInScope(rootNode: ScopedNode, name: string): Reference|Variable|null {
     const entities = this.getEntitiesInScope(rootNode);
 
-    for (const entitity of entities) {
-      if (entitity.name === name) {
-        return entitity;
+    for (const entity of entities) {
+      if (entity.name === name) {
+        return entity;
       }
     }
 
diff --git a/packages/compiler/src/shadow_css.ts b/packages/compiler/src/shadow_css.ts
@@ -155,7 +155,7 @@ export class ShadowCss {
         comments.push(m);
       } else {
         // Replace non hash comments with empty lines.
-        // This is done so that we do not leak any senstive data in comments.
+        // This is done so that we do not leak any sensitive data in comments.
         const newLinesMatches = m.match(_newLinesRe);
         comments.push((newLinesMatches?.join('') ?? '') + '\n');
       }
diff --git a/packages/compiler/src/template/pipeline/ir/src/ops/update.ts b/packages/compiler/src/template/pipeline/ir/src/ops/update.ts
@@ -118,8 +118,8 @@ export interface BindingOp extends Op<UpdateOp> {
   /**
    * Whether the binding is a TextAttribute (e.g. `some-attr="some-value"`).
    *
-   * This needs to be tracked for compatiblity with `TemplateDefinitionBuilder` which treats `style`
-   * and `class` TextAttributes differently from `[attr.style]` and `[attr.class]`.
+   * This needs to be tracked for compatibility with `TemplateDefinitionBuilder` which treats
+   * `style` and `class` TextAttributes differently from `[attr.style]` and `[attr.class]`.
    */
   isTextAttribute: boolean;
 
@@ -507,8 +507,8 @@ export interface AttributeOp extends Op<UpdateOp> {
   /**
    * Whether the binding is a TextAttribute (e.g. `some-attr="some-value"`).
    *
-   * This needs to be tracked for compatiblity with `TemplateDefinitionBuilder` which treats `style`
-   * and `class` TextAttributes differently from `[attr.style]` and `[attr.class]`.
+   * This needs to be tracked for compatibility with `TemplateDefinitionBuilder` which treats
+   * `style` and `class` TextAttributes differently from `[attr.style]` and `[attr.class]`.
    */
   isTextAttribute: boolean;
 
diff --git a/packages/compiler/src/template/pipeline/src/phases/naming.ts b/packages/compiler/src/template/pipeline/src/phases/naming.ts
@@ -162,7 +162,7 @@ function getVariableName(
         break;
       case ir.SemanticVariableKind.Identifier:
         if (unit.job.compatibility === ir.CompatibilityMode.TemplateDefinitionBuilder) {
-          // TODO: Prefix increment and `_r` are for compatiblity with the old naming scheme.
+          // TODO: Prefix increment and `_r` are for compatibility with the old naming scheme.
           // This has the potential to cause collisions when `ctx` is the identifier, so we need a
           // special check for that as well.
           const compatPrefix = variable.identifier === 'ctx' ? 'i' : '';
diff --git a/packages/compiler/src/template/pipeline/src/phases/propagate_i18n_blocks.ts b/packages/compiler/src/template/pipeline/src/phases/propagate_i18n_blocks.ts
@@ -90,7 +90,7 @@ function wrapTemplateWithI18n(unit: ViewCompilationUnit, parentI18n: ir.I18nStar
   if (unit.create.head.next?.kind !== ir.OpKind.I18nStart) {
     const id = unit.job.allocateXrefId();
     ir.OpList.insertAfter(
-        // Nested ng-template i18n start/end ops should not recieve source spans.
+        // Nested ng-template i18n start/end ops should not receive source spans.
         ir.createI18nStartOp(id, parentI18n.message, parentI18n.root, null), unit.create.head);
     ir.OpList.insertBefore(ir.createI18nEndOp(id, null), unit.create.tail);
   }
diff --git a/packages/compiler/src/template/pipeline/src/phases/wrap_icus.ts b/packages/compiler/src/template/pipeline/src/phases/wrap_icus.ts
@@ -27,7 +27,7 @@ export function wrapI18nIcus(job: CompilationJob): void {
         case ir.OpKind.IcuStart:
           if (currentI18nOp === null) {
             addedI18nId = job.allocateXrefId();
-            // ICU i18n start/end ops should not recieve source spans.
+            // ICU i18n start/end ops should not receive source spans.
             ir.OpList.insertBefore<ir.CreateOp>(
                 ir.createI18nStartOp(addedI18nId, op.message, undefined, null), op);
           }
diff --git a/packages/core/src/render3/debug/framework_injector_profiler.ts b/packages/core/src/render3/debug/framework_injector_profiler.ts
@@ -203,7 +203,7 @@ function handleInstanceCreatedByInjectorEvent(
   const environmentInjector: EnvironmentInjector|null =
       context.injector.get(EnvironmentInjector, null, {optional: true});
   // Standalone components should have an environment injector. If one cannot be
-  // found we may be in a test case for low level functionality that did not explictly
+  // found we may be in a test case for low level functionality that did not explicitly
   // setup this injector. In those cases, we simply ignore this event.
   if (environmentInjector === null) {
     return;
diff --git a/packages/core/src/render3/util/injector_discovery_utils.ts b/packages/core/src/render3/util/injector_discovery_utils.ts
@@ -608,7 +608,7 @@ function getInjectorParent(injector: Injector): Injector|null {
     // todo(aleksanderbodurri): ideally nothing in packages/core should deal
     // directly with router concerns. Refactor this so that we can make the jump from
     // NodeInjector -> OutletInjector -> NodeInjector
-    // without explictly relying on types contracts from packages/router
+    // without explicitly relying on types contracts from packages/router
     const injectorParent = (chainedInjector.injector as any)?.parent as Injector;
 
     if (injectorParent instanceof NodeInjector) {
diff --git a/packages/core/testing/src/component_fixture.ts b/packages/core/testing/src/component_fixture.ts
@@ -334,7 +334,7 @@ export class PseudoApplicationComponentFixture<T> extends ComponentFixture<T> {
               (this.componentRef.hostView as any).notifyErrorHandler,
           );
         } catch (e: unknown) {
-          // If an error ocurred during change detection, remove the test view from the application
+          // If an error occurred during change detection, remove the test view from the application
           // ref tracking. Note that this isn't exactly desirable but done this way because of how
           // things used to work with `autoDetect` and uncaught errors. Ideally we would surface
           // this error to the error handler instead and continue refreshing the view like
diff --git a/packages/forms/test/value_accessor_integration_spec.ts b/packages/forms/test/value_accessor_integration_spec.ts
@@ -1070,7 +1070,7 @@ describe('value accessors', () => {
           fixture = initTest(CvaWithDisabledStateForm, CvaWithDisabledState);
         });
 
-        it('sets the disabled state when the control is initally disabled', () => {
+        it('sets the disabled state when the control is initially disabled', () => {
           fixture.componentInstance.form = new FormGroup({
             'login': new FormControl({value: 'aa', disabled: true}),
           });
@@ -1083,7 +1083,7 @@ describe('value accessors', () => {
               .toContain('DISABLED');
         });
 
-        it('sets the enabled state when the control is initally enabled', () => {
+        it('sets the enabled state when the control is initially enabled', () => {
           fixture.componentInstance.form = new FormGroup({
             'login': new FormControl({value: 'aa', disabled: false}),
           });
@@ -1210,7 +1210,7 @@ describe('value accessors in reactive forms with custom options', () => {
       fixture = initTest(CvaWithDisabledStateForm, CvaWithDisabledState);
     });
 
-    it('does not set the enabled state when the control is initally enabled', () => {
+    it('does not set the enabled state when the control is initially enabled', () => {
       fixture.componentInstance.form = new FormGroup({
         'login': new FormControl({value: 'aa', disabled: false}),
       });
diff --git a/packages/language-service/src/completions.ts b/packages/language-service/src/completions.ts
@@ -132,11 +132,11 @@ export class CompletionBuilder<N extends TmplAstNode|AST> {
         length: this.node.name.length,
       }
     };
-    let competionKeywords: string[] = [...blocksWithParens, ...blocksWithoutParens];
+    let completionKeywords: string[] = [...blocksWithParens, ...blocksWithoutParens];
     if (this.nodeParent instanceof SwitchBlock) {
-      competionKeywords = ['case', 'default'];
+      completionKeywords = ['case', 'default'];
     }
-    const completionEntries: ts.CompletionEntry[] = competionKeywords.map(
+    const completionEntries: ts.CompletionEntry[] = completionKeywords.map(
         name => ({
           name,
           sortText: `${AsciiSortPriority.First}${name}`,
diff --git a/packages/language-service/test/legacy/mock_host.ts b/packages/language-service/test/legacy/mock_host.ts
@@ -275,7 +275,7 @@ export class MockService {
 }
 
 /**
- * Replace at most one occurence that matches `regex` in the specified
+ * Replace at most one occurrence that matches `regex` in the specified
  * `searchText` with the specified `replaceText`. Throw an error if there is
  * more than one occurrence.
  */
diff --git a/packages/language-service/test/ts_utils_spec.ts b/packages/language-service/test/ts_utils_spec.ts
@@ -151,7 +151,7 @@ describe('TS util', () => {
             false);
       });
 
-      it('creates a non-existant property', () => {
+      it('creates a non-existent property', () => {
         const obj = updateObjectValueForKey(oldObj, 'newKey', valueAppenderFn);
         expect(print(obj)).toBe('{ foo: "bar", newKey: "baz" }');
       });
diff --git a/packages/service-worker/worker/test/idle_spec.ts b/packages/service-worker/worker/test/idle_spec.ts
@@ -176,7 +176,7 @@ import {envIsSupported} from '../testing/utils';
       const forthTrigger = idle.trigger();
 
       // Finally, advance the clock beyond `maxDelay` (3000) from the first trigger, but not beyond
-      // the timeout for the forth. This should cause the task to be executed nontheless.
+      // the timeout for the forth. This should cause the task to be executed nonetheless.
       scope.advance(3);
       await Promise.all([thirdTrigger, forthTrigger]);
 
diff --git a/packages/zone.js/NON-STANDARD-APIS.md b/packages/zone.js/NON-STANDARD-APIS.md
@@ -186,7 +186,7 @@ In electron, we patched the following APIs with `zone.js`
 
 1. Browser API
 2. NodeJS
-3. Electorn Native API
+3. Electron Native API
 
 ## Usage.
 
diff --git a/packages/zone.js/test/browser/browser.spec.ts b/packages/zone.js/test/browser/browser.spec.ts
@@ -799,7 +799,7 @@ describe('Zone', function() {
                expect(testFn).not.toThrow();
              }));
 
-          it('window.onerror callback signiture should be (message, source, lineno, colno, error)',
+          it('window.onerror callback signature should be (message, source, lineno, colno, error)',
              ifEnvSupportsWithDone(canPatchOnProperty(window, 'onerror'), function(done: DoneFn) {
                const oriOnError = window.onerror;
                let testError = new Error('testError');
@@ -1320,7 +1320,7 @@ describe('Zone', function() {
          }));
 
 
-      it('should support add multipe listeners with AddEventListenerOptions once setting and same capture after normal listener',
+      it('should support add multiple listeners with AddEventListenerOptions once setting and same capture after normal listener',
          ifEnvSupports(supportEventListenerOptions, function() {
            let logs: string[] = [];
 
@@ -1342,7 +1342,7 @@ describe('Zone', function() {
            expect(logs).toEqual(['click']);
          }));
 
-      it('should support add multipe listeners with AddEventListenerOptions once setting and mixed capture after normal listener',
+      it('should support add multiple listeners with AddEventListenerOptions once setting and mixed capture after normal listener',
          ifEnvSupports(supportEventListenerOptions, function() {
            let logs: string[] = [];
 
@@ -1364,7 +1364,7 @@ describe('Zone', function() {
            expect(logs).toEqual(['click']);
          }));
 
-      it('should support add multipe listeners with AddEventListenerOptions once setting before normal listener',
+      it('should support add multiple listeners with AddEventListenerOptions once setting before normal listener',
          ifEnvSupports(supportEventListenerOptions, function() {
            let logs: string[] = [];
 
@@ -1387,7 +1387,7 @@ describe('Zone', function() {
            expect(logs).toEqual(['click']);
          }));
 
-      it('should support add multipe listeners with AddEventListenerOptions once setting with same capture before normal listener',
+      it('should support add multiple listeners with AddEventListenerOptions once setting with same capture before normal listener',
          ifEnvSupports(supportEventListenerOptions, function() {
            let logs: string[] = [];
 
@@ -1410,7 +1410,7 @@ describe('Zone', function() {
            expect(logs).toEqual(['click']);
          }));
 
-      it('should support add multipe listeners with AddEventListenerOptions once setting with mixed capture before normal listener',
+      it('should support add multiple listeners with AddEventListenerOptions once setting with mixed capture before normal listener',
          ifEnvSupports(supportEventListenerOptions, function() {
            let logs: string[] = [];
 

Original file line number	Diff line number	Diff line change
`@@ -41,7 +41,7 @@ class FakeDocViewer {`
`41`	`41`	`@Input('documentFilePath') documentFilePath: string \| undefined;`
`42`	`42`	`}`
`43`	`43`
`44`		`-// TODO: export this class, it's a helpfull mock we could you on other tests.`
	`44`	`+// TODO: export this class, it's a helpful mock we could you on other tests.`
`45`	`45`	`class FakeNodeRuntimeSandbox {`
`46`	`46`	`loadingStep = signal(0);`
`47`	`47`	`previewUrl$ = of();`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`/*`
`2`	`2`	`* This example project is special in that it is not a cli app. To run tests appropriate for this`
`3`		- * project, the test command is overwritten in `aio/content/examples/rx-libary/example-config.json`.
	`3`	+ * project, the test command is overwritten in `aio/content/examples/rx-library/example-config.json`.
`4`	`4`	`*`
`5`	`5`	* This is an empty placeholder file to ensure that `aio/tools/examples/run-example-e2e.mjs` runs
`6`	`6`	`* tests for this project.`
Original file line number	Diff line number	Diff line change
`@@ -908,9 +908,9 @@ export class R3BoundTarget<DirectiveT extends DirectiveMeta> implements BoundTar`
`908`	`908`	`private findEntityInScope(rootNode: ScopedNode, name: string): Reference\|Variable\|null {`
`909`	`909`	`const entities = this.getEntitiesInScope(rootNode);`
`910`	`910`
`911`		`- for (const entitity of entities) {`
`912`		`- if (entitity.name === name) {`
`913`		`- return entitity;`
	`911`	`+ for (const entity of entities) {`
	`912`	`+ if (entity.name === name) {`
	`913`	`+ return entity;`
`914`	`914`	`}`
`915`	`915`	`}`
`916`	`916`