|
12 | 12 | * Markup extensions do not themselves produce linking functions. Think of markup as a way to
|
13 | 13 | * produce shorthand for a {@link angular.widget widget} or a {@link angular.directive directive}.
|
14 | 14 | *
|
15 |
| - * The most prominent example of an markup in angular is the built-in double curly markup |
16 |
| - * `{{expression}}`, which is a shorthand for `<span ng:bind="expression"></span>`. |
| 15 | + * The most prominent example of a markup in angular is the built-in double curly markup |
| 16 | + * `{{expression}}`, which is shorthand for `<span ng:bind="expression"></span>`. |
17 | 17 | *
|
18 | 18 | * Create custom markup like this:
|
19 | 19 | *
|
|
34 | 34 | * @description
|
35 | 35 | *
|
36 | 36 | * Attribute markup extends the angular compiler in a very similar way as {@link angular.markup}
|
37 |
| - * except that it allows you to modify the state of the attribute text rather then the content of a |
| 37 | + * except that it allows you to modify the state of the attribute text rather than the content of a |
38 | 38 | * node.
|
39 | 39 | *
|
40 | 40 | * Create custom attribute markup like this:
|
@@ -138,7 +138,7 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
138 | 138 | *
|
139 | 139 | * @description
|
140 | 140 | * Using <angular/> markup like {{hash}} in an href attribute makes
|
141 |
| - * the page open to a wrong URL, ff the user clicks that link before |
| 141 | + * the page open to a wrong URL, if the user clicks that link before |
142 | 142 | * angular has a chance to replace the {{hash}} with actual URL, the
|
143 | 143 | * link will be broken and will most likely return a 404 error.
|
144 | 144 | * The `ng:href` solves this problem by placing the `href` in the
|
@@ -251,7 +251,8 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
251 | 251 | * </div>
|
252 | 252 | * </pre>
|
253 | 253 | *
|
254 |
| - * the HTML specs do not require browsers preserve the special attributes such as disabled.(The presense of them means true and absense means false) |
| 254 | + * The HTML specs do not require browsers to preserve the special attributes such as disabled. |
| 255 | + * (The presence of them means true and absence means false) |
255 | 256 | * This prevents the angular compiler from correctly retrieving the binding expression.
|
256 | 257 | * To solve this problem, we introduce ng:disabled.
|
257 | 258 | *
|
@@ -281,7 +282,8 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
281 | 282 | * @name angular.directive.ng:checked
|
282 | 283 | *
|
283 | 284 | * @description
|
284 |
| - * the HTML specs do not require browsers preserve the special attributes such as checked.(The presense of them means true and absense means false) |
| 285 | + * The HTML specs do not require browsers to preserve the special attributes such as checked. |
| 286 | + * (The presence of them means true and absence means false) |
285 | 287 | * This prevents the angular compiler from correctly retrieving the binding expression.
|
286 | 288 | * To solve this problem, we introduce ng:checked.
|
287 | 289 | * @example
|
@@ -310,7 +312,8 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
310 | 312 | * @name angular.directive.ng:multiple
|
311 | 313 | *
|
312 | 314 | * @description
|
313 |
| - * the HTML specs do not require browsers preserve the special attributes such as multiple.(The presense of them means true and absense means false) |
| 315 | + * The HTML specs do not require browsers to preserve the special attributes such as multiple. |
| 316 | + * (The presence of them means true and absence means false) |
314 | 317 | * This prevents the angular compiler from correctly retrieving the binding expression.
|
315 | 318 | * To solve this problem, we introduce ng:multiple.
|
316 | 319 | *
|
@@ -345,7 +348,8 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
345 | 348 | * @name angular.directive.ng:readonly
|
346 | 349 | *
|
347 | 350 | * @description
|
348 |
| - * the HTML specs do not require browsers preserve the special attributes such as readonly.(The presense of them means true and absense means false) |
| 351 | + * The HTML specs do not require browsers to preserve the special attributes such as readonly. |
| 352 | + * (The presence of them means true and absence means false) |
349 | 353 | * This prevents the angular compiler from correctly retrieving the binding expression.
|
350 | 354 | * To solve this problem, we introduce ng:readonly.
|
351 | 355 | * @example
|
@@ -374,7 +378,8 @@ angularTextMarkup('option', function(text, textNode, parentElement){
|
374 | 378 | * @name angular.directive.ng:selected
|
375 | 379 | *
|
376 | 380 | * @description
|
377 |
| -* the HTML specs do not require browsers preserve the special attributes such as selected.(The presense of them means true and absense means false) |
| 381 | +* The HTML specs do not require browsers to preserve the special attributes such as selected. |
| 382 | +* (The presence of them means true and absence means false) |
378 | 383 | * This prevents the angular compiler from correctly retrieving the binding expression.
|
379 | 384 | * To solve this problem, we introduce ng:selected.
|
380 | 385 | * @example
|
|
0 commit comments