docs: remove duplicate words

aanchal88 · clydin · commit efeae1e1f195 · 2023-08-04T14:49:14.000-04:00
diff --git a/.github/SAVED_REPLIES.md b/.github/SAVED_REPLIES.md
@@ -84,7 +84,7 @@ Hello, errors like `Error encountered resolving symbol values statically` mean t
 Angular CLI always runs *some* static analysis, even in JIT mode, in order to discover lazy-loaded routes.
 This may cause a lot of static analysis errors to surface when importing your project into the CLI, or upgrading for older versions where we didn't run this kind of analysis.
 
-Below are good resources on how to to debug these errors:
+Below are good resources on how to debug these errors:
 - https://gist.github.com/chuckjaz/65dcc2fd5f4f5463e492ed0cb93bca60
 - https://github.com/rangle/angular-2-aot-sandbox#aot-dos-and-donts
 
diff --git a/docs/specifications/schematic-prompts.md b/docs/specifications/schematic-prompts.md
@@ -56,7 +56,7 @@ Prompts have several different types which provide the ability to display an inp
 - `input` - textual input; ideal for string or number options
 - `list` - a predefined set of items which may be selected
 
-When using the _shorthand_ form, the most appropriate type will automatically be selected based on the property's schema. In the example, the `name` prompt will use an `input` type because it it is a `string` property. The `useColor` prompt will use a `confirmation` type because it is a boolean property with `yes` corresponding to `true` and `no` corresponding to `false`.
+When using the _shorthand_ form, the most appropriate type will automatically be selected based on the property's schema. In the example, the `name` prompt will use an `input` type because it is a `string` property. The `useColor` prompt will use a `confirmation` type because it is a boolean property with `yes` corresponding to `true` and `no` corresponding to `false`.
 
 It is also important that the response from the user conforms to the contraints of the property. By specifying constraints using the JSON schema, the prompt runtime will automatically validate the response provided by the user. If the value is not acceptable, the user will be asked to enter a new value. This ensures that any values passed to the schematic will meet the expectations of the schematic's implementation and removes the need to add additional checks within the schematic's code.
 
diff --git a/packages/angular_devkit/architect/testing/test-project-host.ts b/packages/angular_devkit/architect/testing/test-project-host.ts
@@ -74,7 +74,7 @@ export class TestProjectHost extends NodeJsSyncHost {
         ),
       );
 
-    // Find a unique folder that we can write to to use as current root.
+    // Find a unique folder that we can write to use as current root.
     return this.findUniqueFolderPath().pipe(
       // Save the path and create a scoped host for it.
       tap((newFolderPath) => {
diff --git a/packages/angular_devkit/build_angular/src/builders/browser/specs/base-href_spec.ts b/packages/angular_devkit/build_angular/src/builders/browser/specs/base-href_spec.ts
@@ -61,7 +61,7 @@ describe('Browser Builder base href', () => {
     await run.stop();
   });
 
-  it('should insert base href in the the correct position', async () => {
+  it('should insert base href in the correct position', async () => {
     host.writeMultipleFiles({
       'src/index.html': tags.oneLine`
         <html><head><meta charset="UTF-8"></head>
diff --git a/packages/schematics/angular/third_party/github.com/Microsoft/TypeScript/lib/typescript.d.ts b/packages/schematics/angular/third_party/github.com/Microsoft/TypeScript/lib/typescript.d.ts
@@ -5595,7 +5595,7 @@ declare namespace ts {
          * When targetSource file is specified, emits the files corresponding to that source file,
          * otherwise for the whole program.
          * In case of EmitAndSemanticDiagnosticsBuilderProgram, when targetSourceFile is specified,
-         * it is assumed that that file is handled from affected file list. If targetSourceFile is not specified,
+         * it is assumed that file is handled from affected file list. If targetSourceFile is not specified,
          * it will only emit all the affected files instead of whole program
          *
          * The first of writeFile if provided, writeFile of BuilderProgramHost if provided, writeFile of compiler host
@@ -7270,4 +7270,4 @@ declare namespace ts {
      */
     function transform<T extends Node>(source: T | T[], transformers: TransformerFactory<T>[], compilerOptions?: CompilerOptions): TransformationResult<T>;
 }
-export = ts;
+export = ts;

Original file line number	Diff line number	Diff line change
`@@ -5595,7 +5595,7 @@ declare namespace ts {`
`5595`	`5595`	`* When targetSource file is specified, emits the files corresponding to that source file,`
`5596`	`5596`	`* otherwise for the whole program.`
`5597`	`5597`	`* In case of EmitAndSemanticDiagnosticsBuilderProgram, when targetSourceFile is specified,`
`5598`		`- * it is assumed that that file is handled from affected file list. If targetSourceFile is not specified,`
	`5598`	`+ * it is assumed that file is handled from affected file list. If targetSourceFile is not specified,`
`5599`	`5599`	`* it will only emit all the affected files instead of whole program`
`5600`	`5600`	`*`
`5601`	`5601`	`* The first of writeFile if provided, writeFile of BuilderProgramHost if provided, writeFile of compiler host`
`@@ -7270,4 +7270,4 @@ declare namespace ts {`
`7270`	`7270`	`*/`
`7271`	`7271`	`function transform<T extends Node>(source: T \| T[], transformers: TransformerFactory<T>[], compilerOptions?: CompilerOptions): TransformationResult<T>;`
`7272`	`7272`	`}`
`7273`		`-export = ts;`
	`7273`	`+export = ts;`