From 1148fea3dcf33219140a629067355e83d97b6c8c Mon Sep 17 00:00:00 2001 From: sai09111995 Date: Mon, 2 Feb 2026 15:22:01 +0530 Subject: [PATCH] Improve clarity in APIView documentation --- docs/api-guide/views.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/api-guide/views.md b/docs/api-guide/views.md index 9c9bd9af6a..5b7e8692c0 100644 --- a/docs/api-guide/views.md +++ b/docs/api-guide/views.md @@ -10,7 +10,8 @@ source: > > — [Reinout van Rees][cite] -REST framework provides an `APIView` class, which subclasses Django's `View` class. +REST framework provides an `APIView` class, which subclasses Django’s base `View` class. + `APIView` classes are different from regular `View` classes in the following ways: @@ -19,7 +20,9 @@ REST framework provides an `APIView` class, which subclasses Django's `View` cla * Any `APIException` exceptions will be caught and mediated into appropriate responses. * Incoming requests will be authenticated and appropriate permission and/or throttle checks will be run before dispatching the request to the handler method. -Using the `APIView` class is pretty much the same as using a regular `View` class, as usual, the incoming request is dispatched to an appropriate handler method such as `.get()` or `.post()`. Additionally, a number of attributes may be set on the class that control various aspects of the API policy. +Using the `APIView` class is very similar to using a regular Django `View` class. +As usual, the incoming request is dispatched to an appropriate handler method such as `.get()` or `.post()`. + For example: