diff options
| author | Tom Christie | 2012-09-19 13:02:10 +0100 |
|---|---|---|
| committer | Tom Christie | 2012-09-19 13:02:10 +0100 |
| commit | 575630d7c34b8ee23dad379c4bbd01eba477e4a2 (patch) | |
| tree | 69f548477e891c65964a67b7c7805597854bfe37 /docs/tutorial/2-requests-and-responses.md | |
| parent | 5611769162a022dd7f297074089fe62a4d7f00b1 (diff) | |
| download | django-rest-framework-575630d7c34b8ee23dad379c4bbd01eba477e4a2.tar.bz2 | |
Use named links in tutorial docs
Diffstat (limited to 'docs/tutorial/2-requests-and-responses.md')
| -rw-r--r-- | docs/tutorial/2-requests-and-responses.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/tutorial/2-requests-and-responses.md b/docs/tutorial/2-requests-and-responses.md index ffc5f269..906f11d0 100644 --- a/docs/tutorial/2-requests-and-responses.md +++ b/docs/tutorial/2-requests-and-responses.md @@ -125,11 +125,11 @@ We don't necessarily need to add these extra url patterns in, but it gives us a ## How's it looking? -Go ahead and test the API from the command line, as we did in [tutorial part 1][2]. Everything is working pretty similarly, although we've got some nicer error handling if we send invalid requests. +Go ahead and test the API from the command line, as we did in [tutorial part 1][tut-1]. Everything is working pretty similarly, although we've got some nicer error handling if we send invalid requests. **TODO: Describe using accept headers, content-type headers, and format suffixed URLs** -Now go and open the API in a web browser, by visiting [http://127.0.0.1:8000/][3]." +Now go and open the API in a web browser, by visiting [http://127.0.0.1:8000/][devserver]." **Note: Right now the Browseable API only works with the CBV's. Need to fix that.** @@ -137,15 +137,15 @@ Now go and open the API in a web browser, by visiting [http://127.0.0.1:8000/][3 Because the API chooses a return format based on what the client asks for, it will, by default, return an HTML-formatted representation of the resource when that resource is requested by a browser. This allows for the API to be easily browsable and usable by humans. -See the [browsable api][4] topic for more information about the browsable API feature and how to customize it. +See the [browsable api][browseable-api] topic for more information about the browsable API feature and how to customize it. ## What's next? -In [tutorial part 3][4], we'll start using class based views, and see how generic views reduce the amount of code we need to write. +In [tutorial part 3][tut-3], we'll start using class based views, and see how generic views reduce the amount of code we need to write. [json-url]: http://example.com/api/items/4.json -[2]: 1-serialization.md -[3]: http://127.0.0.1:8000/ -[4]: ../topics/browsable-api.md -[5]: 3-class-based-views.md
\ No newline at end of file +[devserver]: http://127.0.0.1:8000/ +[browseable-api]: ../topics/browsable-api.md +[tut-1]: 1-serialization.md +[tut-3]: 3-class-based-views.md
\ No newline at end of file |