Address feedback

Author: natasha-moore-elastic

troubleshoot/observability/apm/apm-server-response-codes.md

@@ -12,17 +12,47 @@ applies_to:
 
 ## HTTP 400: Data decoding error / Data validation error [apm-bad-request] 
 
-The most likely cause for this error is using incompatible versions of {{apm-agent}} and APM Server. See the [agent/server compatibility matrix](../../../solutions/observability/apps/apm-agent-compatibility.md) to verify compatibility.
+::::{tab-set}
+
+:::{tab-item} {{stack}}
+The most likely cause for this error is using incompatible versions of {{apm-agent}} and APM Server. See the [agent/server compatibility matrix](/solutions/observability/apps/apm-agent-compatibility.md) to verify compatibility.
+:::
+
+:::{tab-item} {{serverless-short}}
+The most likely cause for this error is using an incompatible version of an {{apm-agent}}. See [minimum supported APM agent versions](/solutions/observability/apps/elastic-apm-agents.md#observability-apm-agents-elastic-apm-agents-minimum-supported-versions) to verify compatibility.
+:::
+
+::::
 
 
 ## HTTP 400: Event too large [apm-event-too-large] 
 
-APM agents communicate with the APM server by sending events in an HTTP request. Each event is sent as its own line in the HTTP request body. If events are too large, you should consider increasing the [Max event size](../../../solutions/observability/apps/general-configuration-options.md#apm-max_event_size) setting in the APM integration, and adjusting relevant settings in the agent.
+::::{tab-set}
+
+:::{tab-item} {{stack}}
+APM agents communicate with the APM server by sending events in an HTTP request. Each event is sent as its own line in the HTTP request body. If events are too large, you should consider increasing the [Max event size](/solutions/observability/apps/general-configuration-options.md#apm-max_event_size) setting in the APM integration, and adjusting relevant settings in the agent.
+:::
+
+:::{tab-item} {{serverless-short}}
+APM agents communicate with the Managed intake service by sending events in an HTTP request. Each event is sent as its own line in the HTTP request body. If events are too large, you can reduce the size of the events that your APM agents send by: [enabling span compression](/solutions/observability/apps/spans.md) or [reducing collected stack trace information](/solutions/observability/apps/reduce-storage.md#observability-apm-reduce-stacktrace).
+:::
+
+::::
 
 
 ## HTTP 401: Invalid token [apm-unauthorized] 
 
-Either the [Secret token](../../../solutions/observability/apps/secret-token.md) in the request header doesn’t match the secret token configured in the APM integration, or the [API keys](../../../solutions/observability/apps/api-keys.md) is invalid.
+::::{tab-set}
+
+:::{tab-item} {{stack}}
+Either the [Secret token](/solutions/observability/apps/secret-token.md) in the request header doesn’t match the secret token configured in the APM integration, or the [API keys](/solutions/observability/apps/api-keys.md) is invalid.
+:::
+
+:::{tab-item} {{serverless-short}}
+The API key is invalid.
+:::
+
+::::
 
 
 ## HTTP 403: Forbidden request [apm-forbidden] 

troubleshoot/observability/apm/common-problems.md

@@ -294,24 +294,3 @@ To fix this, make sure these two fields match exactly.
 
 For example, if the APM agent is not configured to use the correct host name, the host name might be set to the container name or the Kubernetes pod name. To get the correct host name, you need to set some additional configuration options, specifically `system.kubernetes.node.name` as described in [Kubernetes data](../../../solutions/observability/apps/elastic-apm-events-intake-api.md#apm-api-kubernetes-data).
 
-
-## Common response codes [observability-apm-troubleshooting-common-response-codes]
-```yaml {applies_to}
-serverless: all
-```
-
-
-### HTTP 400: Data decoding error / Data validation error [bad-request]
-
-The most likely cause for this error is using an incompatible version of an {{apm-agent}}. See [minimum supported APM agent versions](../../../solutions/observability/apps/elastic-apm-agents.md#observability-apm-agents-elastic-apm-agents-minimum-supported-versions) to verify compatibility.
-
-
-### HTTP 400: Event too large [event-too-large]
-
-APM agents communicate with the Managed intake service by sending events in an HTTP request. Each event is sent as its own line in the HTTP request body. If events are too large, you can reduce the size of the events that your APM agents send by: [enabling span compression](../../../solutions/observability/apps/spans.md) or [reducing collected stack trace information](../../../solutions/observability/apps/reduce-storage.md#observability-apm-reduce-stacktrace).
-
-
-### HTTP 401: Invalid token [unauthorized]
-
-The API key is invalid.
-