fixup! docs(guide/animations): list missing animated directives (and other improvements)

Author: gkalpak

docs/content/guide/animations.ngdoc

@@ -6,13 +6,14 @@
 
 # Animations
 
-AngularJS provides animation hooks for common directives such as `ngRepeat`, `ngSwitch`, and
-`ngView`, as well as custom directives via the `$animate` service. These animation hooks are set in
-place to trigger animations during the life cycle of various directives and when triggered, will
-attempt to perform a CSS Transition, CSS Keyframe Animation or a JavaScript callback Animation
-(depending on whether an animation is placed on the given directive). Animations can be placed using
-vanilla CSS by following the naming conventions set in place by AngularJS or with JavaScript code,
-defined as a factory.
+AngularJS provides animation hooks for common directives such as
+{@link ng.directive:ngRepeat ngRepeat}, {@link ng.directive:ngSwitch ngSwitch}`, and
+{@link ngRoute.directive:ngView ngView}`, as well as custom directives via the `$animate` service.
+These animation hooks are set in place to trigger animations during the life cycle of various
+directives and when triggered, will attempt to perform a CSS Transition, CSS Keyframe Animation or a
+JavaScript callback Animation (depending on whether an animation is placed on the given directive).
+Animations can be placed using vanilla CSS by following the naming conventions set in place by
+AngularJS or with JavaScript code, defined as a factory.
 
 <div class="alert alert-info">
   Note that we have used non-prefixed CSS transition properties in our examples as the major
@@ -267,8 +268,8 @@ overwhelming, and the performance may suffer.
 
 Internally, `ngAnimate` waits until all template downloads that are started right after bootstrap
 have finished. Then, it waits for the currently running {@link ng.$rootScope.Scope#$digest $digest}
-and the one more after that to finish. This ensures that the whole app has been compiled fully
-before animations are attempted.
+and one more after that, to finish. This ensures that the whole app has been compiled fully before
+animations are attempted.
 
 If you do want your animations to play when the app bootstraps, you can enable animations globally
 in your main module's {@link angular.Module#run run} function:
@@ -345,11 +346,10 @@ With a single `boolean` argument, it enables / disables animations globally:
 `$animate.enabled(false)` disables all animations in your app.
 
 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.
+animations on this element *and all its children*: `$animate.enabled(myElement, false)`. You can
+still use it to re-enable animations for a child element, even if you have disabled them on a parent
+element. And compared to the `classNameFilter`, you can change the animation status at runtime
+instead of during the config phase.
 
 Note however that the `$animate.enabled()` state for individual elements does not overwrite
 disabling rules that have been set in the {@link $animateProvider#classNameFilter classNameFilter}.
@@ -458,7 +458,7 @@ You can also use one of the other
 strategies to disable animations}.
 
 
-### Enable animations outside of the application DOM tree: {@link ng.$animate#pin $animate.pin()}
+## Enable animations outside of the application DOM tree: {@link ng.$animate#pin $animate.pin()}
 
 Before animating, `ngAnimate` checks if the animated element is inside the application DOM tree. If
 not, no animation is run. Usually, this is not a problem since most apps use the `html` or `body`