From 39f177b5eb900374bf033fd8023d259b3ec95769 Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <richard@matrix.org>
Date: Sat, 18 Feb 2017 20:02:59 +0000
Subject: [PATCH] e2e guide: fix /claim response

---
 .../guides/2016-10-18-e2e_implementation.rst  | 22 ++++++++++---------
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/supporting-docs/guides/2016-10-18-e2e_implementation.rst b/supporting-docs/guides/2016-10-18-e2e_implementation.rst
index d0e1ca5b..39a51d3f 100644
--- a/supporting-docs/guides/2016-10-18-e2e_implementation.rst
+++ b/supporting-docs/guides/2016-10-18-e2e_implementation.rst
@@ -654,20 +654,22 @@ This will return a result as follows:
 .. code:: json
 
   {
-    "<user id>": {
-      "<device_id>": {
-        "signed_curve25519:<key_id>": {
-          "key": "<curve25519_key>",
-          "signatures": {
-            "<user_id>": {
-              "ed25519:<device_id>": "<signature>"
+    "one_time_keys": {
+      "<user id>": {
+        "<device_id>": {
+          "signed_curve25519:<key_id>": {
+            "key": "<curve25519_key>",
+            "signatures": {
+              "<user_id>": {
+                "ed25519:<device_id>": "<signature>"
+              }
             }
-          }
+          },
         },
+        ...
       },
       ...
-    },
-    ...
+    }
   }
 
 The client should first check the signatures on the signed key objects. As with