aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/guide/directive.ngdoc
diff options
context:
space:
mode:
authorMatt Rohrer2012-09-26 15:30:55 +0200
committerBrian Ford2013-01-17 19:10:46 -0500
commit93070f14885801de7e264b04fdf4cb54b7dc7d9b (patch)
tree9a96a5e4c8ea0e18dc775c2b92bc148c57c00a87 /docs/content/guide/directive.ngdoc
parent3c8583e5dd10ff356ac473f53e920fb10eb41571 (diff)
downloadangular.js-93070f14885801de7e264b04fdf4cb54b7dc7d9b.tar.bz2
docs(guide): minor grammar fixes
Diffstat (limited to 'docs/content/guide/directive.ngdoc')
-rw-r--r--docs/content/guide/directive.ngdoc11
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index 3d669b1b..8ef5e08f 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -110,7 +110,7 @@ Compilation of HTML happens in three phases:
## Reasons behind the compile/link separation
At this point you may wonder why the compile process is broken down to a compile and link phase.
-To understand this, let's look at a real world example with repeater:
+To understand this, let's look at a real world example with a repeater:
<pre>
Hello {{user}}, you have these actions:
@@ -296,7 +296,7 @@ makes it injectable following all of the rules of injection annotation.
The directive definition object provides instructions to the {@link api/ng.$compile
compiler}. The attributes are:
- * `name` - Name of the current scope. Optional defaults to the name at registration.
+ * `name` - Name of the current scope. Optional and defaults to the name at registration.
* `priority` - When there are multiple directives defined on a single DOM element, sometimes it
is necessary to specify the order in which the directives are applied. The `priority` is used
@@ -310,7 +310,7 @@ compiler}. The attributes are:
* `scope` - If set to:
* `true` - then a new scope will be created for this directive. If multiple directives on the
- same element request new scope, only one new scope is created. The new scope rule does not
+ same element request a new scope, only one new scope is created. The new scope rule does not
apply for the root of the template since the root of the template always gets a new scope.
* `{}` (object hash) - then a new 'isolate' scope is created. The 'isolate' scope differs from
@@ -474,7 +474,7 @@ compiler linking function will fail to locate the correct elements for linking.
### Post-linking function
-Executed after the child elements are linked. Safe to do DOM transformation in here.
+Executed after the child elements are linked. It is safe to do DOM transformation in the post-linking function.
<a name="Attributes"></a>
## Attributes
@@ -584,7 +584,7 @@ isolated scope then it will not be able to bind to anything. For this reason the
is a child of the original scope, before the widget created an isolated scope for its local
variables. This makes the transcluded and widget isolated scope siblings.
-This may seem as unexpected complexity, but it gives the widget user and developer the least
+This may seem to be unexpected complexity, but it gives the widget user and developer the least
surprise.
Therefore the final directive definition looks something like this:
@@ -609,7 +609,6 @@ can be built.
Following is an example of building a reusable widget.
-
<doc:example module="zippyModule">
<doc:source>
<script>