Clarify message truncation (#13068)

Author: cleptric

develop-docs/sdk/data-model/event-payloads/index.mdx

@@ -304,12 +304,7 @@ Fingerprints](https://docs.sentry.io/data-management/event-grouping/).
 ## Size Limits
 
 Event ingestion imposes limits on the size of events.
-These limits are subject to future change and defined currently as:
-
-- *1MB* decompressed (and `200KB` compressed) for events of type `error`
-- *1MB* decompressed (and `200KB` compressed) for events of type `transaction`
-
-Sessions, client reports, replays, check-ins, and profiles are not events and have different size limits. See [Envelope Size Limits](/sdk/data-model/envelopes/#size-limits).
+See [Envelope Size Limits](/sdk/data-model/envelopes/#size-limits) for futher details.
 
 ## Core Interfaces
 

develop-docs/sdk/data-model/event-payloads/message.mdx

@@ -14,14 +14,16 @@ help to group similar messages into the same issue.
 : **Required**. The fully formatted message. If missing, Sentry will try to
   interpolate the message.
 
-  It must not exceed 8192 characters. Longer messages will be truncated. Sentry
-  also accepts a message where this is not set to support legacy SDKs.
+  A limit of 8192 characters is exposed in Relay and longer messages will be truncated. 
+  SDKs should not enforce this limit.
+  Sentry also accepts a message where this is not set to support legacy SDKs.
 
 `message`
 
 : _Optional_. The raw message string (uninterpolated).
 
-  It must not exceed 8192 characters. Longer messages will be truncated.
+  A limit of 8192 characters is exposed in Relay and longer messages will be truncated.
+  SDKs should not enforce this limit.
 
 `params`