From 0d8d8ea6815b36f7901f1126ec0fc263c1348e9d Mon Sep 17 00:00:00 2001 From: Asif Saif Uddin Date: Tue, 22 Nov 2022 14:34:52 +0600 Subject: [PATCH] Update docs/tutorial/6-viewsets-and-routers.md --- docs/tutorial/6-viewsets-and-routers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/6-viewsets-and-routers.md b/docs/tutorial/6-viewsets-and-routers.md index e8a85c0e1..74789e337 100644 --- a/docs/tutorial/6-viewsets-and-routers.md +++ b/docs/tutorial/6-viewsets-and-routers.md @@ -59,7 +59,7 @@ Custom actions which use the `@action` decorator will respond to `GET` requests The URLs for custom actions by default depend on the method name itself. If you want to change the way url should be constructed, you can include `url_path` as a decorator keyword argument. -## Binding view sets to URLs explicitly +## Binding ViewSets to URLs explicitly The handler methods only get bound to the actions when we define the URLConf. To see what's going on under the hood let's first explicitly create a set of views from our ViewSets.