Rebrand pt. 2.

README.md

@@ -1,32 +1,32 @@
-# Lithium
+# li₃
 
 ### You asked for a better framework. Here it is.
 
-Lithium is fast, flexible and the most RAD development framework for PHP 5.3 and up.
+li3 is fast, flexible and the most RAD development framework for PHP 5.3 and up.
 
 ### A framework of firsts
 
-Lithium is the first and only major PHP framework built from the ground up for PHP 5.3+, and the first to break ground into major new technologies, including bridging the gap between relational and non-relational databases through a single, unified API.
+li3 is the first and only major PHP framework built from the ground up for PHP 5.3+, and the first to break ground into major new technologies, including bridging the gap between relational and non-relational databases through a single, unified API.
 
 ### Promiscuously opinionated
 
 Some frameworks give you a solid set of classes, but little or no default project organization, leaving you to fend for yourself on each project you create, and spend time wiring up framework classes that should just work together. Others provide you with great organizational conventions, but no way to break out of those conventions if you need to, and too often, no way to override or replace core framework classes.
 
-Lithium is the first framework to give you the best of both worlds, without compromising either. In fact, Lithium's API is intentionally designed to allow you to "grow out of" the framework and into your own custom code over the course of your application's lifecycle, if your needs require.
+li3 is the first framework to give you the best of both worlds, without compromising either. In fact, li3's API is intentionally designed to allow you to "grow out of" the framework and into your own custom code over the course of your application's lifecycle, if your needs require.
 
 ### Technology
 
-Lithium takes full advantage of the latest PHP 5.3 features, including namespaces, late static binding and closures. Lithium's innovative [method filter system](http://li3.me/docs/lithium/util/collection/Filters) makes extensive use of closures and anonymous functions to allow application developers to "wrap" framework method calls, intercepting parameters before, and return values after.
+li3 takes full advantage of the latest PHP 5.3 features, including namespaces, late static binding and closures. li3's innovative [method filter system](http://li3.me/docs/lithium/util/collection/Filters) makes extensive use of closures and anonymous functions to allow application developers to "wrap" framework method calls, intercepting parameters before, and return values after.
 
-Lithium also complies with the PHP 5.3 namespacing standard, allowing you to easily integrate other PHP 5.3 standard libraries and frameworks with Lithium applications, and vice-versa.
+li3 also complies with the PHP 5.3 namespacing standard, allowing you to easily integrate other PHP 5.3 standard libraries and frameworks with li3 applications, and vice-versa.
 
-Lithium integrates the latest storage technologies, including MongoDB, CouchDB and Redis, with plugin support for Cassandra, ElasticSearch and others.
+li3 integrates the latest storage technologies, including MongoDB, CouchDB and Redis, with plugin support for Cassandra, ElasticSearch and others.
 
 ### Flexibility
 
-Lithium gives you full control over your application, from filters to dynamically modify framework internals, to dynamic dependencies to extend and replace core classes with application or plugin classes, to heavy use of adapter-oriented configurations, to make it seamless to move between different technologies and options.
+li3 gives you full control over your application, from filters to dynamically modify framework internals, to dynamic dependencies to extend and replace core classes with application or plugin classes, to heavy use of adapter-oriented configurations, to make it seamless to move between different technologies and options.
 
-Every component of the Lithium framework stack is replaceable through the robust plugin architecture. Swap out the default ORM / ODM implementation for [Doctrine 2](https://github.com/mariano/li3_doctrine2/) or [PHP ActiveRecord](https://github.com/greut/li3_activerecord). Don't like the templating? Use [Twig](https://github.com/UnionOfRAD/li3_twig), [Mustache](https://github.com/bruensicke/li3_mustache), or roll your own.
+Every component of the li3 framework stack is replaceable through the robust plugin architecture. Swap out the default ORM / ODM implementation for [Doctrine 2](https://github.com/mariano/li3_doctrine2/) or [PHP ActiveRecord](https://github.com/greut/li3_activerecord). Don't like the templating? Use [Twig](https://github.com/UnionOfRAD/li3_twig), [Mustache](https://github.com/bruensicke/li3_mustache), or roll your own.
 
 If you don't even need to write a full application, build a micro-app in a single file using the routing system, without giving up the maintainability of the framework's structure.
 

console/README.md

@@ -11,7 +11,7 @@ request/response flow. In that commands are quite similar to controllers.
 Commands don't leverage the full MVC as they don't utilize views, but
 directly interact with the user through `in()` and `out()`.
 
-Lithium itself provides amongst others commands for creating new applications
+li3 itself provides amongst others commands for creating new applications
 or parts thereof. However commands can also be provided through other libraries
 or by your application. Commands running in the application context will have
 complete access to your application. This is especially useful to reuse
@@ -22,7 +22,7 @@ i.e. a cron-job.
 
 You invoke the console front-controller through one of the wrappers
 provided, as shown below. The examples shown are relative to the root directory
-of a standard Lithium  distribution. The first is for users on a *nix command
+of a standard li3  distribution. The first is for users on a *nix command
 line the second for users on a Windows system. Please note that the preceding
 `$` in examples always indicates things that you enter on the command line.
 

template/README.md

@@ -3,12 +3,14 @@
 ## Special syntax
 
 Views have a special syntax for outputting escaped text. The standard way to
-output escaped text in your views from Lithium is as follows: {{{
+output escaped text in your views from li3 is as follows: 
+
+```
 <?=$variable; ?>
-}}}
+```
 
 This is where a lot of confusion comes in, because it is commonly misunderstood
-that Lithium depends on `short_open_tags`, however, that's not the case. The
+that li3 depends on `short_open_tags`, however, that's not the case. The
 contents of a view are processed through a [tokenizer](template/view/Compiler) before
 it is included by PHP. The file is then `compiled` into the final PHP+HTML (or whatever
 other content type that is requested), which is then passed off to be fully rendered
@@ -31,6 +33,7 @@ contained in the shorthands syntax, it will be output as normal without being
 filtered. This is to make it easier to work with helpers that return markup.
 
 An example would be something like: 
+
 ```
 <?=$this->form->create(); ?>
 ... my form here ...
@@ -100,7 +103,7 @@ plugin.
 
 ## Extending core helpers
 
-Because your application and plugins have a higher order-of-precedence than the Lithium core,
+Because your application and plugins have a higher order-of-precedence than the li3 core,
 classes like helpers can be extended and replaced seamlessly, without any changes to your templates.
 
 For example, to add or replace methods in the `Form` helper, you can add the following to