From a40be647591004f285a0074dc910a2dc59d1ecdb Mon Sep 17 00:00:00 2001 From: Ievgenii Meshcheriakov Date: Tue, 18 Oct 2022 11:23:24 +0200 Subject: [PATCH] QNetworkReply: Fix typos in the documentation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes: QTBUG-107719 Change-Id: Ic5bbc59aebeb44595cfde000bfd1cfb28991d311 Reviewed-by: Mårten Nordheim (cherry picked from commit dd0eb89d2e3b196343cbf322b0f35ea0b54f0814) Reviewed-by: Qt Cherry-pick Bot --- src/network/access/qnetworkreply.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/network/access/qnetworkreply.cpp b/src/network/access/qnetworkreply.cpp index 8095a4591de..335a0131ff0 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