From dd570dcb5ca613a3f91e5d64f3e00326c8b8595a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= <paul@oshannessy.com>
Date: Mon, 13 Jul 2015 10:35:22 -0700
Subject: [PATCH] Merge pull request #4363 from
 tako-black/change_css_to_uppercase

Change `css` to uppercase
(cherry picked from commit fa7aeb65ac1267cd919a22cab96902efde714bdf)
---
 docs/docs/10.1-animation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/10.1-animation.md b/docs/docs/10.1-animation.md
index 4e8734673e..6f6193a94a 100644
--- a/docs/docs/10.1-animation.md
+++ b/docs/docs/10.1-animation.md
@@ -216,7 +216,7 @@ Every DOM component that React can render is available for use. However, `compon
 >
 > Prior to v0.12, when using DOM components, the `component` prop needed to be a reference to `React.DOM.*`. Since the component is simply passed to `React.createElement`, it must now be a string. Composite components must pass the factory.
 
-Any additional, user-defined, properties will become properties of the rendered component. For example, here's how you would render a `<ul>` with css class:
+Any additional, user-defined, properties will become properties of the rendered component. For example, here's how you would render a `<ul>` with CSS class:
 
 ```javascript{1}
 <ReactTransitionGroup component="ul" className="animated-list">