Update content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-row-format.md

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>

Author: ilianiliev-redis

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-row-format.md

@@ -132,7 +132,7 @@ output:
     Please note that `key` should not be used in combination with `row_format: full` and more than one output, as the `key` object will be overwritten by the previous output. This is a known limitation of the current implementation and is subject to change in future versions.
 
 
-- The final result of the processing, that will be stored in the output, is the value of the `after` object, so you have to reference the fields using the `after` prefix unless you change the output structure in a transformation step. This also means that when adding new fields, you have to prefix them with `after.` to ensure that they are added to the correct part of the output. Example:
+- The final result of the processing (which is what will be stored in the output) is the value of the `after` object. This means you must reference the fields using the `after` prefix unless you change the output structure in a transformation step. Also, when you add new fields, you must prefix them with `after.` to ensure that they are added to the correct part of the output:
 
     ```yaml
     source: