honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(modules): fix typos 

closes #2914
This commit is contained in:
Eric Lee Carraway 2015-07-06 22:55:50 -05:00 committed by Tobias Bosch
parent abc1580fa9
commit 3869818d8f
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
modules/angular2/docs/core/02_directives.md
View File

@ -52,7 +52,7 @@ CSS Selectors can be combined:
## Directives ## Directives
The simplest kind of directive is a decorator. Directives are usefull for encapsulating behavior. The simplest kind of directive is a decorator. Directives are useful for encapsulating behavior.
* Multiple decorators can be placed on a single element. * Multiple decorators can be placed on a single element.
* Directives do not introduce new evaluation context. * Directives do not introduce new evaluation context.
@ -260,7 +260,7 @@ Injecting other directives into directives follows a similar mechanism as inject
There are five kinds of visibilities: There are five kinds of visibilities:
* (no annotation): Inject dependant directives only if they are on the current element. * (no annotation): Inject dependent directives only if they are on the current element.
* `@ancestor`: Inject a directive if it is at any element above the current element. * `@ancestor`: Inject a directive if it is at any element above the current element.
* `@parent`: Inject a directive which is a direct parent of the current element. * `@parent`: Inject a directive which is a direct parent of the current element.
* `@child`: Inject a list of direct children which match a given type. (Used with `Query`) * `@child`: Inject a list of direct children which match a given type. (Used with `Query`)
@ -325,7 +325,7 @@ Assume the following DOM structure for `my_app.html`:
#### Shadow DOM effects on Directive DI #### Shadow DOM effects on Directive DI
Shadow DOM provides an encapsulation for components, so as a general rule it does not allow directive injections to cross the shadow DOM boundaries. To remedy this, declaritively specify the required component as an injectable. Shadow DOM provides an encapsulation for components, so as a general rule it does not allow directive injections to cross the shadow DOM boundaries. To remedy this, declaratively specify the required component as an injectable.
``` ```
@Component({ @Component({

4
modules/benchpress/docs/index.md
View File

@ -4,7 +4,7 @@ Benchpress is a framework for e2e performance tests.
# Why? # Why?
There are so called "micro benchmarks" that esentially use a stop watch in the browser to measure time There are so called "micro benchmarks" that essentially use a stop watch in the browser to measure time
(e.g. via `performance.now()`). This approach is limited to time, and in some cases memory (e.g. via `performance.now()`). This approach is limited to time, and in some cases memory
(Chrome with special flags), as metric. It does not allow to measure: (Chrome with special flags), as metric. It does not allow to measure:
@ -80,7 +80,7 @@ index.html:
var container = document.getElementById('container'); var container = document.getElementById('container');
var complexHtmlString = '...'; // TODO var complexHtmlString = '...'; // TODO
function reset() { cotainer.innerHTML = ''; } function reset() { container.innerHTML = ''; }
function fill() { function fill() {
container.innerHTML = complexHtmlString; container.innerHTML = complexHtmlString;

2
modules/rtts_assert/README.js.md
View File

@ -28,7 +28,7 @@ assert(value).is(...)
// Custom type assert: // Custom type assert:
// - i have a custom type // - i have a custom type
// - adding an assert methos // - adding an assert methods
assert.define(MyUser, function(value) { assert.define(MyUser, function(value) {
assert(value).is(Type, Type2); // or assert(value).is(Type, Type2); // or
assert(value, 'name').is(assert.string); assert(value, 'name').is(assert.string);