Alphabetize by title (#6608)

* Alphabetize by title

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

* Alphabetize by title

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

---------

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

_data-prepper/common-use-cases/anomaly-detection.md

@@ -2,7 +2,7 @@
 layout: default
 title: Anomaly detection
 parent: Common use cases
-nav_order: 30
+nav_order: 5
 ---
 
 # Anomaly detection

_data-prepper/common-use-cases/codec-processor-combinations.md

@@ -2,7 +2,7 @@
 layout: default
 title: Codec processor combinations
 parent: Common use cases
-nav_order: 25
+nav_order: 10
 ---
 
 # Codec processor combinations

_data-prepper/common-use-cases/event-aggregation.md

@@ -2,7 +2,7 @@
 layout: default
 title: Event aggregation
 parent: Common use cases
-nav_order: 40
+nav_order: 25
 ---
 
 # Event aggregation

_data-prepper/common-use-cases/log-analytics.md

@@ -2,7 +2,7 @@
 layout: default
 title: Log analytics
 parent: Common use cases
-nav_order: 10
+nav_order: 30
 ---
 
 # Log analytics

_data-prepper/common-use-cases/log-enrichment.md

@@ -2,7 +2,7 @@
 layout: default
 title: Log enrichment
 parent: Common use cases
-nav_order: 50
+nav_order: 35
 ---
 
 # Log enrichment

_data-prepper/common-use-cases/metrics-traces.md

@@ -2,7 +2,7 @@
 layout: default
 title: Deriving metrics from traces
 parent: Common use cases
-nav_order: 60
+nav_order: 20
 ---
 
 # Deriving metrics from traces

_data-prepper/common-use-cases/s3-logs.md

@@ -2,7 +2,7 @@
 layout: default
 title: S3 logs
 parent: Common use cases
-nav_order: 20
+nav_order: 40
 ---
 
 # S3 logs

_data-prepper/common-use-cases/text-processing.md

@@ -2,7 +2,7 @@
 layout: default
 title: Text processing
 parent: Common use cases
-nav_order: 35
+nav_order: 55
 ---
 
 # Text processing

_data-prepper/common-use-cases/trace-analytics.md

@@ -2,7 +2,7 @@
 layout: default
 title: Trace analytics
 parent: Common use cases
-nav_order: 5
+nav_order: 60
 ---
 
 # Trace analytics
@@ -15,7 +15,7 @@ When using Data Prepper as a server-side component to collect trace data, you ca
 
 The following flowchart illustrates the trace analytics workflow, from running OpenTelemetry Collector to using OpenSearch Dashboards for visualization.
 
-<img src="{{site.url}}{{site.baseurl}}/images/data-prepper/trace-analytics/trace-analytics-components.jpg" alt="Trace analyticis component overview">{: .img-fluid}
+<img src="{{site.url}}{{site.baseurl}}/images/data-prepper/trace-analytics/trace-analytics-components.jpg" alt="Trace analytics component overview">{: .img-fluid}
 
 To monitor trace analytics, you need to set up the following components in your service environment:
 - Add **instrumentation** to your application so it can generate telemetry data and send it to an OpenTelemetry collector.
@@ -322,7 +322,7 @@ For other configurations available for OpenSearch sinks, see [Data Prepper OpenS
 
 ## OpenTelemetry Collector
 
-You need to run OpenTelemetry Collector in your service environment. Follow [Getting Started](https://opentelemetry.io/docs/collector/getting-started/#getting-started) to install an OpenTelemetry collector.  Ensure that you configure the collector with an exporter configured for your Data Prepper instance. The following example `otel-collector-config.yaml` file receives data from various instrumentations and exports it to Data Prepper.
+You need to run OpenTelemetry Collector in your service environment. Follow [Getting Started](https://opentelemetry.io/docs/collector/getting-started/#getting-started) to install an OpenTelemetry collector. Ensure that you configure the collector with an exporter configured for your Data Prepper instance. The following example `otel-collector-config.yaml` file receives data from various instrumentations and exports it to Data Prepper.
 
 ### Example otel-collector-config.yaml file