Added docs for no-literals rule

Author: CalebMorris

README.md

@@ -84,6 +84,7 @@ Finally, enable all of the rules that you would like to use.
 * [no-danger](docs/rules/no-danger.md): Prevent usage of dangerous JSX properties
 * [no-did-mount-set-state](docs/rules/no-did-mount-set-state.md): Prevent usage of setState in componentDidMount
 * [no-did-update-set-state](docs/rules/no-did-update-set-state.md): Prevent usage of setState in componentDidUpdate
+* [no-literals](docs/rules/no-literals.md): Prevent usage of unwrapped JSX strings
 * [no-multi-comp](docs/rules/no-multi-comp.md): Prevent multiple component definition per file
 * [no-unknown-property](docs/rules/no-unknown-property.md): Prevent usage of unknown DOM property
 * [prop-types](docs/rules/prop-types.md): Prevent missing props validation in a React component definition

docs/rules/no-literals.md

@@ -0,0 +1,23 @@
+# Prevent usage of unwrapped JSX strings (no-literals)
+
+In JSX when using a literal string you can wrap it in a JXS container `{'TEXT'}`.
+This rules requies that you wrap all literal strings.
+Prevents any odd artifacts of highlighters if you unwrapped string contains a enclsoing character like `'` in contractions and enforces consistency.
+
+## Rule Details
+
+The following patterns are considered warnings:
+
+```javascript
+var Hello = <div>test</div>;
+```
+
+The following patterns are not considered:
+
+```javascript
+var Hello = <div>{'test'}</div>;
+```
+
+## When Not To Use It
+
+If you do not want to enforce any style JSX literals, then you can disable this rule.