From 0d034a98ec4ef1e0c3c1727e23d1ccd971ae74e6 Mon Sep 17 00:00:00 2001
From: Matias Niemelä
Date: Fri, 28 Feb 2014 14:59:12 -0500
Subject: docs(forms): generated CSS classes for forms and inputs must have a
 ng prefix

---
 src/ng/directive/form.js | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'src/ng/directive/form.js')

diff --git a/src/ng/directive/form.js b/src/ng/directive/form.js
index 4e6ec20d..1424157c 100644
--- a/src/ng/directive/form.js
+++ b/src/ng/directive/form.js
@@ -287,10 +287,11 @@ function FormController(element, attrs, $scope, $animate) {
  *
  * ## Animation Hooks
  *
- * Animations in ngForm are triggered when any of the associated CSS classes are added and removed. These
- * classes are: `.pristine`, `.dirty`, `.invalid` and `.valid` as well as any other validations that
- * are performed within the form. Animations in ngForm are similar to how they work in ngClass and
- * animations can be hooked into using CSS transitions, keyframes as well as JS animations.
+ * Animations in ngForm are triggered when any of the associated CSS classes are added and removed.
+ * These classes are: `.ng-pristine`, `.ng-dirty`, `.ng-invalid` and `.ng-valid` as well as any
+ * other validations that are performed within the form. Animations in ngForm are similar to how
+ * they work in ngClass and animations can be hooked into using CSS transitions, keyframes as well
+ * as JS animations.
  *
  * The following example shows a simple way to utilize CSS transitions to style a form element
  * that has been rendered as invalid after it has been validated:
-- 
cgit v1.2.3