(/integrations/webhooks/sync-data) update guide

docs/integrations/webhooks/sync-data.mdx

@@ -53,8 +53,6 @@ These steps apply to any Clerk event. To make the setup process easier, it's rec
 
   ### Set up a webhook endpoint
 
-  To set up a webhook endpoint, you must provide the **Endpoint URL** and choose the events you want to listen to. For this guide, select the `user.created` event.
-
   1. In the Clerk Dashboard, navigate to the [**Webhooks**](https://dashboard.clerk.com/last-active?path=webhooks) page.
   1. Select **Add Endpoint**.
   1. In the **Endpoint URL** field, paste the ngrok **Forwarding** URL you saved earlier, followed by `/api/webhooks`. This is the endpoint that Svix uses to send the webhook payload. The full URL should resemble `https://fawn-two-nominally.ngrok-free.app/api/webhooks`.
@@ -78,27 +76,13 @@ These steps apply to any Clerk event. To make the setup process easier, it's rec
 
   Incoming webhook events have no auth information. They come from an external source and will not be signed in or signed out. To allow access, the route must be public.
 
-  The following example shows the recommended Middleware configuration for webhook routes.
-
-  ```ts {{ filename: 'middleware.ts' }}
-  import { clerkMiddleware } from '@clerk/nextjs/server'
-
-  // Make sure that the `/api/webhooks(.*)` route is not protected here
-  export default clerkMiddleware()
+  Incoming webhook events contain no authentication information. They come from an external source and won't be signed in or signed out, so the route must be public to allow access.
 
-  export const config = {
-    matcher: [
-      // Skip Next.js internals and all static files, unless found in search params
-      '/((?!_next|[^?]*\\.(?:html?|css|js(?!on)|jpe?g|webp|png|gif|svg|ttf|woff2?|ico|csv|docx?|xlsx?|zip|webmanifest)).*)',
-      // Always run for API routes
-      '/(api|trpc)(.*)',
-    ],
-  }
-  ```
+  To configure your Middleware, refer to the [clerkMiddleware() guide](docs/references/nextjs/clerk-middleware).
 
   ### Install `svix`
 
-  You'll use [`svix`](https://www.npmjs.com/package/svix) to verify the webhook signature. Run the following command in your terminal to install it:
+  Clerk uses [`svix`](https://www.npmjs.com/package/svix) to deliver webhooks, so you'll need the package to verify the webhook signature. Run the following command in your terminal to install it:
 
   <CodeBlockTabs type="installer" options={["npm", "yarn", "pnpm"]}>
     ```bash {{ filename: 'terminal' }}
@@ -116,11 +100,13 @@ These steps apply to any Clerk event. To make the setup process easier, it's rec
 
   ### Create the endpoint
 
-  Set up a Route Handler that uses `svix` to verify the webhook and process the payload.
+  Set up a Route Handler that uses `svix` to verify the incoming Clerk webhook and process the payload.
 
   For this guide, the payload will be logged to the console. In a real app, you'd use the payload to trigger an action. For example, if listening for the `user.created` event, you might perform a database `create` or `upsert` to add the user's details to the user's table.
 
-  The webhook must return either an [error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#client_error_responses) such as `405` or `403` or a [success code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#successful_responses), such as `200` or `201`. An error code will appear in the Clerk Dashboard log and trigger a [retry](/docs/integrations/webhooks/overview#retry). A success code will stop further retries and show a success status in the Clerk Dashboard log.
+  If the route handler returns a [2xx code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#successful_responses), the event will be marked as successful, and retries will stop. If the route handler returns a [4xx](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#client_error_responses) or [5xx code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#server_error_responses), or no code at all, the webhook event will be [retried](/docs/integrations/webhooks/overview#retry).
+
+  In summary, a 2xx (success) code stops retries, while any other response is considered a failure and will trigger retries.
 
   > [!NOTE]
   > The following Route Handler can be used for any webhook event you choose to listen to, not just `user.created`.