From 8519761afd342ac50db3e6566b8059e75b0bde4c Mon Sep 17 00:00:00 2001
From: Hyunbin Seo <47051820+hyunbinseo@users.noreply.github.com>
Date: Sat, 23 May 2026 23:50:32 +0900
Subject: [PATCH] docs: remove await on server side query.set

---
 documentation/docs/20-core-concepts/60-remote-functions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/docs/20-core-concepts/60-remote-functions.md b/documentation/docs/20-core-concepts/60-remote-functions.md
index 496251a314fd..7a1ac71b6bce 100644
--- a/documentation/docs/20-core-concepts/60-remote-functions.md
+++ b/documentation/docs/20-core-concepts/60-remote-functions.md
@@ -1013,7 +1013,7 @@ export const updatePost = form(
 );
 ```
 
-Because queries are keyed based on their arguments, `await getPost(post.id).set(result)` on the server knows to look up the matching `getPost(id)` on the client to update it. The same goes for `getPosts().refresh()` -- it knows to look up `getPosts()` with no argument on the client.
+Because queries are keyed based on their arguments, `getPost(post.id).set(result)` on the server knows to look up the matching `getPost(id)` on the client to update it. The same goes for `getPosts().refresh()` -- it knows to look up `getPosts()` with no argument on the client.
 
 ### Reconnecting live queries in mutations