Rename org config to orgId

Author: cleptric

develop-docs/sdk/telemetry/traces/index.mdx

@@ -78,9 +78,9 @@ This must be a boolean value. Default is `false`. This option controls trace con
 
 If the SDK is able parse an org ID from the configured DSN, it must be propagated as a baggage entry with the key `sentry-org`. Given a DSN of `https://[email protected]/1`, the org ID is `1`, based on `o1`.
 
-Addiotnally, the SDK must be configurable with an optional `org: <org-id>` setting that takes precedence over the parsed value from the DSN. This option should be set when running a self-hosted version of Sentry or if a non-standard Sentry DSN is used, such as when using a local Relay.
+Addiotnally, the SDK must be configurable with an optional `orgId: <org-id>` setting that takes precedence over the parsed value from the DSN. This option should be set when running a self-hosted version of Sentry or if a non-standard Sentry DSN is used, such as when using a local Relay.
 
-On incoming traces, the SDK must compare the `sentry-org` baggage value against its own parsed value from the DSN or org setting. Only if both match, the trace is continued. If there is no match, neither the trace ID, the parent sampling decision nor the baggage should be taken into account.
+On incoming traces, the SDK must compare the `sentry-org_id` baggage value against its own parsed value from the DSN or org setting. Only if both match, the trace is continued. If there is no match, neither the trace ID, the parent sampling decision nor the baggage should be taken into account.
 The SDK should behave like it is the head of trace in this case, and not consider any propagted values.
 
 This behavior can be disabled by setting `strictTraceContinuation: false` in the SDK init call.