Skip to content

Commit 781890b

Browse files
authored
docs(api-guide-testing): Fix typo 'CRSF' and plural of word (encode#8238)
1 parent 00cd4ef commit 781890b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/api-guide/testing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,7 @@ If you're using `SessionAuthentication` then you'll need to include a CSRF token
234234
for any `POST`, `PUT`, `PATCH` or `DELETE` requests.
235235

236236
You can do so by following the same flow that a JavaScript based client would use.
237-
First make a `GET` request in order to obtain a CRSF token, then present that
237+
First, make a `GET` request in order to obtain a CSRF token, then present that
238238
token in the following request.
239239

240240
For example...
@@ -259,7 +259,7 @@ With careful usage both the `RequestsClient` and the `CoreAPIClient` provide
259259
the ability to write test cases that can run either in development, or be run
260260
directly against your staging server or production environment.
261261

262-
Using this style to create basic tests of a few core piece of functionality is
262+
Using this style to create basic tests of a few core pieces of functionality is
263263
a powerful way to validate your live service. Doing so may require some careful
264264
attention to setup and teardown to ensure that the tests run in a way that they
265265
do not directly affect customer data.

0 commit comments

Comments
 (0)