From d9c934debd877b18fa349bf628021784eb71ed40 Mon Sep 17 00:00:00 2001 From: Adrian Mester Date: Thu, 23 Jul 2015 13:10:20 +0300 Subject: [PATCH] fixed a typo in docs --- docs/api-guide/serializers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-guide/serializers.md b/docs/api-guide/serializers.md index 2f13bd2a4..abdb67afa 100644 --- a/docs/api-guide/serializers.md +++ b/docs/api-guide/serializers.md @@ -565,7 +565,7 @@ Typically we would recommend *not* using inheritance on inner Meta classes, but The ModelSerializer class also exposes an API that you can override in order to alter how serializer fields are automatically determined when instantiating the serializer. -Normally if a `ModelSerializer` does not generate the fields you need by default the you should either add them to the class explicitly, or simply use a regular `Serializer` class instead. However in some cases you may want to create a new base class that defines how the serializer fields are created for any given model. +Normally if a `ModelSerializer` does not generate the fields you need by default then you should either add them to the class explicitly, or simply use a regular `Serializer` class instead. However in some cases you may want to create a new base class that defines how the serializer fields are created for any given model. ### `.serializer_field_mapping`