aboutsummaryrefslogtreecommitdiffstats
path: root/docs/api-guide
diff options
context:
space:
mode:
authorVita Smid2014-02-14 10:44:02 +0100
committerVita Smid2014-02-14 10:44:02 +0100
commit821f8488023cb5161eb0f69b9121f6d956c39baf (patch)
treebd5735ec7763b6339f0c1185fbf4461c0aa40a7c /docs/api-guide
parentaaa58852326ecf98785de853a71c8a6f19a0cb7e (diff)
downloaddjango-rest-framework-821f8488023cb5161eb0f69b9121f6d956c39baf.tar.bz2
Minor typos fixed in api-guide/testing.md (request -> response).
Diffstat (limited to 'docs/api-guide')
-rw-r--r--docs/api-guide/testing.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/api-guide/testing.md b/docs/api-guide/testing.md
index 4a8a9168..72c33961 100644
--- a/docs/api-guide/testing.md
+++ b/docs/api-guide/testing.md
@@ -218,12 +218,12 @@ You can use any of REST framework's test case classes as you would for the regul
When checking the validity of test responses it's often more convenient to inspect the data that the response was created with, rather than inspecting the fully rendered response.
-For example, it's easier to inspect `request.data`:
+For example, it's easier to inspect `response.data`:
response = self.client.get('/users/4/')
self.assertEqual(response.data, {'id': 4, 'username': 'lauren'})
-Instead of inspecting the result of parsing `request.content`:
+Instead of inspecting the result of parsing `response.content`:
response = self.client.get('/users/4/')
self.assertEqual(json.loads(response.content), {'id': 4, 'username': 'lauren'})