From 966348800bc37c4177a8876a906f0afbf855dff9 Mon Sep 17 00:00:00 2001
From: Sergei Maertens <sergei@maykinmedia.nl>
Date: Thu, 24 Oct 2024 10:48:24 +0200
Subject: [PATCH] :pencil: Update developer docs about mocking in stories

---
 src/developer-docs.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/developer-docs.mdx b/src/developer-docs.mdx
index a8740043d..e31081f6d 100644
--- a/src/developer-docs.mdx
+++ b/src/developer-docs.mdx
@@ -192,7 +192,7 @@ There are some known limitations related to mocking, with possible workarounds d
 
 There is no dedicated add-on panel to manage mock responses. Instead, you can rely on story args to
 dynamically change response data. To achieve this, you need to configure the worker as part of the
-story template, for example:
+story render function, for example:
 
 ```jsx
 import {getWorker} from 'msw-storybook-addon';
@@ -201,9 +201,9 @@ import {myMockFactory} from './mocks';
 
 export const worker = getWorker();
 
-export const Template = args => {
-  worker.use(myMockFactory(args.someArg));
-  return <MyComponent />;
+const render = ({someMockArg, ...args}) => {
+  worker.use(myMockFactory(someMockArg));
+  return <MyComponent {...args} />;
 };
 ```