--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/.ffignore Wed Aug 17 16:00:24 2016 +0000
@@ -0,0 +1,1 @@
+docs/build/
--- a/docs/02-overview.markdown Fri Aug 12 19:57:26 2016 +0000
+++ b/docs/02-overview.markdown Wed Aug 17 16:00:24 2016 +0000
@@ -57,10 +57,10 @@
powerful. You can use `typep`, generic methods, before/after/around methods,
and everything else CLOS gives you.
-Like every engineering decision this comes with are tradeoffs. You can't
-(easily) add or remove aspects to/from a particular entity at runtime like you
-can with cl-ecs. And there's no way to give an entity multiple "copies" of
-a single aspect.
+Like every engineering decision this comes with tradeoffs. You can't (easily)
+add or remove aspects to/from a particular entity at runtime like you can with
+cl-ecs. And there's no way to give an entity multiple "copies" of a single
+aspect.
The author has found this approach to work well for his needs. You should take
a look at both approaches and decide which is best for you. If you want to read
--- a/docs/index.markdown Fri Aug 12 19:57:26 2016 +0000
+++ b/docs/index.markdown Wed Aug 17 16:00:24 2016 +0000
@@ -2,7 +2,7 @@
Lisp. It's a thin layer of sugar over CLOS that makes it easy to write flexible
objects for video games.
-Check out the [Overview](./overview/) for a five-minute description of what
+Check out the [Overview](./overview/) for a three-minute description of what
this is, or the [Usage](./usage/) for a full rundown.
* **License:** MIT/X11