From 8ac5531913e547238c4e75c6786a525937a50610 Mon Sep 17 00:00:00 2001 From: Soichiro Miki Date: Tue, 17 Dec 2024 01:11:21 +0900 Subject: [PATCH] Rename remaining "Server Actions" (#7352) --- src/content/reference/react/useTransition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/reference/react/useTransition.md b/src/content/reference/react/useTransition.md index 537dd6f85..f4781295c 100644 --- a/src/content/reference/react/useTransition.md +++ b/src/content/reference/react/useTransition.md @@ -310,7 +310,7 @@ This is a basic example to demonstrate how Actions work, but this example does n For common use cases, React provides built-in abstractions such as: - [`useActionState`](/reference/react/useActionState) - [`
` actions](/reference/react-dom/components/form) -- [Server Actions](/reference/rsc/server-actions) +- [Server Functions](/reference/rsc/server-functions) These solutions handle request ordering for you. When using Transitions to build your own custom hooks or libraries that manage async state transitions, you have greater control over the request ordering, but you must handle it yourself.