summaryrefslogtreecommitdiff
path: root/src/websockets/doc/src/overview.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'src/websockets/doc/src/overview.qdoc')
-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.