diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-errors.md b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-errors.md
index 3f1cb8f76..fa8533928 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-errors.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/.generated/client-errors.md
@@ -136,16 +136,6 @@ Often when encountering this issue, the value in question shouldn't be state (fo
 Cannot use `fork(...)` unless the `experimental.async` compiler option is `true`
 ```
 
-### flush_sync_in_effect
-
-```
-Cannot use `flushSync` inside an effect
-```
-
-The `flushSync()` function can be used to flush any pending effects synchronously. It cannot be used if effects are currently being flushed — in other words, you can call it after a state change but _not_ inside an effect.
-
-This restriction only applies when using the `experimental.async` option, which will be active by default in Svelte 6.
-
 ### fork_discarded
 
 ```
diff --git a/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-errors.md b/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-errors.md
index ab24bf45e..a0b0e874d 100644
--- a/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-errors.md
+++ b/apps/svelte.dev/content/docs/svelte/98-reference/30-runtime-errors.md
@@ -143,16 +143,6 @@ Often when encountering this issue, the value in question shouldn't be state (fo
 Cannot use `fork(...)` unless the `experimental.async` compiler option is `true`
 ```
 
-### flush_sync_in_effect
-
-```
-Cannot use `flushSync` inside an effect
-```
-
-The `flushSync()` function can be used to flush any pending effects synchronously. It cannot be used if effects are currently being flushed — in other words, you can call it after a state change but _not_ inside an effect.
-
-This restriction only applies when using the `experimental.async` option, which will be active by default in Svelte 6.
-
 ### fork_discarded
 
 ```