From b121feebce9524eb1ce4102bc0c012369c85a3d5 Mon Sep 17 00:00:00 2001
From: Erik Johnston <erik@matrix.org>
Date: Fri, 30 Sep 2016 11:24:51 +0100
Subject: [PATCH] Comment what the is_direct flag actually does

---
 api/client-server/create_room.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/api/client-server/create_room.yaml b/api/client-server/create_room.yaml
index 2e7cc0ad..87289682 100644
--- a/api/client-server/create_room.yaml
+++ b/api/client-server/create_room.yaml
@@ -179,6 +179,8 @@ paths:
                   as should the inviter. This is to keep the intent for new rooms
                   synchronised at first. Both users may subsequently choose to
                   tag the room differently.
+                  This adds an ``is_direct`` flag to the content of any invites
+                  sent.
       responses:
         200:
           description: Information about the newly created room.