From f1ca370d877befb4570a1578d9bcef764953bbba Mon Sep 17 00:00:00 2001 From: Arden Kirkland Date: Sat, 8 May 2021 00:03:22 -0400 Subject: [PATCH] Update understandingFilters.rst correcting some typos --- source/Tutorials/understandingFilters.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/Tutorials/understandingFilters.rst b/source/Tutorials/understandingFilters.rst index aa592f4a..17eb86e0 100644 --- a/source/Tutorials/understandingFilters.rst +++ b/source/Tutorials/understandingFilters.rst @@ -24,8 +24,7 @@ modify it somehow (though this can include completely replacing it or leaving it unchanged), and return the result. That returned value is what's passed to any later functions attached to the same filter, and eventually back to the code that applied the filter in the first place. Since filters -work this way, there's aclear distinction from how hooks work in this case: -filter functions filter functions **must** return a value. +work this way, there's a clear distinction from how hooks work in this case: filter functions **must** return a value. The second parameter to a filter function is conventionally called ``$args``. Just like with hooks, ``$args`` is an array of arguments, optional useful