deletions | additions       diff --git a/Implementation.md b/Implementation.md  index 7eac797..a5dc311 100644  --- a/Implementation.md  +++ b/Implementation.md 
...
- display: `read`  - like: `incr >> read` (or `fetch_add`)  - new: `write`  diff --git a/Questions.md b/Questions.md  index 0936ec3..aa77702 100644  --- a/Questions.md  +++ b/Questions.md 
...
- Redis? ("data structures server", but not designed to be consistent across replicas)  - would people take this seriously if it was a modification to Redis?  - Tapir?  -Doppel? (Phase Reconciliation paper)  - code not (yet) available  -  Lynx / Rococo (geo-replicated, explicit transaction chains)  - Distributed Rococo (distributed  key/value store store, reorder pieces of transactions to ensure strict serializability)  - Existing DTM framework  - HyFlow (Scala)  - how best to evaluate? 
...
- what's the minimal set of features to make this interesting?  - combining ops w/o replication?  - combining & replication w/o multi-object transactions?  - all? - What's the difference between "strict serializability" vs just "serializability"?  - for instance, Rococo differentiates itself from Lynx this way (Rococo is strictly serializable, Lynx just serializable)