made suggested changes

Author: altafDevRev

fern/docs/pages/references/functions.mdx

@@ -29,9 +29,15 @@ functions:
 
 ### Synchronous execution with synchronization key
 
-To ensure that function executions are processed in order, FIFO, for a given context such as a user or conversation, enable synchronization support in your function’s manifest and use a synchronization key, sync-id.
+To ensure that function executions are processed in order, FIFO, for a given context such as a user or conversation, enable synchronization support in your function’s manifest and use a synchronization key, sync_id.
 
-#### How it works
+The platform uses the sync_id as the message group for FIFO processing. This ensures that all executions with the same sync_id are processed in order, preventing race conditions or duplicate conversations.
+Use cases for synchronous execution include:
+
+- Ensuring order of message processing for chatbots or messaging integrations.
+- Preventing duplicate or out-of-order actions when multiple events are triggered.
+
+To enable this: 
 
 1. Enable synchronization in manifest
    - In your function’s manifest, add the field:
@@ -44,8 +50,8 @@ To ensure that function executions are processed in order, FIFO, for a given con
    - This tells the platform to use a FIFO queue for this function.
 
 1. Set the synchronization key
-   - When triggering an automation, include the sync-id in your rego policy along with the `event_key`. For example:
-     ```rego focus
+   - When triggering an automation, include the sync_id in your rego policy along with the `event_key`. For example:
+     ```rego rego
      package rego
 
      output = {"event": event, "event_key": event_key, "sync_id": sync_id} {
@@ -60,24 +66,12 @@ To ensure that function executions are processed in order, FIFO, for a given con
      }
      ```
 
-   - The sync-id groups related executions for ordered processing.
-
+   - The sync_id groups related executions for ordered processing.
 
 3. Execution behavior
-   - If `supports_synchronization` is true and a sync-id is provided, executions with the same sync-id are processed in order.
-   - If no sync-id is provided, executions are grouped by a random string.
-   - If `supports_synchronization` is false, the sync-id is ignored and executions are processed as usual.
-
-#### Platform behavior
-
-- The platform uses the sync-id as the message group for FIFO processing.
-- This ensures that all executions with the same sync-id are processed in order, preventing race conditions or duplicate conversations.
-
-#### Use cases
-
-- Ensuring order of message processing for chatbots or messaging integrations.
-- Preventing duplicate or out-of-order actions when multiple events are triggered.
-
+   - If `supports_synchronization` is true and a sync_id is provided, executions with the same sync_id are processed in order.
+   - If no sync_id is provided, executions are grouped by a random string.
+   - If `supports_synchronization` is false, the sync_id is ignored and executions are processed as usual.
 
 
 <Callout intent="note">