update with configuration diagrams (#1300)

tiny tweaks for clarity

Author: MariadeAnton

site/assets/docs/images/otel/checkly-traces-instrument-app-diagram.png

@@ -12,13 +12,14 @@ aliases:
 ---
 
 
-> Checkly Traces are OpenTelemetry native and available on all plans. 
+> Checkly Traces are OpenTelemetry native and available on all plans.
 > Need help getting started? We offer a **free, 1:1 onboarding service** to help you instrument your stack with the 
 > correct OpenTelemetry SDKs and enable tracing inside Checkly. 
 > [Book an onboarding session right here](https://calendly.com/maria-checkly/traces-onboarding).
 
-With Traces configured, you will have access to traces in all the places where it matters to more quickly resolve issues:
-- **Check results:** resolve production outages faster by correlating failing checks with backend traces.
+With telemetry traces configured, you will have access to traces in all the places where it matters to more quickly resolve issues:
+
+- **Check results:** resolve production outages faster by correlating failing checks with infrastructure traces.
 - **Test sessions:** understand any failures during test session execution.
 - **Check editors:** get a live trace while building, editing and debugging check code.
 
@@ -40,8 +41,8 @@ To get started with Checkly Traces using OpenTelemetry, pick the scenario that b
 {{< doc-card
 	  class="three-column-card"
 	  headerTag="h3"
-	  title="I want to see traces in Checkly"
-	  description="Send your backend traces to Checkly to get contextualized check failure analysis."
+	  title="I already have an OTEL Collector"
+	  description="Send your infrastructure traces to Checkly to get contextualized check failure analysis."
 	  img="/docs/images/icons/opentelemetry.svg"
 	  link="/docs/traces-open-telemetry/importing-traces/"
 >}}

site/assets/docs/images/otel/checkly-traces-otel-collector-diagram.png

@@ -8,7 +8,9 @@ menu:
     parent: "Traces"
 ---
 
-Send your 3rd party backend OpenTelemetry traces to Checkly. Inspect and drill down to why a check failed or degraded.
+Send your infrastructure OpenTelemetry traces to Checkly. Inspect and drill down to why a check failed or degraded.
+
+![OTEL Collector Diagram with Checkly Traces](/docs/images/otel/checkly-traces-otel-collector-diagram.png)
 
 <!--more-->
 

site/assets/docs/images/otel/otel_basic_instrumentation.png

@@ -11,10 +11,14 @@ aliases:
   - "/docs/open-telemetry/instrumenting-code/"
 ---
 
-If you are completely new to OpenTelemetry, you should start by instrumenting your web facing application code with the 
-relevant OTel libraries. This will allow you to send traces directly to Checkly without setting up a 3rd party [OpenTelemetry collector](/learn/opentelemetry/what-is-the-otel-collector/).
+Use OpenTelemetry SDKs and libraries to instrument your applications and services. Send traces directly to Checkly without setting up an [OpenTelemetry collector](/learn/opentelemetry/what-is-the-otel-collector/).
+
+If you are new to OpenTelemetry, start by instrumenting your web facing application code with the relevant OpenTelemetry SDKs and libraries.
+
+![OTEL App Diagram with Checkly Traces](/docs/images/otel/checkly-traces-instrument-app-diagram.png)
+
 <!--more-->
-Below you will find instructions on how to instrument your popular languages and frameworks, and how to send traces to Checkly.
+Below you will find instructions on how to instrument your code, and how to send traces to Checkly. Select your coding language / framework to begin:
 
 ## Languages
 
@@ -93,5 +97,4 @@ Below you will find instructions on how to instrument your popular languages and
 </div>
 <br>
 
-If you don't find the language or framework you are using in the list above, you can always reference the
-[OpenTelemetry Languages docs](https://opentelemetry.io/docs/languages/) directly.
+> If you don't find the language or framework you are using in the list above, you can find all languages and frameworks there's OpenTelemetry support in the [OpenTelemetry Instrumentation docs](https://opentelemetry.io/docs/languages/).