Adapt the README to the new strategy style

Author: aspiwack

README.md

@@ -24,27 +24,26 @@ The Benign library is an attempt to address this gap. A difficulty is
 laziness. With laziness, things have a beginning (when the thunk is
 being forced), but not a well-defined end. So what do we measure the
 time of? The solution of the Benign library is to be less lazy. We
-keep laziness for algorithms, but use strict (or at least stricter)
-types to assemble bigger steps. It's fine to log or trace in pure
-code, since we don't consider that these observations are part of the
-semantics of the program.
+keep laziness for algorithms, but use evaluate more strictly when
+assembling bigger steps. It's fine to log or trace in pure code, since
+we don't consider that these observations are part of the semantics of
+the program.
 
 The Benign library provides facilities to create benign effects,
-including to use strict types to assemble these large steps.
+including evaluation strategies to express precisely how strict we
+want to be.
 
 The premise underlying all this, as well as the implementation of the
 library, is that logging or tracing is not very fast. So we don't want
 to log or trace in places where performance is really essential. This
 is why at the most inner level, where tight loops and algorithms live,
 laziness is not a problem: we are not going to log there, this would
-cost too much performance. At a more outer level, we can use
-strictness to make steps with a beginning and an end. It's ok if there
-is a cost in terms of conversion, this is not where we need to
-optimise too much. The library can, and does, prevent optimisation
-through its functions (note that cost-centre profiling also prevents
-optimisation through cost centres; it isn't surprising that we are
-having a similar problem). With the optimisation not working at that
-level, strictness is much less of a problem.
+cost too much performance. The library can, and does, prevent
+optimisation through its functions anyway (note that cost-centre
+profiling also prevents optimisation through cost centres; it isn't
+surprising that we are having a similar problem). So benign effects
+all must happen at rather macro steps, where we don't have to worry
+too much about the impact of evaluation.
 
 ## Backends