aboutsummaryrefslogtreecommitdiffstats
path: root/docs/api-guide/routers.md
diff options
context:
space:
mode:
authorStephan Groß2013-05-28 07:39:56 -0700
committerStephan Groß2013-05-28 07:39:56 -0700
commitf6d7f54fc15ed3bb97b1d97ff1ecaf99e933660e (patch)
treea1c18df58b9b8ae459d1c36ff083855e6c942844 /docs/api-guide/routers.md
parent22e1950e1cca237e6edeea3ddc9c798b975c6183 (diff)
parent8f35ac4f93c608eaced3f48a46e8922104e09182 (diff)
downloaddjango-rest-framework-f6d7f54fc15ed3bb97b1d97ff1ecaf99e933660e.tar.bz2
Merge pull request #897 from pborreli/typos
Fixed typos
Diffstat (limited to 'docs/api-guide/routers.md')
-rw-r--r--docs/api-guide/routers.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/api-guide/routers.md b/docs/api-guide/routers.md
index 6588d7e5..fd3a15d5 100644
--- a/docs/api-guide/routers.md
+++ b/docs/api-guide/routers.md
@@ -85,7 +85,7 @@ This router is similar to `SimpleRouter` as above, but additionally includes a d
# Custom Routers
-Implementing a custom router isn't something you'd need to do very often, but it can be useful if you have specfic requirements about how the your URLs for your API are strutured. Doing so allows you to encapsulate the URL structure in a reusable way that ensures you don't have to write your URL patterns explicitly for each new view.
+Implementing a custom router isn't something you'd need to do very often, but it can be useful if you have specific requirements about how the your URLs for your API are strutured. Doing so allows you to encapsulate the URL structure in a reusable way that ensures you don't have to write your URL patterns explicitly for each new view.
The simplest way to implement a custom router is to subclass one of the existing router classes. The `.routes` attribute is used to template the URL patterns that will be mapped to each viewset.