From 6e8bc310f0899c46d8a065ac2743c85272d2b24d Mon Sep 17 00:00:00 2001 From: Eli Sadoff Date: Fri, 2 Jun 2017 15:10:54 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20change=20=E2=80=9Dit's"=20to=20"its"=20?= =?UTF-8?q?as=20needed=20in=20several=20docs.=20(#21867)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Most of them are in content but one is in common and needs special approval. PR Close #21867 --- aio/content/guide/ngmodule-faq.md | 4 ++-- aio/content/guide/structural-directives.md | 2 +- aio/content/guide/upgrade.md | 12 ++++++------ packages/common/src/directives/ng_template_outlet.ts | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/aio/content/guide/ngmodule-faq.md b/aio/content/guide/ngmodule-faq.md index 651b8875fa..8c8ea9e806 100644 --- a/aio/content/guide/ngmodule-faq.md +++ b/aio/content/guide/ngmodule-faq.md @@ -165,7 +165,7 @@ Such [entry components](guide/ngmodule-faq#q-entry-component-defined) can never While there's no harm in exporting them, there's also no benefit. * Pure service modules that don't have public (exported) declarations. For example, there's no point in re-exporting `HttpClientModule` because it doesn't export anything. -It's only purpose is to add http service providers to the application as a whole. +Its only purpose is to add http service providers to the application as a whole.
@@ -190,7 +190,7 @@ An NgModule can export a combination of its own declarations, selected imported Don't bother re-exporting pure service modules. Pure service modules don't export [declarable](guide/bootstrapping#the-declarations-array) classes that another NgModule could use. For example, there's no point in re-exporting `HttpClientModule` because it doesn't export anything. -It's only purpose is to add http service providers to the application as a whole. +Its only purpose is to add http service providers to the application as a whole.
diff --git a/aio/content/guide/structural-directives.md b/aio/content/guide/structural-directives.md index 754bf37158..cc186ac568 100644 --- a/aio/content/guide/structural-directives.md +++ b/aio/content/guide/structural-directives.md @@ -297,7 +297,7 @@ These properties include `index` and `odd` and a special property named `$implic Angular sets them to the current value of the context's `index` and `odd` properties. * The context property for `let-hero` wasn't specified. -It's intended source is implicit. +Its intended source is implicit. Angular sets `let-hero` to the value of the context's `$implicit` property which `NgFor` has initialized with the hero for the current iteration. diff --git a/aio/content/guide/upgrade.md b/aio/content/guide/upgrade.md index 6a1b6c7688..ed9fecfaef 100644 --- a/aio/content/guide/upgrade.md +++ b/aio/content/guide/upgrade.md @@ -588,7 +588,7 @@ and a controller: You can *upgrade* this component to Angular using the `UpgradeComponent` class. By creating a new Angular **directive** that extends `UpgradeComponent` and doing a `super` call -inside it's constructor, you have a fully upgraded AngularJS component to be used inside Angular. +inside its constructor, you have a fully upgraded AngularJS component to be used inside Angular. All that is left is to add it to `AppModule`'s `declarations` array. @@ -602,7 +602,7 @@ All that is left is to add it to `AppModule`'s `declarations` array. Upgraded components are Angular **directives**, instead of **components**, because Angular is unaware that AngularJS will create elements under it. As far as Angular knows, the upgraded component is just a directive - a tag - and Angular doesn't have to concern itself with -it's children. +its children. @@ -784,7 +784,7 @@ compilation can pick it up. -You can then inject it in Angular using it's class as a type annotation: +You can then inject it in Angular using its class as a type annotation: @@ -1260,7 +1260,7 @@ app. Switch to the [ngUpgrade bootstrap](#bootstrapping-hybrid-applications) met instead. First, remove the `ng-app` attribute from `index.html`. -Then import `UpgradeModule` in the `AppModule`, and override it's `ngDoBootstrap` method: +Then import `UpgradeModule` in the `AppModule`, and override its `ngDoBootstrap` method: @@ -1619,7 +1619,7 @@ instead of the default "push state" strategy. Now update the `AppModule` to import this `AppRoutingModule` and also the declare the root `AppComponent` as the bootstrap component. That tells Angular that it should bootstrap the app with the _root_ `AppComponent` and -insert it's view into the host web page. +insert its view into the host web page. You must also remove the bootstrap of the AngularJS module from `ngDoBootstrap()` in `app.module.ts` and the `UpgradeModule` import. @@ -1695,7 +1695,7 @@ module configuration files and not needed in Angular: The external typings for AngularJS may be uninstalled as well. The only ones you still need are for Jasmine and Angular polyfills. -The `@angular/upgrade` package and it's mapping in `systemjs.config.js` can also go. +The `@angular/upgrade` package and its mapping in `systemjs.config.js` can also go. npm uninstall @angular/upgrade --save diff --git a/packages/common/src/directives/ng_template_outlet.ts b/packages/common/src/directives/ng_template_outlet.ts index 860d8dce04..f653503b62 100644 --- a/packages/common/src/directives/ng_template_outlet.ts +++ b/packages/common/src/directives/ng_template_outlet.ts @@ -24,7 +24,7 @@ import {Directive, EmbeddedViewRef, Input, OnChanges, SimpleChange, SimpleChange * `[ngTemplateOutletContext]` should be an object, the object's keys will be available for binding * by the local template `let` declarations. * - * Note: using the key `$implicit` in the context object will set it's value as default. + * Note: using the key `$implicit` in the context object will set its value as default. * * ## Example *