diff --git a/README.md b/README.md
index 1e95b3a..a1644f3 100644
--- a/README.md
+++ b/README.md
@@ -54,12 +54,12 @@ unknown fields survive untouched.
   - A node present in only one backend always appears (falls back to whichever
     backend actually returned facts for it).
 - **`/reports`, `/events`** — **union**, not a per-node winner. Reports are
-  immutable history, so a node that moved between PuppetDBs legitimately has
-  reports in both and both belong in the merged view. Reports dedupe
-  on `hash`; events, which carry no id of their own, dedupe on the verbatim
-  record (a node briefly reporting to both PuppetDBs stores identical records in
-  each). Records the merge cannot key — `extract`/`group_by` aggregate rows — are
-  never deduped, so every backend's rows pass through even when byte-identical;
+  immutable history, so a node's reports can legitimately exist in more than one
+  backend and all of them belong in the merged view. Reports dedupe on `hash`;
+  events, which carry no id of their own, dedupe on the verbatim record (a node
+  reporting to more than one backend stores identical records in each). Records
+  the merge cannot key — `extract`/`group_by` aggregate rows — are never
+  deduped, so every backend's rows pass through even when byte-identical;
   summing those aggregates across backends is not implemented yet.
 
 ### Paging and ordering on the merged endpoints