@@ -301,7 +301,7 @@ expected to return an updated response object.
301
301
302
302
.. note ::
303
303
The :ref: `request.g <The "g" Object >` object is a special object that allows
304
- the before and after request handlers, as well sa the route function to
304
+ the before and after request handlers, as well as the route function to
305
305
share data during the life of the request.
306
306
307
307
Error Handlers
@@ -500,7 +500,7 @@ contents as a file-like object.
500
500
Cookies
501
501
^^^^^^^
502
502
503
- Cookies that are sent by the client are made available throught the
503
+ Cookies that are sent by the client are made available through the
504
504
:attr: `cookies <microdot.Request.cookies> ` attribute of the request object in
505
505
dictionary form.
506
506
@@ -595,7 +595,7 @@ always returned to the client in the response body::
595
595
In the above example, Microdot issues a standard 200 status code response, and
596
596
inserts the necessary headers.
597
597
598
- The applicaton can provide its own status code as a second value returned from
598
+ The application can provide its own status code as a second value returned from
599
599
the route. The example below returns a 202 status code::
600
600
601
601
@app.get('/')
@@ -611,7 +611,7 @@ The next example returns an HTML response, instead of a default text response::
611
611
return '<h1>Hello, World!</h1>', 202, {'Content-Type': 'text/html'}
612
612
613
613
If the application needs to return custom headers, but does not need to change
614
- the default status code, then it can return two values, omitting the stauts
614
+ the default status code, then it can return two values, omitting the status
615
615
code::
616
616
617
617
@app.get('/')
@@ -753,7 +753,7 @@ Another option is to create a response object directly in the route function::
753
753
Standard cookies do not offer sufficient privacy and security controls, so
754
754
never store sensitive information in them unless you are adding additional
755
755
protection mechanisms such as encryption or cryptographic signing. The
756
- :ref: `session <Maintaing Secure User Sessions >` extension implements signed
756
+ :ref: `session <Maintaining Secure User Sessions >` extension implements signed
757
757
cookies that prevent tampering by malicious actors.
758
758
759
759
Concurrency
0 commit comments