anchor.diff:  %%                                  the BKey asked for.  The returned object's
   %%                                  BKey is constant, so any part of Riak that
   %%                                  cares about matching/valid BKey inside of
  -%%                                  the object will be confused and/or break.
  +%%                                  the object will be confused and/or break.</li>
   %% <li>`yessir_aae_mode_encoding' - Specify which mode of behavior to
   %%                                  use when interacting with Riak KV's
  -%%                                  anti-entropy mode for put & put_object
  +%%                                  anti-entropy mode for put and put_object
   %%                                  calls.
   %%   <ul>
   %%   <li>`constant_binary' - The default mode: lie to AAE by returning
  -%%                           a constant binary, <<>>.</li>  This will cause
  +%%                           a constant binary, `<<>>'. This will cause
   %%                           AAE to maintain a tiny tree of order-size(1).
   %%                           This is the fastest mode but also causes the
   %%                           least amount of AAE work and thus may or may
   %%                           not meet all users' needs. </li>
  -%%   <li>`bkey' </li> - Return term_to_binary({Bucket, Key}), which will
  +%%   <li>`bkey' - Return term_to_binary({Bucket, Key}), which will
   %%                      cause AAE's tree to churn with order-size(NumKeys)
   %%                      but will be much smaller than the entire serialized
   %%                      #r_object{}, so AAE will spend less CPU time during
   %%                      its processing. </li>
  -%%   <li>`r_object' </li> - Serialize the entire #r_object{}, like Riak KV
  +%%   <li>`r_object' - Serialize the entire #r_object{}, like Riak KV
   %%                          does in normal operation.  This mode has the
   %%                          highest overhead per operation. </li>
  -%%   </ul>
  +%%   </ul></li>
   %% <li>`yessir_default_size' - The number of bytes of generated data for the value.</li>
   %% <li>`yessir_key_count'    - The number of keys that will be folded over, e.g. list_keys().</li>
   %% <li>`yessir_bucket_prefix_list'  - A list {BucketPrefixBin, {Module, Fun}}
  
positive.code: %%   previously-put keys or to correlate get values with previously-put
  %%   values.
  %%   - Get operation keys that are formatted in with the convention
  %%     <<"yessir.{integer}.anything">> will use integer (interpreted in
  %%     base 10) as the returned binary's Size.
  %%
  %% fold_keys and fold_objects are implemented for both sync and async.
  
negative.code: %%     for some simulations.
  %% * Is there a need for simulations for get to return different vclocks?
  %% * Add variable latency before responding.  This callback API is
  %%   synchronous, but adding constant- and uniform- and pareto-distributed
  %%   delays would simulate disk `I/O' latencies because all other backend
  %%   APIs are also synchronous.
  
  -module(riak_kv_yessir_backend).
  