Skip to content

Commit 66e4c85

Browse files
petebacondarwinnetman92
authored andcommitted
docs(ngAnimate): fix typos
1 parent 70a751e commit 66e4c85

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/ngAnimate/module.js

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,7 @@
327327
* ## CSS + JS Animations Together
328328
*
329329
* AngularJS 1.4 and higher has taken steps to make the amalgamation of CSS and JS animations more flexible. However, unlike earlier versions of Angular,
330-
* defining CSS and JS animations to work off of the same CSS class will not work anymore. Therefore example below will only result in **JS animations taking
330+
* defining CSS and JS animations to work off of the same CSS class will not work anymore. Therefore the example below will only result in **JS animations taking
331331
* charge of the animation**:
332332
*
333333
* ```html
@@ -356,8 +356,8 @@
356356
* }
357357
* ```
358358
*
359-
* Does this mean that CSS and JS animations cannot be used together? Do JS-based animations always have higher priority? We can suppliment for the
360-
* lack of CSS animations by making use of the `$animateCss` service to trigger our own tweaked-out, CSS-based animations directly from
359+
* Does this mean that CSS and JS animations cannot be used together? Do JS-based animations always have higher priority? We can make up for the
360+
* lack of CSS animations by using the `$animateCss` service to trigger our own tweaked-out, CSS-based animations directly from
361361
* our own JS-based animation code:
362362
*
363363
* ```js

0 commit comments

Comments
 (0)