From 8ee3cc72c3141568f612dac3b66b3881f023b5ef Mon Sep 17 00:00:00 2001 From: Tejas Kumar Date: Fri, 29 Jun 2018 22:34:55 +0200 Subject: [PATCH] Update Section 6 -- Execution.md (#469) Fixed typo in spec: acknoledgment -> acknowledgement --- spec/Section 6 -- Execution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index e8ff7bb99..c851d6634 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -235,7 +235,7 @@ connectivity. GraphQL subscriptions do not require any specific serialization format or transport mechanism. Subscriptions specifies algorithms for the creation of a stream, the content of each payload on that stream, and the closing of that -stream. There are intentionally no specifications for message acknoledgement, +stream. There are intentionally no specifications for message acknowledgement, buffering, resend requests, or any other quality of service (QoS) details. Message serialization, transport mechanisms, and quality of service details should be chosen by the implementing service.