feat(OTEL): Added a table from the beta doc with NR settings.

src/content/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-quick-start.mdx

@@ -48,7 +48,7 @@ Go to the repository for your language and follow the instructions to instrument
 
 The [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md), or OTLP for short, is a general purpose telemetry data delivery protocol designed for the OpenTelemetry project. This protocol describes how to encode and transmit telemetry data, which makes it a natural choice for data transport. Each language SDK provides an OTLP exporter you can configure to export data over OTLP. 
 
-In this step, we focus on how to configure an OTLP exporter in your service to export data directly to New Relic:
+In this step, we focus on how to configure an OTLP exporter in your service to export data directly to New Relic. If you prefer to export your data first to an OpenTelemetry collector, we have separate [instructions](#collector). 
 
 ![Diagram showing OpenTelemetry using New Relic's OTLP endpoint.](./images/native_otlp.svg "Diagram of OTLP endpoint")
 <figcaption>Here's an example of sending data from your service directly to New Relic.</figcaption>
@@ -109,58 +109,7 @@ Before you go to the external OTLP exporter documentation, consult the table bel
 In Node.js, the [opentelemetry-collector-grpc](https://www.npmjs.com/package/@opentelemetry/exporter-collector-grpc) library requires additional options to enable TLS.
 </Callout>
 
-To complete this step, you'll follow the OTLP exporter documenentation for your language. Before you go to this external documentation, keep in mind you'll need to configure the OTLP exporter to send data to New Relic: 
-
-* Configure the OTLP exporter to add a header ( ```api-key``` ) whose value is your [Account License Key](https://one.newrelic.com/launcher/api-keys-ui.launcher).
-* Configure the endpoint for the exporter to point to New Relic.  
-
-<table>
-  <thead>
-    <tr>
-      <th>Region</th>
-      <th>gRPC</th>
-      <th>HTTP</th>
-      <th>Endpoint</th>
-      <th>API Header Name</th>
-      <th>API Header Value</th>
-      <th>TLS encryption required</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>US</td>
-      <td>✅</td>
-      <td>❌</td>
-      <td><a href="https://otlp.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://otlp.nr-data.net:4317</a></td>
-      <td><code>api-key</code></td>
-      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
-      <td>✅</td>
-    </tr>
-    <tr>
-      <td>EU</td>
-      <td>✅</td>
-      <td>❌</td>
-      <td><a href="https://otlp.eu01.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://otlp.eu01.nr-data.net:4317</a></td>
-      <td><code>api-key</code></td>
-      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
-      <td>✅</td>
-    </tr>
-        <tr>
-      <td>FedRamp</td>
-      <td>✅</td>
-      <td>❌</td>
-      <td><a href="https://gov-otlp.nr-data.net:4317" target="_blank" rel="noopener noreferrer">https://gov-otlp.nr-data.net:4317</a></td>
-      <td><code>api-key</code></td>
-      <td><a href="https://one.newrelic.com/launcher/api-keys-ui.launcher" target="_blank" rel="noopener noreferrer">License Key</a></td>
-      <td>✅</td>
-    </tr>
-  </tbody>
-</table>
-
-<Callout variant="important">
-In NodeJS, the [opentelemetry-collector-grpc](https://www.npmjs.com/package/@opentelemetry/exporter-collector-grpc) library requires additional options to enable TLS.
-</Callout>
-
+### Complete the export configuration steps
 
 Click on the link below for your language and complete the configuration steps. When you're done, return here to complete [Step 4. View your data in the New Relic UI](#view-data).