Update docs

Author: wol-soft

docs/source/nonStandardExtensions/filter.rst

@@ -360,6 +360,8 @@ Custom transforming filter
 
 If you want to provide a custom filter which transforms a value (eg. redirect data into a manually written model, transforming between data types [eg. accepting values as an integer but handle them internally as binary strings]) you must implement the **PHPModelGenerator\\PropertyProcessor\\Filter\\TransformingFilterInterface**. This interface adds the **getSerializer** method to your filter. The method is similar to the **getFilter** method. It must return a callable which is available during the render process as well as during code execution. The returned callable must return null or a string and undo a transformation (eg. the serializer method of the builtin **dateTime** filter transforms a DateTime object back into a formatted string). The serializer method will be called with the current value of the property as the first argument and with the (optionally provided) additional options of the filter as the second argument. Your custom transforming filter might look like:
 
+The custom serializer method will be called if the model utilizing the custom filter is generated with `serialization methods<../gettingStarted.html#serialization-methods>`__ and *toArray* or *toJSON* is called.
+
 .. code-block:: php
 
     namespace MyApp\Model\Generator\Filter;
@@ -378,7 +380,7 @@ If you want to provide a custom filter which transforms a value (eg. redirect da
 
         // $customer will contain the current value of the property the filter is applied to
         // $additionalOptions will contain all additional options from the JSON Schema
-        public static function instantiateCustomer(?Customer $customer, array $additionalOptions): ?string
+        public static function serializeCustomer(?Customer $customer, array $additionalOptions): ?string
         {
             return $data !== null ? $customer->serialize($additionalOptions) : null;
         }