summaryrefslogtreecommitdiffstats
path: root/src/network/access
diff options
context:
space:
mode:
authorIevgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>2022-10-18 11:23:24 +0200
committerIevgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>2022-10-18 18:09:55 +0200
commitdd0eb89d2e3b196343cbf322b0f35ea0b54f0814 (patch)
treeff4e6188e58de9d704ad78fdd0c80bce524d72e2 /src/network/access
parent9e5e330a09607c62fa440f6222cb75005be12b01 (diff)
QNetworkReply: Fix typos in the documentation
Fixes: QTBUG-107719 Pick-to: 5.15 6.2 6.4 Change-Id: Ic5bbc59aebeb44595cfde000bfd1cfb28991d311 Reviewed-by: MÃ¥rten Nordheim <marten.nordheim@qt.io>
Diffstat (limited to 'src/network/access')
-rw-r--r--src/network/access/qnetworkreply.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/network/access/qnetworkreply.cpp b/src/network/access/qnetworkreply.cpp
index 8095a4591d..335a0131ff 100644
--- a/src/network/access/qnetworkreply.cpp
+++ b/src/network/access/qnetworkreply.cpp
@@ -42,7 +42,7 @@ QNetworkReplyPrivate::QNetworkReplyPrivate()
itself.
QNetworkReply is a sequential-access QIODevice, which means that
- once data is read from the object, it no longer kept by the
+ once data is read from the object, it is no longer kept by the
device. It is therefore the application's responsibility to keep
this data if it needs to. Whenever more data is received from the
network and processed, the readyRead() signal is emitted.
@@ -331,7 +331,7 @@ QNetworkReplyPrivate::QNetworkReplyPrivate()
processing. After this signal is emitted, there will be no more
updates to the reply's data or metadata.
- Unless close() or abort() have been called, the reply will be still be opened
+ Unless close() or abort() have been called, the reply will still be opened
for reading, so the data can be retrieved by calls to read() or
readAll(). In particular, if no calls to read() were made as a
result of readyRead(), a call to readAll() will retrieve the full