diff --git a/1.1.4/docs/partials/api/ng.directive:ngAnimate.html b/1.1.4/docs/partials/api/ng.directive:ngAnimate.html
index b4c8493cad..28da5edca3 100644
--- a/1.1.4/docs/partials/api/ng.directive:ngAnimate.html
+++ b/1.1.4/docs/partials/api/ng.directive:ngAnimate.html
@@ -5,7 +5,7 @@ <h1><code ng:non-bindable="">ngAnimate</code>
 <div><a href="http://github.com/angular/angular.js/edit/master/src/ng/animator.js" class="improve-docs btn btn-primary">Improve this doc</a><h2 id="Description">Description</h2>
 <div class="description"><p>The <code>ngAnimate</code> directive works as an attribute that is attached alongside pre-existing directives.
 It effects how the directive will perform DOM manipulation. This allows for complex animations to take place while
-without burduning the directive which uses the animation with animation details. The built dn directives
+without burdening the directive which uses the animation with animation details. The built in directives
 <code>ngRepeat</code>, <code>ngInclude</code>, <code>ngSwitch</code>, <code>ngShow</code>, <code>ngHide</code> and <code>ngView</code> already accept <code>ngAnimate</code> directive.
 Custom directives can take advantage of animation through <a href="api/ng.$animator"><code>$animator service</code></a>.</p>
 
@@ -79,7 +79,7 @@ <h4>CSS-defined Animations</h4>
 the start class is added to trigger the animation. The ngAnimate directive will automatically extract the duration
 of the animation to determine when the animation ends. Once the animation is over then both CSS classes will be
 removed from the DOM. If a browser does not support CSS transitions then the animation will start and end
-immediately resulting in a DOM element that is at it's final state. This final state is when the DOM element
+immediately resulting in a DOM element that is at its final state. This final state is when the DOM element
 has no CSS animation classes surrounding it.</p>
 
 <h4>JavaScript-defined Animations</h4>