Clarify data correctness explanation in quickstart

Rephrase text for clarity regarding data correctness issues.
This commit is contained in:
ANUROOP 2026-01-27 19:14:28 +05:30 committed by GitHub
parent 798e006f43
commit 17e611808e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -801,8 +801,8 @@ Logging
.. versionadded:: 0.3 .. versionadded:: 0.3
Sometimes you might be in a situation where you deal with data that Sometimes you may encounter a situation where you deal with data that should be correct,
should be correct, but actually is not. For example you may have but is not.For example you may have
some client-side code that sends an HTTP request to the server some client-side code that sends an HTTP request to the server
but it's obviously malformed. This might be caused by a user tampering but it's obviously malformed. This might be caused by a user tampering
with the data, or the client code failing. Most of the time it's okay with the data, or the client code failing. Most of the time it's okay