More precise wording for the subscriptions RAM issue

	modified:   docs/sdk/reference/graphql-server/configuration/subscriptions.md
	modified:   docs/sdk/reference/graphql-server/overview.md

Author: abernatskiy

docs/sdk/reference/graphql-server/configuration/subscriptions.md

@@ -7,7 +7,7 @@ description: Subscribe to updates over a websocket
 # Subscriptions
 
 :::danger
-Implementation of subscriptions by the SQD GraphQL server [leaks memory under load](/sdk/reference/graphql-server/overview/#known-issues). Do not use it in scenarios where more than a few users simultaneously maintain connections to the server. This includes most production usage scenarios.
+RAM usage of subscriptions scales poorly under high load, making the feature unsuitable for most production uses. There are currently no plans to fix this issue.
 :::
 
 OpenReader supports [GraphQL subscriptions](https://www.apollographql.com/docs/react/data/subscriptions/) via live queries. To use these, a client opens a websocket connection to the server and sends a `subscription` query there. The query body is then repeatedly executed (every 5 seconds by default) and the results are sent to the client whenever they change.

docs/sdk/reference/graphql-server/overview.md

@@ -44,6 +44,6 @@ The OpenReader GraphQL API defines the following custom scalar types:
 
 ## Known issues
 
-- [Subscriptions](/sdk/reference/graphql-server/configuration/subscriptions) leak memory under load and are thus unsuitable for use in production.
+- RAM usage of [subscriptions](/sdk/reference/graphql-server/configuration/subscriptions) scales poorly under high load, making the feature unsuitable for most production uses. There are currently no plans to fix this issue.
 - Setting up custom resolvers for subscriptions is unreasonably hard.
 - `@subsquid/graphql-server` depends on the deprecated Apollo Server v3.