docs(guide/animations): use the arguments of enabled() in correct order

Deklin · gkalpak · commit 995ccfc9f6e8 · 2016-07-12T17:52:05.000+03:00
Closes #14900
diff --git a/docs/content/guide/animations.ngdoc b/docs/content/guide/animations.ngdoc
@@ -313,8 +313,8 @@ This function can be used to enable / disable animations in two different ways:
 With a single `boolean` argument, it enables / disables animations globally: `$animate.enabled(false)`
 disables all animations in your app.
 
-When the second argument is a native DOM or jQuery element, the function enables / disables
-animations on this element *and all its children*: `$animate.enabled(false, myElement)`. This is the
+When the first argument is a native DOM or jqLite/jQuery element, the function enables / disables
+animations on this element *and all its children*: `$animate.enabled(myElement, false)`. This is the
 most flexible way to change the animation state. For example, even if you have used it to disable
 animations on a parent element, you can still re-enable it for a child element. And compared to the
 `classNameFilter`, you can change the animation status at runtime instead of during the config phase.
