Correcting language for trace prop example

Author: codyde

platform-includes/distributed-tracing/how-to-use/javascript.astro.mdx

@@ -4,9 +4,9 @@ When you are interacting with other external API systems, you might have to defi
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.mdx

@@ -4,9 +4,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx

@@ -4,9 +4,9 @@ For client-side, when you are interacting with other external API systems, you m
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.node.mdx

@@ -10,9 +10,9 @@ Sentry.init({
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.nuxt.mdx

@@ -4,9 +4,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx

@@ -35,9 +35,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx

@@ -29,9 +29,9 @@ To get around possible [Browser CORS](https://developer.mozilla.org/en-US/docs/W
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>
 

platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx

@@ -4,9 +4,9 @@ When you are interacting with other external API systems, you might have to defi
 
 <Alert>
 
-When testing locally, you may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your local services if they have different port numbers. 
+Note: port numbers are relevant for trace propagation and the origin. You may need to configure the `tracePropagationTargets` to ensure that traces are propagated across your services if they run on different ports. 
 
-For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, you'll need to add `http://localhost:5173` and `http://localhost:3000` to the `tracePropagationTargets` array.
+For example, if you have a Vite frontend running on `http://localhost:5173` and a Bun backend running on `http://localhost:3000`, both `http://localhost:5173` and `http://localhost:3000` should be added to the `tracePropagationTargets` array.
 
 </Alert>