diff --git a/adev/README.md b/adev/README.md index 08ab121e9fe..6335c24805c 100644 --- a/adev/README.md +++ b/adev/README.md @@ -6,7 +6,7 @@ The content is written primarily in Markdown format located in `src/content`. Fo ## Local Development -For local development, [yarn](https://yarnpkg.com/) is the preferred package manager. You can setup a local environment with the following commands +For local development, [yarn](https://yarnpkg.com/) is the preferred package manager. You can set up a local environment with the following commands : ```bash diff --git a/adev/src/content/best-practices/runtime-performance/zone-pollution.md b/adev/src/content/best-practices/runtime-performance/zone-pollution.md index 8c0adf32a84..bf8ceb13d32 100644 --- a/adev/src/content/best-practices/runtime-performance/zone-pollution.md +++ b/adev/src/content/best-practices/runtime-performance/zone-pollution.md @@ -35,7 +35,7 @@ class AppComponent implements OnInit { The preceding snippet instructs Angular to call `setInterval` outside the Angular Zone and skip running change detection after `pollForUpdates` runs. -Third-party libraries commonly trigger unnecessary change detection cycles when their APIs are invoked within the Angular zone. This phenomenon particularly affects libraries that setup event listeners or initiate other tasks (such as timers, XHR requests, etc.). Avoid these extra cycles by calling library APIs outside the Angular zone: +Third-party libraries commonly trigger unnecessary change detection cycles when their APIs are invoked within the Angular zone. This phenomenon particularly affects libraries that set up event listeners or initiate other tasks (such as timers, XHR requests, etc.). Avoid these extra cycles by calling library APIs outside the Angular zone: import { Component, NgZone, OnInit } from '@angular/core'; diff --git a/adev/src/content/guide/templates/two-way-binding.md b/adev/src/content/guide/templates/two-way-binding.md index 610b0911755..c3380685614 100644 --- a/adev/src/content/guide/templates/two-way-binding.md +++ b/adev/src/content/guide/templates/two-way-binding.md @@ -36,7 +36,7 @@ To use two-way binding with native form controls, you need to: 1. Use the `ngModel` directive with the two-way binding syntax (e.g., `[(ngModel)]`) 1. Assign it the state that you want it to update (e.g., `firstName`) -Once that is setup, Angular will ensure that any updates in the text input will reflect correctly inside of the component state! +Once that is set up, Angular will ensure that any updates in the text input will reflect correctly inside of the component state! Learn more about [`NgModel`](guide/directives#displaying-and-updating-properties-with-ngmodel) in the official docs. diff --git a/adev/src/content/introduction/installation.md b/adev/src/content/introduction/installation.md index a785c7409f9..fa41e5866f9 100644 --- a/adev/src/content/introduction/installation.md +++ b/adev/src/content/introduction/installation.md @@ -13,7 +13,7 @@ If you just want to play around with Angular in your browser without setting up -## Setup a new project locally +## Set up a new project locally If you're starting a new project, you'll most likely want to create a local project so that you can use tooling such as Git. diff --git a/adev/src/content/reference/errors/NG0403.md b/adev/src/content/reference/errors/NG0403.md index fd54ce65b4c..a78c1d99cea 100644 --- a/adev/src/content/reference/errors/NG0403.md +++ b/adev/src/content/reference/errors/NG0403.md @@ -35,7 +35,7 @@ platformBrowser().bootstrapModule(AppModule); ## Debugging the error -Please make sure that the NgModule that is used for bootstrapping is setup correctly: +Please make sure that the NgModule that is used for bootstrapping is set up correctly: - either the `bootstrap` property exists (and contains a non-empty array) in the `@NgModule` annotation - or the `ngDoBootstrap` method exists on the NgModule class diff --git a/adev/src/content/tools/cli/end-to-end.md b/adev/src/content/tools/cli/end-to-end.md index 00d2350885f..b5a7f84caa7 100644 --- a/adev/src/content/tools/cli/end-to-end.md +++ b/adev/src/content/tools/cli/end-to-end.md @@ -2,7 +2,7 @@ End-to-end or (E2E) testing is a form of testing used to assert your entire application works as expected from start to finish or _"end-to-end"_. E2E testing differs from unit testing in that it is completely decoupled from the underlying implementation details of your code. It is typically used to validate an application in a way that mimics the way a user would interact with it. This page serves as a guide to getting started with end-to-end testing in Angular using the Angular CLI. -## Setup E2E Testing +## Set Up E2E Testing The Angular CLI downloads and installs everything you need to run end-to-end tests for your Angular application. diff --git a/adev/src/content/tutorials/learn-angular/steps/12-enable-routing/README.md b/adev/src/content/tutorials/learn-angular/steps/12-enable-routing/README.md index 927bb72dad0..4464975e2a1 100644 --- a/adev/src/content/tutorials/learn-angular/steps/12-enable-routing/README.md +++ b/adev/src/content/tutorials/learn-angular/steps/12-enable-routing/README.md @@ -2,7 +2,7 @@ For most apps, there comes a point where the app requires more than a single page. When that time inevitably comes, routing becomes a big part of the performance story for users. -In this activity, you'll learn how to setup and configure your app to use Angular Router. +In this activity, you'll learn how to set up and configure your app to use Angular Router.
@@ -71,6 +71,6 @@ export class AppComponent {} -Your app is now setup to use Angular Router. Nice work! 🙌 +Your app is now set up to use Angular Router. Nice work! 🙌 Keep the momentum going to learn the next step of defining the routes for our app. diff --git a/adev/src/content/tutorials/learn-angular/steps/15-forms/README.md b/adev/src/content/tutorials/learn-angular/steps/15-forms/README.md index 08dbb5bc961..47483325a5b 100644 --- a/adev/src/content/tutorials/learn-angular/steps/15-forms/README.md +++ b/adev/src/content/tutorials/learn-angular/steps/15-forms/README.md @@ -4,7 +4,7 @@ Forms are a big part of many apps because they enable your app to accept user in In Angular, there are two types of forms: template-driven and reactive. You'll learn about both over the next few activities. -In this activity, you'll learn how to setup a form using a template-driven approach. +In this activity, you'll learn how to set up a form using a template-driven approach.
diff --git a/adev/src/content/tutorials/learn-angular/steps/16-form-control-values/README.md b/adev/src/content/tutorials/learn-angular/steps/16-form-control-values/README.md index 1e6a8f8671e..f1e673d3757 100644 --- a/adev/src/content/tutorials/learn-angular/steps/16-form-control-values/README.md +++ b/adev/src/content/tutorials/learn-angular/steps/16-form-control-values/README.md @@ -1,6 +1,6 @@ # Getting form control value -Now that your forms are setup with Angular, the next step is to access the values from the form controls. +Now that your forms are set up with Angular, the next step is to access the values from the form controls. In this activity, you'll learn how to get the value from your form input. diff --git a/adev/src/content/tutorials/learn-angular/steps/17-reactive-forms/README.md b/adev/src/content/tutorials/learn-angular/steps/17-reactive-forms/README.md index c257767e06e..bfc4b213c6e 100644 --- a/adev/src/content/tutorials/learn-angular/steps/17-reactive-forms/README.md +++ b/adev/src/content/tutorials/learn-angular/steps/17-reactive-forms/README.md @@ -2,7 +2,7 @@ When you want to manage your forms programmatically instead of relying purely on the template, reactive forms are the answer. -In this activity, you'll learn how to setup reactive forms. +In this activity, you'll learn how to set up reactive forms.
diff --git a/devtools/docs/release.md b/devtools/docs/release.md index 33dd8548c5f..14d41346ac2 100644 --- a/devtools/docs/release.md +++ b/devtools/docs/release.md @@ -65,7 +65,7 @@ Then upload it: 1. Go to the Firefox Addons [page](https://addons.mozilla.org/developers/addons) 1. Find the email and password [on Valentine](http://valentine/#/show/1651707871496288) -1. Setup Google Authenticator with the 2FA QR code. +1. Set up Google Authenticator with the 2FA QR code. * You can find the QR code [on Valentine as well](http://valentine/#/show/1651792043556329) The Firefox publishing process is slightly more involved than Chrome. In particular, they diff --git a/packages/misc/angular-in-memory-web-api/README.md b/packages/misc/angular-in-memory-web-api/README.md index edfe6535859..67b22614514 100644 --- a/packages/misc/angular-in-memory-web-api/README.md +++ b/packages/misc/angular-in-memory-web-api/README.md @@ -140,7 +140,7 @@ export class AppModule { ... } * Always import the `HttpClientInMemoryWebApiModule` _after_ the `HttpClientModule` to ensure that the in-memory backend provider supersedes the Angular version. -* You can setup the in-memory web api within a lazy loaded feature module by calling the `.forFeature` method as you would `.forRoot`. +* You can set up the in-memory web api within a lazy loaded feature module by calling the `.forFeature` method as you would `.forRoot`. * In production, you want HTTP requests to go to the real server and probably have no need for the _in-memory_ provider. CLI-based apps can exclude the provider in production builds like this: @@ -155,7 +155,7 @@ CLI-based apps can exclude the provider in production builds like this: # Examples The [tests](https://github.com/angular/angular/blob/main/packages/misc/angular-in-memory-web-api/test) -are a good place to learn how to setup and use this in-memory web api library. +are a good place to learn how to set up and use this in-memory web api library. See also the example source code in the official Angular.dev documentation such as the [HttpClient](https://angular.dev/guide/http) guide and the