fix: Add connecting services to node + express (#3418)

- Also Adding a line about how exceeding the span limit can result in
  broken subtraces

Co-authored-by: Fiona <[email protected]>

Author: wmak

src/docs/product/performance/trace-view.mdx

@@ -41,6 +41,7 @@ Broken subtraces may be caused by:
 - [Ad blockers](/platforms/javascript/troubleshooting/#dealing-with-ad-blockers) may prevent transactions in browsers being sent, but HTTP requests to backend projects will still create child transactions
 - [Rate-limiting](/product/accounts/quotas/#limiting-events) on a project may cause only some events to be sent to Sentry
 - [Project permissions](/product/accounts/membership/#restricting-access) may mean you do not have access to transactions in another project
+- Exceeding the span limit. Transactions are associated via the child spans of the parent transaction, but if the number of spans exceed the limit, the association cannot be made
 
 ### Multiple Roots
 

src/platforms/common/performance/index.mdx

@@ -91,11 +91,11 @@ Leaving the sample rate at `1.0` means that included instrumentation will send a
 
 ## Connecting Services
 
-If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/) depending on where your request originates there are two methods to connect your traces:
-1. For requests that start in your backend, this is done by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
-2. For requests that start in JavaScript, this is done by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
+If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
+1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
+2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
 
-Otherwise backend services with Performance Monitoring will connect automatically.
+Otherwise, backend services with Performance Monitoring connect automatically.
 
 </PlatformSection>
 

src/platforms/node/common/performance/index.mdx

@@ -99,3 +99,11 @@ app.get("/success", function successHandler(req, res) {
   res.status(200).end();
 });
 ```
+
+## Connecting Services
+
+If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
+1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
+2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
+
+Otherwise, backend services with Performance Monitoring connect automatically.

src/platforms/node/guides/express/performance/index.mdx

@@ -100,3 +100,11 @@ app.get("/success", function successHandler(req, res) {
   res.status(200).end();
 });
 ```
+
+## Connecting Services
+
+If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
+1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
+2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
+
+Otherwise, backend services with Performance Monitoring connect automatically.

src/platforms/php/common/performance.mdx

@@ -116,11 +116,11 @@ After you set up Relay, you should see a dramatic improvement to the impact on y
 
 <PlatformSection notSupported={["php.laravel"]}>
 
-If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/) depending on where your request originates there are two methods to connect your traces:
-1. For requests that start in your backend, this is done by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
-2. For requests that start in JavaScript, this is done by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
+If you are also using Performance Monitoring for [JavaScript](/platforms/javascript/performance/), depending on where your request originates, you can connect traces:
+1. For requests that start in your backend, by [adding a meta tag](/platforms/javascript/performance/connect-services/#pageload) in your HTML template that contains tracing information.
+2. For requests that start in JavaScript, by the SDK [setting a header](/platforms/javascript/performance/connect-services/#navigation-and-other-xhr-requests) on requests to your backend.
 
-Otherwise backend services with Performance Monitoring will connect automatically.
+Otherwise, backend services with Performance Monitoring connect automatically.
 
 </PlatformSection>