diff --git a/docs/platforms/javascript/common/configuration/async-context.mdx b/docs/platforms/javascript/common/configuration/async-context.mdx
index 6ac68d46b8cebf..0fec8b51bcdc76 100644
--- a/docs/platforms/javascript/common/configuration/async-context.mdx
+++ b/docs/platforms/javascript/common/configuration/async-context.mdx
@@ -2,19 +2,8 @@
 title: Async Context
 sidebar_order: 80
 description: "Learn more about how to isolate Sentry scope and breadcrumbs across requests."
-supported:
-  - javascript.node
-  - javascript.eve
-  - javascript.mastra
-  - javascript.aws-lambda
-  - javascript.azure-functions
-  - javascript.express
-  - javascript.fastify
-  - javascript.gcp-functions
-  - javascript.hapi
-  - javascript.hono
-  - javascript.koa
-  - javascript.nestjs
+supportedCategories:
+  - server
 ---
 
 By default, the Sentry SDK will automatically isolate each request's scope and breadcrumbs. This means that any breadcrumbs or tags added will be isolated to the request. This is useful if you are finding that breadcrumbs and scope are leaking across requests. Take the following example: