diff --git a/aio/content/tutorial/index.md b/aio/content/tutorial/index.md index e988eae0c8..174c908a48 100644 --- a/aio/content/tutorial/index.md +++ b/aio/content/tutorial/index.md @@ -3,22 +3,22 @@
Getting Started
-In this tutorial, you build your own app from the ground up, providing experience with the typical development process, as well as an introduction to basic app-design concepts, tools, and terminology. +In this tutorial, you build your own application from the ground up, providing experience with the typical development process, as well as an introduction to basic app-design concepts, tools, and terminology. -If you're completely new to Angular, you might want to try the [**Try it now**](start) quick-start app first. +If you're completely new to Angular, you might want to try the [**Try it now**](start) quick-start application first. It is based on a ready-made partially-completed project, which you can examine and modify in the StackBlitz interactive development environment, where you can see the results in real time. -The "Try it" tutorial covers the same major topics—components, template syntax, routing, services, and accessing data via HTTP—in a condensed format, following the most current best practices. +The "Try it" tutorial covers the same major topics—components, template syntax, routing, services, and accessing data using HTTP—in a condensed format, following the most current best practices.
-This _Tour of Heroes_ tutorial shows you how to set up your local development environment and develop an app using the [Angular CLI tool](cli "CLI command reference"), and provides an introduction to the fundamentals of Angular. +This _Tour of Heroes_ tutorial shows you how to set up your local development environment and develop an application using the [Angular CLI tool](cli "CLI command reference"), and provides an introduction to the fundamentals of Angular. -The _Tour of Heroes_ app that you build helps a staffing agency manage its stable of heroes. -The app has many of the features you'd expect to find in any data-driven application. -The finished app acquires and displays a list of heroes, edits a selected hero's detail, and navigates among different views of heroic data. +The _Tour of Heroes_ application that you build helps a staffing agency manage its stable of heroes. +The application has many of the features you'd expect to find in any data-driven application. +The finished application acquires and displays a list of heroes, edits a selected hero's detail, and navigates among different views of heroic data. -You will find references to and expansions of this app domain in many of the examples used throughout the Angular documentation, but you don't necessarily need to work through this tutorial to understand those examples. +You will find references to and expansions of this application domain in many of the examples used throughout the Angular documentation, but you don't necessarily need to work through this tutorial to understand those examples. By the end of this tutorial you will be able to do the following: @@ -38,7 +38,7 @@ Angular can do whatever you need it to do.
Solution
-After completing all tutorial steps, the final app will look like this: . +After completing all tutorial steps, the final application will look like this: .
@@ -63,7 +63,7 @@ where you can change the hero's name. Clicking the "Back" button returns you to the Dashboard. Links at the top take you to either of the main views. -If you click "Heroes," the app displays the "Heroes" master list view. +If you click "Heroes," the application displays the "Heroes" master list view. -Here's the app in action: +Here's the application in action: Angular's [class binding](guide/attribute-binding#class-binding) can add and remove a CSS class conditionally. -Just add `[class.some-css-class]="some-condition"` to the element you want to style. +Add `[class.some-css-class]="some-condition"` to the element you want to style. Add the following `[class.selected]` binding to the `
  • ` in the `HeroesComponent` template: diff --git a/aio/content/tutorial/toh-pt4.md b/aio/content/tutorial/toh-pt4.md index 349807cd61..c51d7f973b 100644 --- a/aio/content/tutorial/toh-pt4.md +++ b/aio/content/tutorial/toh-pt4.md @@ -175,7 +175,7 @@ as if heroes could be fetched synchronously. -This will not work in a real app. +This will not work in a real application. You're getting away with it now because the service currently returns _mock heroes_. But soon the application will fetch heroes from a remote server, which is an inherently _asynchronous_ operation. @@ -434,7 +434,7 @@ Here are the code files discussed on this page. ## Summary * You refactored data access to the `HeroService` class. -* You registered the `HeroService` as the _provider_ of its service at the root level so that it can be injected anywhere in the app. +* You registered the `HeroService` as the _provider_ of its service at the root level so that it can be injected anywhere in the application. * You used [Angular Dependency Injection](guide/dependency-injection) to inject it into a component. * You gave the `HeroService` _get data_ method an asynchronous signature. * You discovered `Observable` and the RxJS _Observable_ library. diff --git a/aio/content/tutorial/toh-pt5.md b/aio/content/tutorial/toh-pt5.md index 46bc0034b5..d5afd80d40 100644 --- a/aio/content/tutorial/toh-pt5.md +++ b/aio/content/tutorial/toh-pt5.md @@ -93,7 +93,7 @@ configures it with the `routes` in one step by calling -Next, `AppRoutingModule` exports `RouterModule` so it will be available throughout the app. +Next, `AppRoutingModule` exports `RouterModule` so it will be available throughout the application. @@ -313,7 +313,7 @@ At this point, all application routes are in place. The `DashboardComponent` hero links do nothing at the moment. Now that the router has a route to `HeroDetailComponent`, -fix the dashboard hero links to navigate via the _parameterized_ dashboard route. +fix the dashboard hero links to navigate using the _parameterized_ dashboard route. @@ -82,7 +82,7 @@ Replace the default contents of `in-memory-data.service.ts` with the following: The `in-memory-data.service.ts` file will take over the function of `mock-heroes.ts`. However, don't delete `mock-heroes.ts` yet, as you still need it for a few more steps of this tutorial. -When the server is ready, you'll detach the In-memory Web API, and the app's requests will go through to the server. +When the server is ready, you'll detach the In-memory Web API, and the application's requests will go through to the server. {@a import-heroes} @@ -205,7 +205,7 @@ Because each service method returns a different kind of `Observable` result, ### Tap into the Observable The `HeroService` methods will **tap** into the flow of observable values -and send a message, via the `log()` method, to the message area at the bottom of the page. +and send a message, using the `log()` method, to the message area at the bottom of the page. They'll do that with the RxJS `tap()` operator, which looks at the observable values, does something with those values, @@ -286,7 +286,7 @@ The hero now appears in the list with the changed name. To add a hero, this application only needs the hero's name. You can use an `` element paired with an add button. -Insert the following into the `HeroesComponent` template, just after +Insert the following into the `HeroesComponent` template, after the heading: