refactor: fix typos (#18000)
This commit is contained in:
Victor Berchet
committed by
Jason Aden
Jason Aden
parent
9dd550fa1e
commit
c723d42d0a
@ -96,7 +96,7 @@ This section describes how each of the aforementioned sub-tasks is accomplished:
|
||||
|
||||
5. **Deploy the artifacts to the corresponding PR's directory.**
|
||||
|
||||
With the preceeding steps, we have verified that the uploaded artifacts have been uploaded by
|
||||
With the preceding steps, we have verified that the uploaded artifacts have been uploaded by
|
||||
Travis. Additionally, we have determined whether the PR can be trusted to have its previews
|
||||
publicly accessible or whether further verification is necessary. The artifacts will be stored to
|
||||
the PR's directory, but will not be publicly accessible unless the PR has been verified.
|
||||
|
||||
@ -6,7 +6,7 @@ import { Hero } from './hero';
|
||||
const HEROES = [
|
||||
new Hero('Windstorm', 'Weather mastery'),
|
||||
new Hero('Mr. Nice', 'Killing them with kindness'),
|
||||
new Hero('Magneta', 'Manipulates metalic objects')
|
||||
new Hero('Magneta', 'Manipulates metallic objects')
|
||||
];
|
||||
|
||||
@Injectable()
|
||||
|
||||
@ -39,7 +39,7 @@ if (!/e2e/.test(location.search)) {
|
||||
directives.push(CountdownLocalVarParentComponent);
|
||||
directives.push(CountdownViewChildParentComponent);
|
||||
} else {
|
||||
// In e2e test use CUSTOM_ELEMENTS_SCHEMA to supress unknown element errors
|
||||
// In e2e test use CUSTOM_ELEMENTS_SCHEMA to suppress unknown element errors
|
||||
schemas.push(CUSTOM_ELEMENTS_SCHEMA);
|
||||
}
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
{
|
||||
"description": "Hierachical Dependency Injection",
|
||||
"description": "Hierarchical Dependency Injection",
|
||||
"basePath": "src/",
|
||||
"files":[
|
||||
"!**/*.d.ts",
|
||||
|
||||
@ -85,7 +85,7 @@ describe('Pipes', function () {
|
||||
return resetEle.click();
|
||||
})
|
||||
.then(function() {
|
||||
expect(flyingHeroesEle.count()).toEqual(2, 'reset should restore orginal flying heroes');
|
||||
expect(flyingHeroesEle.count()).toEqual(2, 'reset should restore original flying heroes');
|
||||
});
|
||||
});
|
||||
|
||||
|
||||
@ -273,7 +273,7 @@ export class InnerCompWithExternalTemplateComponent { }
|
||||
|
||||
@Component({
|
||||
selector: 'bad-template-comp',
|
||||
templateUrl: './non-existant.html'
|
||||
templateUrl: './non-existent.html'
|
||||
})
|
||||
export class BadTemplateUrlComponent { }
|
||||
|
||||
|
||||
@ -227,7 +227,7 @@ function heroModuleSetup() {
|
||||
// #enddocregion route-no-id
|
||||
|
||||
// #docregion route-bad-id
|
||||
describe('when navigate to non-existant hero id', () => {
|
||||
describe('when navigate to non-existent hero id', () => {
|
||||
beforeEach( async(() => {
|
||||
activatedRoute.testParamMap = { id: 99999 };
|
||||
createComponent();
|
||||
|
||||
@ -244,7 +244,7 @@ You can limit the scope of an injected service to a *branch* of the application
|
||||
by providing that service *at the sub-root component for that branch*.
|
||||
This example shows how similar providing a service to a sub-root component is
|
||||
to providing a service in the root `AppComponent`. The syntax is the same.
|
||||
Here, the `HeroService` is availble to the `HeroesBaseComponent` because it is in the `providers` array:
|
||||
Here, the `HeroService` is available to the `HeroesBaseComponent` because it is in the `providers` array:
|
||||
|
||||
<code-example path="dependency-injection-in-action/src/app/sorted-heroes.component.ts" region="injection" title="src/app/sorted-heroes.component.ts (HeroesBaseComponent excerpt)">
|
||||
|
||||
|
||||
@ -320,7 +320,7 @@ Read more about `ngIf` and `*` in the [ngIf section](guide/template-syntax#ngIf)
|
||||
|
||||
|
||||
The template expression inside the double quotes,
|
||||
`*ngIf="heros.length > 3"`, looks and behaves much like TypeScript.
|
||||
`*ngIf="heroes.length > 3"`, looks and behaves much like TypeScript.
|
||||
When the component's list of heroes has more than three items, Angular adds the paragraph
|
||||
to the DOM and the message appears. If there are three or fewer items, Angular omits the
|
||||
paragraph, so no message appears. For more information,
|
||||
|
||||
@ -168,10 +168,8 @@ on custom validation directives.
|
||||
|
||||
* Binding to the new `formErrors.name` property is sufficient to display all name validation error messages.
|
||||
|
||||
|
||||
{@a component-class}
|
||||
|
||||
|
||||
### Component class
|
||||
The original component code for Template 1 stayed the same; however,
|
||||
Template 2 requires some changes in the component. This section covers the code
|
||||
|
||||
@ -614,7 +614,7 @@ If you do not bind the value, the select shows the first option from the data mo
|
||||
The component _class_ defines control properties without regard for their representation in the template.
|
||||
You define the `state`, `power`, and `sidekick` controls the same way you defined the `name` control.
|
||||
You tie these controls to the template HTML elements in the same way,
|
||||
specifiying the `FormControl` name with the `formControlName` directive.
|
||||
specifying the `FormControl` name with the `formControlName` directive.
|
||||
|
||||
See the API reference for more information about
|
||||
[radio buttons](api/forms/RadioControlValueAccessor "API: RadioControlValueAccessor"),
|
||||
@ -1220,7 +1220,7 @@ Place a button on the form so the user can add a new _secret lair_ and wire it t
|
||||
|
||||
Be sure to **add the `type="button"` attribute**.
|
||||
In fact, you should always specify a button's `type`.
|
||||
Without an explict type, the button type defaults to "submit".
|
||||
Without an explicit type, the button type defaults to "submit".
|
||||
When you later add a _form submit_ action, every "submit" button triggers the submit action which
|
||||
might do something like save the current changes.
|
||||
You do not want to save changes when the user clicks the _Add a Secret Lair_ button.
|
||||
|
||||
@ -199,7 +199,7 @@ If you do, this page can help you understand their purpose.
|
||||
|
||||
|
||||
A list of files that you can delete if you want to purge your setup of the
|
||||
original QuickStart Seed testing and git maintainence artifacts.
|
||||
original QuickStart Seed testing and git maintenance artifacts.
|
||||
See instructions in the optional
|
||||
[_Deleting non-essential files_](guide/setup#non-essential "Setup: Deleting non-essential files") section.
|
||||
*Do this only in the beginning to avoid accidentally deleting your own tests and git setup!*
|
||||
|
||||
@ -3127,7 +3127,7 @@ that may need features from another common module; for example,
|
||||
|
||||
|
||||
|
||||
**Why?** A lazy loaded feature module that imports that shared module will make its own copy of the service and likely have undesireable results.
|
||||
**Why?** A lazy loaded feature module that imports that shared module will make its own copy of the service and likely have undesirable results.
|
||||
|
||||
|
||||
</div>
|
||||
@ -3377,7 +3377,7 @@ Yet they're too big and messy to leave loose in the root folder.
|
||||
|
||||
|
||||
|
||||
**Why?** A lazily loaded feature module that directly imports the `CoreModule` will make its own copy of services and likely have undesireable results.
|
||||
**Why?** A lazily loaded feature module that directly imports the `CoreModule` will make its own copy of services and likely have undesirable results.
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
@ -431,7 +431,7 @@ by calling the `@Inject()` decorator with the injection token.
|
||||
In the following example, the token is the string `'heroName'`.
|
||||
|
||||
The other JavaScript dialects add a `parameters` array to the class constructor function.
|
||||
Each item constrains a new instance of `Inject`:
|
||||
Each item contains a new instance of `Inject`:
|
||||
|
||||
* _Plain ES6_—each item is a new instance of `Inject(token)` in a sub-array.
|
||||
* _ES5_—simply list the string tokens.
|
||||
|
||||
@ -259,7 +259,7 @@
|
||||
<path d="M15.1748197,2.88436401 L12.7958773,15.1229617" id="Line-Copy-9"></path>
|
||||
<path d="M1.2029061,0.773628441 L0.767790904,13.2336973" id="Line-Copy-10"></path>
|
||||
</g>
|
||||
<g id="speed-guage" transform="translate(17.000000, 0.000000)">
|
||||
<g id="speed-gauge" transform="translate(17.000000, 0.000000)">
|
||||
<mask id="mask-29" fill="white">
|
||||
<use xlink:href="#path-28"></use>
|
||||
</mask>
|
||||
|
||||
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 27 KiB |
@ -2,7 +2,7 @@
|
||||
|
||||
Media queries
|
||||
|
||||
To use these, put this snippet in the approriate selector:
|
||||
To use these, put this snippet in the appropriate selector:
|
||||
|
||||
@include bp(tiny) {
|
||||
background-color: purple;
|
||||
|
||||
@ -101,7 +101,7 @@ describe('addNotYetDocumentedProperty', function() {
|
||||
});
|
||||
|
||||
|
||||
it('should not mark documents explicity tagged as `@noDescription`', function() {
|
||||
it('should not mark documents explicitly tagged as `@noDescription`', function() {
|
||||
var a, a1, a2, b, b1, b2, c, c1, c2;
|
||||
var docs = [
|
||||
a = {
|
||||
|
||||
@ -21,7 +21,7 @@ module.exports = function() {
|
||||
if (newLines.length > 0) {
|
||||
newLines.pop();
|
||||
} else {
|
||||
// wierd case - first expression in str is an @example
|
||||
// weird case - first expression in str is an @example
|
||||
// in this case the :marked appear above the str passed in,
|
||||
// so we need to put 'something' into the markdown tag.
|
||||
newLines.push(sp + '.'); // '.' is a dummy char
|
||||
|
||||
Reference in New Issue
Block a user