Incorporate details from ML thread
diff --git a/rfcs/018-sharded-changes-feeds.md b/rfcs/018-sharded-changes-feeds.md
index fdeb3a1..4f28b9d 100644
--- a/rfcs/018-sharded-changes-feeds.md
+++ b/rfcs/018-sharded-changes-feeds.md
@@ -206,13 +206,18 @@
`GET /db/_changes/<ShardID>`
-will provide the change feed for a given shard using all the same semantics as
-the current changes endpoint, while
+will provide the change feed for a given shard using JSONL for all responses,
+but otherwise matching the existing format of the changes feed, while
`GET /db/_changes/_meta?since=N`
can be used to retrieve the shard topology as of a particular sequence.
+`POST /db/_changes/_reshard {"shard_count": 4}`
+
+would update the number of shards in the database. We would cap the maximum
+number of shards that a database could have as a server-wide config setting.
+
## HTTP API deprecations
None, although the shard-level endpoint above would be recommended over the
