From 4a81ee1a2c614fc12b28c4967097b48d4c697daf Mon Sep 17 00:00:00 2001 From: Hassan Mohamed <104525221+Moe-Hassan-123@users.noreply.github.com> Date: Sat, 9 Dec 2023 21:59:25 +0200 Subject: [PATCH] fix typo in filtering.md qeryset to queryset --- docs/docs/guides/input/filtering.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/guides/input/filtering.md b/docs/docs/guides/input/filtering.md index eab93d5b6..f7de6985b 100644 --- a/docs/docs/guides/input/filtering.md +++ b/docs/docs/guides/input/filtering.md @@ -62,7 +62,7 @@ By default, the filters will behave the following way: * `None` values will be ignored and not filtered against; * Every non-`None` field will be converted into a `Q`-expression based on the `Field` definition of each field; * All `Q`-expressions will be merged into one using `AND` logical operator; -* The resulting `Q`-expression is used to filter the queryset and return you a qeryset with a `.filter` clause applied. +* The resulting `Q`-expression is used to filter the queryset and return you a queryset with a `.filter` clause applied. ## Customizing Fields By default, `FilterSet` will use the field names to generate Q expressions: @@ -182,4 +182,4 @@ class BookFilterSchema(FilterSchema): ) return q ``` -The `custom_expression` method takes precedence over any other definitions described earlier, including `filter_` methods. \ No newline at end of file +The `custom_expression` method takes precedence over any other definitions described earlier, including `filter_` methods.