Fix grammar and article usage in documentation

- Fix verb agreement in lifecycle.rst: 'creates and send' -> 'creates and sends'
- Fix article usage: 'a HTTP' -> 'an HTTP' in quickstart.rst and errorhandling.rst
This commit is contained in:
alaa 2025-08-01 22:36:19 +01:00
parent 85c5d93cbd
commit 0e8dc9f269
3 changed files with 3 additions and 3 deletions

View file

@ -261,7 +261,7 @@ Custom Error Pages
Sometimes when building a Flask application, you might want to raise a Sometimes when building a Flask application, you might want to raise a
:exc:`~werkzeug.exceptions.HTTPException` to signal to the user that :exc:`~werkzeug.exceptions.HTTPException` to signal to the user that
something is wrong with the request. Fortunately, Flask comes with a handy something is wrong with the request. Fortunately, Flask comes with a handy
:func:`~flask.abort` function that aborts a request with a HTTP error from :func:`~flask.abort` function that aborts a request with an HTTP error from
werkzeug as desired. It will also provide a plain black and white error page werkzeug as desired. It will also provide a plain black and white error page
for you with a basic description, but nothing fancy. for you with a basic description, but nothing fancy.

View file

@ -83,7 +83,7 @@ will return data that is translated into an HTTP response.
to a view function, handle errors, etc. to a view function, handle errors, etc.
#. Flask translates View function return into WSGI response data, passes it to WSGI #. Flask translates View function return into WSGI response data, passes it to WSGI
server. server.
#. WSGI server creates and send an HTTP response. #. WSGI server creates and sends an HTTP response.
#. Client receives the HTTP response. #. Client receives the HTTP response.

View file

@ -535,7 +535,7 @@ attributes mentioned above::
What happens if the key does not exist in the ``form`` attribute? In that What happens if the key does not exist in the ``form`` attribute? In that
case a special :exc:`KeyError` is raised. You can catch it like a case a special :exc:`KeyError` is raised. You can catch it like a
standard :exc:`KeyError` but if you don't do that, a HTTP 400 Bad Request standard :exc:`KeyError` but if you don't do that, an HTTP 400 Bad Request
error page is shown instead. So for many situations you don't have to error page is shown instead. So for many situations you don't have to
deal with that problem. deal with that problem.