[Nbd] [PATCH] doc: Cleanup to info extension thanks to synchronous haggling

[Eric Blake <eblake@...696...>]

Now that we require at most one in-flight option request, we
can simplify the wording related to handling of NBD_OPT_GO
replies.

Signed-off-by: Eric Blake <eblake@...696...>
---

extension-info branch

 doc/proto.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/doc/proto.md b/doc/proto.md
index e1f3848..4093055 100644
--- a/doc/proto.md
+++ b/doc/proto.md
@@ -947,11 +947,9 @@ of the newstyle negotiation.
     with `NBD_REP_ACK`), the client and the server both immediately
     enter the transmission phase. The server MUST NOT send any zero
     padding bytes after the `NBD_REP_ACK` data, whether or not the
-    client negotiated the `NBD_FLAG_C_NO_ZEROES` flag. The server MUST
-    NOT send the final `NBD_REP_ACK` reply until all other pending
-    option replies have been sent by the server, and a client MUST NOT
-    send any further option requests after `NBD_OPT_GO` unless it
-    first receives an error reply.
+    client negotiated the `NBD_FLAG_C_NO_ZEROES` flag. The client MUST
+    NOT send further option requests unless the final reply from the
+    server indicates an error.

 - `NBD_OPT_GO` (7)

-- 
2.5.5