diff options
| author | José Padilla | 2014-11-29 14:43:05 -0400 | 
|---|---|---|
| committer | José Padilla | 2014-11-29 14:43:05 -0400 | 
| commit | 731c8421afe3093a78cdabb9c3cc28fa52cd1c8e (patch) | |
| tree | bcbcfcfb32d0ab0e59605a5564cf320913767d6d /docs/tutorial | |
| parent | 3a5b3772fefc3c2f2c0899947cbc07bfe6e6b5d2 (diff) | |
| download | django-rest-framework-731c8421afe3093a78cdabb9c3cc28fa52cd1c8e.tar.bz2 | |
Remove YAML support from core
Diffstat (limited to 'docs/tutorial')
| -rw-r--r-- | docs/tutorial/2-requests-and-responses.md | 2 | 
1 files changed, 1 insertions, 1 deletions
| diff --git a/docs/tutorial/2-requests-and-responses.md b/docs/tutorial/2-requests-and-responses.md index f377c712..06a684b1 100644 --- a/docs/tutorial/2-requests-and-responses.md +++ b/docs/tutorial/2-requests-and-responses.md @@ -92,7 +92,7 @@ Here is the view for an individual snippet, in the `views.py` module.  This should all feel very familiar - it is not a lot different from working with regular Django views. -Notice that we're no longer explicitly tying our requests or responses to a given content type.  `request.data` can handle incoming `json` requests, but it can also handle `yaml` and other formats.  Similarly we're returning response objects with data, but allowing REST framework to render the response into the correct content type for us. +Notice that we're no longer explicitly tying our requests or responses to a given content type.  `request.data` can handle incoming `json` requests, but it can also handle other formats.  Similarly we're returning response objects with data, but allowing REST framework to render the response into the correct content type for us.  ## Adding optional format suffixes to our URLs | 
