From dbba737135b063f3b00afb9d5fcece0698225b36 Mon Sep 17 00:00:00 2001
From: Daniel Wagner-Hall <daniel@matrix.org>
Date: Thu, 10 Dec 2015 15:47:27 +0000
Subject: [PATCH] Explain scope of uniqueness of txnid

---
 api/client-server/room_send.yaml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/api/client-server/room_send.yaml b/api/client-server/room_send.yaml
index 70d005c2..b7ccbcfb 100644
--- a/api/client-server/room_send.yaml
+++ b/api/client-server/room_send.yaml
@@ -48,8 +48,9 @@ paths:
           name: txnId
           type: string
           description: |-
-            The transaction ID for this event. Clients should generate a
-            unique ID; it will be used by the server to ensure idempotency of requests.
+            The transaction ID for this event. Clients should generate an
+            ID unique across requests with the same access token; it will be
+            used by the server to ensure idempotency of requests.
           required: true
           x-example: "35"
         - in: body