Merge pull request #16285 from newrelic/akristen-patch-4

Update vague language in otel doc

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/get-started/opentelemetry-set-up-your-app.mdx

@@ -52,10 +52,9 @@ Go to the repository for your language and follow the instructions to instrument
   <Step>
 ## Review configurations for exporting telemetry data to New Relic [#review-settings]
 
-Before you set up the export of your telemetry data, you first need to review and bookmark this section of settings for New Relic. You'll need this information when you later go to other pages explaining the export steps.
-
-The export relies on the [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md), or OTLP for short, which 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.
+Exporting telemetry data relies on the [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md), or OTLP for short. This 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.
 
+Before you can export your telemetry data, you need to have your ingest license key and the appropriate OTLP endpoint. We recommend pasting this information in a text file, as you’ll need both in the following steps.
 You have two choices for exporting data to New Relic via OTLP:
 
 * Directly from your app: