SME feedback

src/content/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing.mdx

@@ -103,7 +103,7 @@ The best way to minimize your risk is to ensure you fully understand the process
 
 To use distributed tracing with cross-origin resources, you populate a list of approved cross-origin resources in New Relic, and then we automatically send the following custom headers to those resources: `newrelic`, `traceparent`, and `tracestate`. For this process to work, you must first ensure that someone has configured the services on the other origins to accept this custom header.
 
-Cross-origin resource sharing uses a variety of HTTP headers (both in the request and response). The header that specifically applies to New Relic is the `Access-Control-Allow-Headers` response header, which needs to include `newrelic`, `traceparent`, and `tracestate` in its value. You must configure your server to return this CORS header in its response. Example:
+Cross-origin resource sharing uses a variety of HTTP headers (both in the request and response). The header that specifically applies to New Relic is the `Access-Control-Allow-Headers` response header, which can include `newrelic`, `traceparent, tracestate`, or `newrelic, traceparent, tracestate` in its value depending on what tracing strategies you enabled in your APM-monitored application. You must configure your server to return this CORS header in its response. Example:
 
 `Access-Control-Allow-Headers: newrelic, traceparent, tracestate`