document other places

pages/docs/reference/events/send.mdx

@@ -59,6 +59,8 @@ To send events from within of the context of a function, use [`step.sendEvent()`
 
 	    If the `ts` time is in the future, function runs will be scheduled to start at the given time.   This has the same effect as running `await step.sleepUntil(event.ts)` at
 	    the start of the function.
+
+            Note: This does not apply to functions waiting for events. Functions waiting for events will immediately resume, regardless of the timestamp.
           </Property>
           <Property name="v" type="string">
             A version identifier for a particular event payload. e.g. `"2023-04-14.1"`

pages/docs/reference/python/client/send.mdx

@@ -54,6 +54,8 @@ Only for async/await code.
             A timestamp integer representing the time (in milliseconds) at which the event occurred. Defaults to the time the Inngest receives the event.
 
             If the `ts` time is in the future, function runs will be scheduled to start at the given time. This has the same effect as sleeping at the start of the function.
+
+            Note: This does not apply to functions waiting for events. Functions waiting for events will immediately resume, regardless of the timestamp.
         </Property>
     </Properties>
     </Property>

pages/docs/reference/python/steps/send-event.mdx

@@ -32,6 +32,8 @@ Sends 1 or more events to the Inngest server. Returns a list of the event IDs.
                 A timestamp integer representing the time (in milliseconds) at which the event occurred. Defaults to the time the Inngest receives the event.
 
                 If the `ts` time is in the future, function runs will be scheduled to start at the given time. This has the same effect as sleeping at the start of the function.
+
+                Note: This does not apply to functions waiting for events. Functions waiting for events will immediately resume, regardless of the timestamp.
             </Property>
         </Properties>
     </Property>