From 4ac21966957536d734bb2de87458fcbf89a0561b Mon Sep 17 00:00:00 2001 From: Asaf M <302302302v@gmail.com> Date: Sun, 31 Jul 2022 15:01:19 +0300 Subject: [PATCH] docs: fixed typos (#47008) Used my script: https://github.com/Uziel302/websites-spell-checker/blob/master/mdnversion PR Close #47008 --- .devcontainer/README.md | 2 +- aio/content/guide/dynamic-form.md | 2 +- aio/content/guide/hierarchical-dependency-injection.md | 2 +- aio/content/guide/typed-forms.md | 2 +- packages/compiler-cli/src/ngtsc/incremental/README.md | 2 +- packages/core/test/di/reflective_injector_spec.ts | 2 +- packages/core/test/linker/ng_module_integration_spec.ts | 2 +- packages/zone.js/MODULE.md | 2 +- packages/zone.js/test/browser/browser.spec.ts | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.devcontainer/README.md b/.devcontainer/README.md index 6c93540407d3b..0f36d35c7c085 100644 --- a/.devcontainer/README.md +++ b/.devcontainer/README.md @@ -12,7 +12,7 @@ Info on remote development and developing inside a container with VSCode: _Prerequisite: [Install Docker](https://docs.docker.com/install) on your local environment._ -To get started, read and follow the instuctions in [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers). The [.devcontainer/](.) directory contains pre-configured `devcontainer.json` and `Dockerfile` files, which you can use to set up remote development with a docker container. +To get started, read and follow the instructions in [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers). The [.devcontainer/](.) directory contains pre-configured `devcontainer.json` and `Dockerfile` files, which you can use to set up remote development with a docker container. In a nutshell, you need to: - Install the [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension. diff --git a/aio/content/guide/dynamic-form.md b/aio/content/guide/dynamic-form.md index e3f33686c6534..e6989ea02ed48 100644 --- a/aio/content/guide/dynamic-form.md +++ b/aio/content/guide/dynamic-form.md @@ -162,7 +162,7 @@ The following figure shows the final form. | Steps | Details | |:--- |:--- | -| Different types of forms and control collection | This tutorial shows how to build a questionaire, which is just one kind of dynamic form. The example uses `FormGroup` to collect a set of controls. For an example of a different type of dynamic form, see the section [Creating dynamic forms](guide/reactive-forms#creating-dynamic-forms "Create dynamic forms with arrays") in the Reactive Forms guide. That example also shows how to use `FormArray` instead of `FormGroup` to collect a set of controls. | +| Different types of forms and control collection | This tutorial shows how to build a questionnaire, which is just one kind of dynamic form. The example uses `FormGroup` to collect a set of controls. For an example of a different type of dynamic form, see the section [Creating dynamic forms](guide/reactive-forms#creating-dynamic-forms "Create dynamic forms with arrays") in the Reactive Forms guide. That example also shows how to use `FormArray` instead of `FormGroup` to collect a set of controls. | | Validating user input | The section [Validating form input](guide/reactive-forms#validating-form-input "Basic input validation") introduces the basics of how input validation works in reactive forms.
The [Form validation guide](guide/form-validation "Form validation guide") covers the topic in more depth. | diff --git a/aio/content/guide/hierarchical-dependency-injection.md b/aio/content/guide/hierarchical-dependency-injection.md index 8c98ba8f33a63..612845220ae71 100644 --- a/aio/content/guide/hierarchical-dependency-injection.md +++ b/aio/content/guide/hierarchical-dependency-injection.md @@ -173,7 +173,7 @@ If the component's injector lacks the provider, it passes the request up to its The requests keep forwarding up until Angular finds an injector that can handle the request or runs out of ancestor `ElementInjector` hierarchies. -If Angular doesn't find the provider in any `ElementInjector` hierarchiess, it goes back to the element where the request originated and looks in the `ModuleInjector` hierarchy. +If Angular doesn't find the provider in any `ElementInjector` hierarchies, it goes back to the element where the request originated and looks in the `ModuleInjector` hierarchy. If Angular still doesn't find the provider, it throws an error. If you have registered a provider for the same DI token at different levels, the first one Angular encounters is the one it uses to resolve the dependency. diff --git a/aio/content/guide/typed-forms.md b/aio/content/guide/typed-forms.md index 759699d84c819..f0fe691cfc9ae 100644 --- a/aio/content/guide/typed-forms.md +++ b/aio/content/guide/typed-forms.md @@ -72,7 +72,7 @@ email.reset(); console.log(email.value); // null ``` -TypeScript will enforce that you always handle the possibility that the control has become `null`. If you want to make this control non-nullable, you may use the `nonNullable` option. This will cause the control to reset to its intial value, instead of `null`: +TypeScript will enforce that you always handle the possibility that the control has become `null`. If you want to make this control non-nullable, you may use the `nonNullable` option. This will cause the control to reset to its initial value, instead of `null`: ```ts const email = new FormControl('angularrox@gmail.com', {nonNullable: true}); diff --git a/packages/compiler-cli/src/ngtsc/incremental/README.md b/packages/compiler-cli/src/ngtsc/incremental/README.md index a5ed27edd879b..d09a0c2319cf1 100644 --- a/packages/compiler-cli/src/ngtsc/incremental/README.md +++ b/packages/compiler-cli/src/ngtsc/incremental/README.md @@ -274,7 +274,7 @@ the previous compilation failed, such information may be unreliable. In theory, the compiler could simply not perform incremental compilation on top of a broken build, and assume that it must redo all analysis and re-emit all files, but this would result in -devestatingly poor performance for common developer workflows that rely on automatically running +devastatingly poor performance for common developer workflows that rely on automatically running builds and/or tests on every change. The compiler must deal with such scenarios more gracefully. ngtsc solves this problem by always performing its incremental steps from a "last known good" diff --git a/packages/core/test/di/reflective_injector_spec.ts b/packages/core/test/di/reflective_injector_spec.ts index f51e6cf50095a..03f011d6de586 100644 --- a/packages/core/test/di/reflective_injector_spec.ts +++ b/packages/core/test/di/reflective_injector_spec.ts @@ -391,7 +391,7 @@ describe('instantiate', () => { }); }); -describe('depedency resolution', () => { +describe('dependency resolution', () => { describe('@Self()', () => { it('should return a dependency from self', () => { const inj = ReflectiveInjector.resolveAndCreate([ diff --git a/packages/core/test/linker/ng_module_integration_spec.ts b/packages/core/test/linker/ng_module_integration_spec.ts index 2ed0db8217c84..888652f427e58 100644 --- a/packages/core/test/linker/ng_module_integration_spec.ts +++ b/packages/core/test/linker/ng_module_integration_spec.ts @@ -948,7 +948,7 @@ describe('NgModule', () => { }); }); - describe('depedency resolution', () => { + describe('dependency resolution', () => { describe('@Self()', () => { it('should return a dependency from self', () => { const inj = createInjector([ diff --git a/packages/zone.js/MODULE.md b/packages/zone.js/MODULE.md index fef300bb9291f..a07cb88274892 100644 --- a/packages/zone.js/MODULE.md +++ b/packages/zone.js/MODULE.md @@ -100,7 +100,7 @@ This package will provide following functionality. console.log('is MyError instanceof Error', (myError instanceof Error)); ``` - without `zone-error` patch, the example above will output `false`, with the patch, the reuslt will be `true`. + without `zone-error` patch, the example above will output `false`, with the patch, the result will be `true`. 2. ZoneJsInternalStackFrames: remove zone.js stack from `stackTrace`, and add `zone` information. Without this patch, a lot of `zone.js` invocation stack will be shown in stack frames. diff --git a/packages/zone.js/test/browser/browser.spec.ts b/packages/zone.js/test/browser/browser.spec.ts index d1c3220303bf8..065e7d3fc0d0e 100644 --- a/packages/zone.js/test/browser/browser.spec.ts +++ b/packages/zone.js/test/browser/browser.spec.ts @@ -3141,7 +3141,7 @@ describe('Zone', function() { }); // TODO: Re-enable via https://github.com/angular/angular/pull/41526 - xdescribe('unhandle promise rejection', () => { + xdescribe('unhandled promise rejection', () => { const AsyncTestZoneSpec = (Zone as any)['AsyncTestZoneSpec']; const asyncTest = function(testFn: Function) { return (done: Function) => {