cf596da94297

--- a/beast/index.html	Fri Aug 12 19:57:04 2016 +0000
+++ b/beast/index.html	Wed Aug 17 16:00:33 2016 +0000
@@ -15,7 +15,7 @@
 <p>Beast is a <strong>B</strong>asic <strong>E</strong>ntity/<strong>A</strong>spect/<strong>S</strong>ystem <strong>T</strong>oolkit for Common
 Lisp.  It's a thin layer of sugar over CLOS that makes it easy to write flexible
 objects for video games.</p>
-<p>Check out the <a href="./overview/">Overview</a> for a five-minute description of what
+<p>Check out the <a href="./overview/">Overview</a> for a three-minute description of what
 this is, or the <a href="./usage/">Usage</a> for a full rundown.</p>
 <ul>
 <li><strong>License:</strong> MIT/X11</li>

--- a/beast/overview/index.html	Fri Aug 12 19:57:04 2016 +0000
+++ b/beast/overview/index.html	Wed Aug 17 16:00:33 2016 +0000
@@ -65,10 +65,10 @@
 <p>Beast tries to be just a very thin layer over CLOS, because CLOS is quite
 powerful.  You can use <code>typep</code>, generic methods, before/after/around methods,
 and everything else CLOS gives you.</p>
-<p>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.</p>
+<p>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.</p>
 <p>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
 more, check out the <a href="../usage/">Usage</a> document.</p>