aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteve Nicolai2012-08-05 14:16:37 -0500
committerMisko Hevery2012-08-30 16:02:24 -0700
commit5cb7297a08649107d5155a22477c8c3511372034 (patch)
treee25e455b8289342f1b98281c1fe5c9d0d3701cc8
parent0f05516d14329a5e080969c174fb7535b3a43cbe (diff)
downloadangular.js-5cb7297a08649107d5155a22477c8c3511372034.tar.bz2
doc(devguide) - Fix typos and small grammatical errors in the developer guide.
Diffstat
-rw-r--r--docs/content/guide/bootstrap.ngdoc6
-rw-r--r--docs/content/guide/dev_guide.services.$location.ngdoc4
-rw-r--r--docs/content/guide/dev_guide.services.testing_services.ngdoc2
-rw-r--r--docs/content/guide/dev_guide.templates.databinding.ngdoc2
-rw-r--r--docs/content/guide/dev_guide.unit-testing.ngdoc2
-rw-r--r--docs/content/guide/directive.ngdoc4
-rw-r--r--docs/content/guide/expression.ngdoc2
-rw-r--r--docs/content/guide/ie.ngdoc10
-rw-r--r--docs/content/guide/scope.ngdoc8
9 files changed, 20 insertions, 20 deletions
diff --git a/docs/content/guide/bootstrap.ngdoc b/docs/content/guide/bootstrap.ngdoc
index 58b2eb03..3be24bb5 100644
--- a/docs/content/guide/bootstrap.ngdoc
+++ b/docs/content/guide/bootstrap.ngdoc
@@ -24,7 +24,7 @@ initialization.
</html>
</pre>
- * Place the `script` tag at the buttom of the page. Placing script tags at the end of the page
+ * Place the `script` tag at the bottom of the page. Placing script tags at the end of the page
improves app load time because the HTML loading is not blocked by loading of the `angular.js`
script. You can get the latest bits from {@link http://code.angularjs.org}. Please don't link
your production code to this URL, as it will expose a security hole on your site. For
@@ -34,12 +34,12 @@ initialization.
* Choose: `angular-[version].min.js` for a compressed and obfuscated file, suitable for use in
production.
* Place `ng-app` to the root of your application, typically on the `<html>` tag if you want
- anugular to auto-bootstrap your application.
+ angular to auto-bootstrap your application.
<html ng-app>
* If you choose to use the old style directive syntax `ng:` then include xml-namespace in `html`
- to make IE happy. (This is here for historical resons, and we no longer recomend use of
+ to make IE happy. (This is here for historical reasons, and we no longer recommend use of
`ng:`.)
<html xmlns:ng="http://angularjs.org">
diff --git a/docs/content/guide/dev_guide.services.$location.ngdoc b/docs/content/guide/dev_guide.services.$location.ngdoc
index b13a47d1..17d38b14 100644
--- a/docs/content/guide/dev_guide.services.$location.ngdoc
+++ b/docs/content/guide/dev_guide.services.$location.ngdoc
@@ -331,11 +331,11 @@ to entry point of your application (e.g. index.html)
### Crawling your app
-If you want your AJAX application to be indexed by web crawlers, you rill need to add the following
+If you want your AJAX application to be indexed by web crawlers, you will need to add the following
meta tag to the HEAD section of your document:
<pre><meta name="fragment" content="!" /></pre>
-This statement causes a crawler to request links with empty `_escaped_fragment_` parameter so that
+This statement causes a crawler to request links with an empty `_escaped_fragment_` parameter so that
your server can recognize the crawler and serve it HTML snapshots. For more information about this
technique, see {@link http://code.google.com/web/ajaxcrawling/docs/specification.html Making AJAX
Applications Crawlable}.
diff --git a/docs/content/guide/dev_guide.services.testing_services.ngdoc b/docs/content/guide/dev_guide.services.testing_services.ngdoc
index dde00970..6e0bbace 100644
--- a/docs/content/guide/dev_guide.services.testing_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.testing_services.ngdoc
@@ -55,7 +55,7 @@ it('should clear messages after alert', function() {
* {@link dev_guide.services.understanding_services Understanding Angular Services}
* {@link dev_guide.services.creating_services Creating Angular Services}
* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
-* {@link dev_guide.services.injecting_controllers Injecting Services Into Conrollers}
+* {@link dev_guide.services.injecting_controllers Injecting Services Into Controllers}
## Related API
diff --git a/docs/content/guide/dev_guide.templates.databinding.ngdoc b/docs/content/guide/dev_guide.templates.databinding.ngdoc
index ebd9a1e6..396aa609 100644
--- a/docs/content/guide/dev_guide.templates.databinding.ngdoc
+++ b/docs/content/guide/dev_guide.templates.databinding.ngdoc
@@ -24,7 +24,7 @@ because first the template (which is the uncompiled HTML along with any addition
directives) is compiled on the browser, and second, the compilation step produces a live view. We
say live because any changes to the view are immediately reflected in the model, and any changes in
the model are propagated to the view. This makes the model always the single-source-of-truth for
-the application state, greatly simplifying the programing model for the developer. You can think of
+the application state, greatly simplifying the programming model for the developer. You can think of
the view as simply an instant projection of your model.
Because the view is just a projection of the model, the controller is completely separated from the
diff --git a/docs/content/guide/dev_guide.unit-testing.ngdoc b/docs/content/guide/dev_guide.unit-testing.ngdoc
index fe3db075..fd0fe1dd 100644
--- a/docs/content/guide/dev_guide.unit-testing.ngdoc
+++ b/docs/content/guide/dev_guide.unit-testing.ngdoc
@@ -16,7 +16,7 @@ this may seem obvious it usually is very difficult to be able to call an individ
typical project. The reason is that the developers often time mix concerns, and they end up with a
piece of code which does everything. It reads the data from XHR, it sorts it and then it
manipulates the DOM. With angular we try to make it easy for you to do the right thing, and so we
-provide dependency injection for your XHR (which you can mock out) and we crated abstraction which
+provide dependency injection for your XHR (which you can mock out) and we created abstraction which
allow you to sort your model without having to resort to manipulating the DOM. So that in the end,
it is easy to write a sort function which sorts some data, so that your test can create a data set,
apply the function, and assert that the resulting model is in the correct order. The test does not
diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index 9656a773..b600f4d9 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -271,7 +271,7 @@ simplified as:
});
</pre>
-Most directives concern themselves only with instances not with template transformations allowing
+Most directives concern themselves only with instances, not with template transformations, allowing
further simplification:
<pre>
@@ -342,7 +342,7 @@ compiler}. The attributes are:
`scope: { localFn:'increment()' }`, then isolate scope property `localFn` will point to
a function wrapper for the `increment()` expression. Often it's desirable to pass data from
the isolate scope via an expression and to the parent scope, this can be done by passing a
- map of local variable names and values into the expression wrapper fn. For example if the
+ map of local variable names and values into the expression wrapper fn. For example, if the
expression is `increment(amount)` then we can specify the amount value by calling the
`localFn` as `localFn({amount: 22})`.
diff --git a/docs/content/guide/expression.ngdoc b/docs/content/guide/expression.ngdoc
index 770e356e..469381ff 100644
--- a/docs/content/guide/expression.ngdoc
+++ b/docs/content/guide/expression.ngdoc
@@ -3,7 +3,7 @@
@description
Expressions are JavaScript-like code snippets that are usually placed in bindings such as `{{
-expression }}`. Expressions are process by the {@link api/ng.$parse $parse}
+expression }}`. Expressions are processed by {@link api/ng.$parse $parse}
service.
For example, these are all valid expressions in angular:
diff --git a/docs/content/guide/ie.ngdoc b/docs/content/guide/ie.ngdoc
index 803942f8..e6185a78 100644
--- a/docs/content/guide/ie.ngdoc
+++ b/docs/content/guide/ie.ngdoc
@@ -56,7 +56,7 @@ The **important** parts are:
# Long Version
-IE has an issues with element tag names which are not standard HTML tag names. These fall into two
+IE has issues with element tag names which are not standard HTML tag names. These fall into two
categories, and each category has its own fix.
* If the tag name starts with `my:` prefix than it is considered an XML namespace and must
@@ -65,7 +65,7 @@ categories, and each category has its own fix.
* If the tag has no `:` but it is not a standard HTML tag, then it must be pre-created using
`document.createElement('my-tag')`
- * If you have are planning on styling the custom tag with CSS selectors, then it must be
+ * If you are planning on styling the custom tag with CSS selectors, then it must be
pre-created using `document.createElement('my-tag')` regardless of XML namespace.
@@ -88,7 +88,7 @@ result):
</html>
</pre>
-It should pares into the following DOM:
+It should parse into the following DOM:
<pre>
#document
@@ -122,12 +122,12 @@ In IE, the behavior is that the `BODY` element has three children:
3. A corrupt self closing `/mytag`. This is corrupt since element names are not allowed to have
the `/` character. Furthermore this closing element should not be part of the DOM since it is
- only used to delimitate the structure of the DOM.
+ only used to delineate the structure of the DOM.
## CSS Styling of Custom Tag Names
-The to make CSS selector work with custom elements the custom element name must be shived with the
+To make CSS selectors work with custom elements, the custom element name must be pre-created with
`document.createElement('my-tag')` regardless of XML namespace.
<pre>
diff --git a/docs/content/guide/scope.ngdoc b/docs/content/guide/scope.ngdoc
index 0866e199..5425215f 100644
--- a/docs/content/guide/scope.ngdoc
+++ b/docs/content/guide/scope.ngdoc
@@ -231,9 +231,9 @@ directive listens on DOM events, such as {@link
api/ng.directive:ngClick `ng-click`} it must evaluate the
expression inside the `$apply` method.
-After evaluating the expression `$apply` method performs a {@link
-api/ng.$rootScope.Scope#$digest `$digest`}. In $digest phase the scope examines all
-of the `$watch` expressions and compares them with previous value. This dirty checking, is done
+After evaluating the expression, the `$apply` method performs a {@link
+api/ng.$rootScope.Scope#$digest `$digest`}. In the $digest phase the scope examines all
+of the `$watch` expressions and compares them with the previous value. This dirty checking is done
asynchronously. This means that assignment such as `$scope.username="angular"` will not
immediately cause a `$watch` to be notified, instead the `$watch` notification is delayed until
the `$digest` phase. This delay is desirable, since it coalesces multiple model updates into one
@@ -250,7 +250,7 @@ the `$digest` phase. This delay is desirable, since it coalesces multiple model
2. **Watcher registration**
During template linking directives register {@link
- api/ng.$rootScope.Scope#$watch watches} on the scope. This watches will be
+ api/ng.$rootScope.Scope#$watch watches} on the scope. These watches will be
used to propagate model values to the DOM.
3. **Model mutation**
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-31 17:15:25 +0000