Update image links, remove unused images

docs/sources/tempo/getting-started/metrics-from-traces.md

@@ -28,15 +28,15 @@ Span metrics are of particular interest if your system is not monitored with met
 Metrics generation is disabled by default. Contact Grafana Support to enable metrics generation in your organization.
 {{% /admonition %}}
 
-After the metrics generator is enabled in your organization, refer to [Metrics-generator configuration]({{< relref "../configuration" >}}) for information about metrics-generator options.
+After the metrics-generator is enabled in your organization, refer to [Metrics-generator configuration]({{< relref "../configuration" >}}) for information about metrics-generator options.
 
-<p align="center"><img src="../assets/trace_service_graph.png" alt="Trace service graph"></p>
+![Trace service graph](/media/docs/grafana/data-sources/tempo/query-editor/tempo-ds-query-service-graph.png)
 
 These metrics exist in your Hosted Metrics instance and can also be easily used to generate powerful custom dashboards.
 
 <p align="center"><img src="../assets/trace_custom_metrics_dash.png" alt="Trace custom metrics dashboard"></p>
 
-The metrics generator automatically generates exemplars as well which allows easy metrics to trace linking. [Exemplars](/docs/grafana-cloud/monitor-infrastructure/traces/exemplars/) are available in Grafana Cloud so you can also push your own.
+The metrics-generator automatically generates exemplars as well which allows easy metrics to trace linking. [Exemplars](https://grafana.com/docs/grafana/latest/fundamentals/exemplars/) are available in Grafana Cloud so you can also push your own.
 
 <p align="center"><img src="../assets/trace_exemplars.png" alt="Trace exemplars"></p>
 

docs/sources/tempo/metrics-generator/_index.md

@@ -29,7 +29,7 @@ Every processor derives different metrics. Currently, the following processors a
 - Span metrics
 - Local blocks
 
-<p align="center"><img src="server-side-metrics-arch-overview.png" alt="Service metrics architecture"></p>
+<p align="center"><img src="tempo-metrics-gen-overview.svg" alt="Service metrics architecture"></p>
 
 ## Service graphs
 
@@ -39,17 +39,17 @@ This service graphs processor builds a map of services by analyzing traces, with
 Edges are spans with a parent-child relationship, that represent a jump (e.g. a request) between two services.
 The amount of request and their duration are recorded as metrics, which are used to represent the graph.
 
-To learn more about this processor, read the [documentation]({{< relref "./service_graphs" >}}).
+To learn more about this processor, refer to [service graph]({{< relref "./service_graphs" >}}) documentation.
 
 ## Span metrics
 
-The span metrics processor derives RED (Request, Error and Duration) metrics from spans.
+The span metrics processor derives RED (Request, Error, and Duration) metrics from spans.
 
-The span metrics processor will compute the total count and the duration of spans for every unique combination of dimensions.
+The span metrics processor computes the total count and the duration of spans for every unique combination of dimensions.
 Dimensions can be the service name, the operation, the span kind, the status code and any tag or attribute present in the span.
 The more dimensions are enabled, the higher the cardinality of the generated metrics.
 
-To learn more about this processor, read the [documentation]({{< relref "./span_metrics" >}}).
+To learn more about this processor, refer to the[span metrics]({{< relref "./span_metrics" >}}).
 
 ## Local blocks
 

docs/sources/tempo/traceql/query-editor/_index.md

@@ -13,7 +13,7 @@ keywords:
   - TraceQL
 ---
 
-# Query tracing data
+# Write TraceQL queries in Grafana
 
 The Tempo data source's query editor helps you query and display traces from Tempo in [Explore](https://grafana.com/docs/grafana/<GRAFANA_VERSION>/explore/).
 The queries use [TraceQL](/docs/tempo/latest/traceql), the query language designed specifically for tracing.