summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKai Koehne <kai.koehne@theqtcompany.com>2016-04-07 08:41:17 +0200
committerKai Koehne <kai.koehne@qt.io>2016-08-12 13:14:31 +0000
commitef7b03e3e5e20f89963bae799f7ecb753f332c34 (patch)
treec701ab72aa590f2e2e763ea000378a7545f8a6e1
parente66dcd51d0e5517e88cd59912fd08501522a2902 (diff)
downloadqtwebsockets-ef7b03e3e5e20f89963bae799f7ecb753f332c34.tar.gz
Doc: Add verb to WebSockets introv5.6.25.6.2
Change-Id: I4c9f3a50c24f945c0f14010a10ff808d8adf7845 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
-rw-r--r--src/websockets/doc/src/overview.qdoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/websockets/doc/src/overview.qdoc b/src/websockets/doc/src/overview.qdoc
index eb9e429..e85461a 100644
--- a/src/websockets/doc/src/overview.qdoc
+++ b/src/websockets/doc/src/overview.qdoc
@@ -39,7 +39,7 @@ Historically, web applications that needed bidirectional communication or
push notifications had to use one of the HTTP-based solutions available. These
solutions employed different techniques such as polling, long-polling, and
streaming, to overcome the limitations of HTTP protocol, which is not designed
-for such use cases. As a result, high network latency, unnecessary data
+for such use cases. This resulted in high network latency, unnecessary data
exchange, and stale or old data. The WebSocket offering by IETF helps to
overcome these problems to a large extent.