diff --git a/content/docs/rfcs/34/README.md b/content/docs/rfcs/34/README.md
index fc47e723..93707833 100644
--- a/content/docs/rfcs/34/README.md
+++ b/content/docs/rfcs/34/README.md
@@ -49,7 +49,8 @@ To get the best anonymity properties with respect to response peer sets, respond
 
 To save bandwidth, and as a trade off to anonymity,
 responders MAY maintain a larger cache of exchange peers and randomly sample response sets from this local cache.
-This local cache SHOULD store peers by `cluster_id`/`shard` for faster retrieval. For peers without shard info, cache can maintain another list of peers.
+This local cache SHOULD store peers by `cluster_id`/`shard` for faster retrieval.
+For peers without shard info, the cache can maintain a separate set of peers.
 The size of each `cluster_id`/`shard` pair being maintained in cache SHOULD be large enough to allow randomly sampling peer sets that (on average) do not overlap too much.
 The responder SHOULD periodically replace the oldest peers in the cache.
 This document provides recommended choices for the cache size in the [Implementation Suggestions Section](#implementation-suggestions).