README.md in celluloid-0.12.4 vs README.md in celluloid-0.13.0.pre
- old
+ new
@@ -1,10 +1,10 @@
=========
[](http://travis-ci.org/celluloid/celluloid)
[](https://gemnasium.com/celluloid/celluloid)
-[](https://codeclimate.com/github/celluloid/celluloid)
+[](https://codeclimate.com/github/celluloid/celluloid)
> "I thought of objects being like biological cells and/or individual
> computers on a network, only able to communicate with messages"
> _--Alan Kay, creator of Smalltalk, on the meaning of "object oriented programming"_
@@ -43,11 +43,11 @@
* __Fault-tolerance:__ Celluloid has taken to heart many of Erlang's ideas
about fault-tolerance in order to enable self-healing applications.
The central idea: have you tried turning it off and on again? Celluloid
takes care of rebooting subcomponents of your application when they crash,
whether it's a single actor, or large (potentially multi-tiered) groups of
- actors that are all interdependent. This means rather that worrying about
+ actors that are all interdependent. This means rather than worrying about
rescuing every last exception, you can just sit back, relax, and let parts
of your program crash, knowing Celluloid will automatically reboot them in
a clean state. Celluloid provides its own implementation of the core
fault-tolerance concepts in Erlang including [linking](https://github.com/celluloid/celluloid/wiki/Linking),
[supervisors](https://github.com/celluloid/celluloid/wiki/Supervisors),
@@ -139,7 +139,7 @@
* If I've accepted a patch, feel free to ask for commit access
License
-------
-Copyright (c) 2012 Tony Arcieri. Distributed under the MIT License. See
+Copyright (c) 2013 Tony Arcieri. Distributed under the MIT License. See
LICENSE.txt for further details.