diff --git a/semantic-kernel/Frameworks/process/examples/example-cycles.md b/semantic-kernel/Frameworks/process/examples/example-cycles.md
index 78248e01..6d73ee18 100644
--- a/semantic-kernel/Frameworks/process/examples/example-cycles.md
+++ b/semantic-kernel/Frameworks/process/examples/example-cycles.md
@@ -145,7 +145,7 @@ class ProofreadStep(KernelProcessStep):
         else:
             await context.emit_event(
                 process_event="documentation_rejected",
-                data={"explanation": formatted_response.explanation, "suggestions": formatted_response.suggestions},
+                data="suggestions_text",
             )
 ```
 A new step named `ProofreadStep` has been created. This step uses the LLM to grade the generated documentation as discussed above. Notice that this step conditionally emits either the `documentation_approved` event or the `documentation_rejected` event based on the response from the LLM. In the case of `documentation_approved`, the event will include the approved documentation as it's payload and in the case of `documentation_rejected` it will include the suggestions from the proofreader.
@@ -496,4 +496,4 @@ For more support, explore our comprehensive FAQ section or contact our dedicated
 Our process is now reliably generating documentation that meets our defined standards. This is great, but before we publish our documentation publicly we really should require a human to review and approve. Let's do that next.
 
 > [!div class="nextstepaction"]
-> [Human-in-the-loop](./example-human-in-loop.md)
\ No newline at end of file
+> [Human-in-the-loop](./example-human-in-loop.md)