Merge branch 'main' into patch-4

docs/ingest-via-json-api-endpoint-3416f8f.md

@@ -167,7 +167,7 @@ If you cannot find the payload shipped in the respective index, the default dash
 
 ## Result
 
-You can analyze the ingested OpenTelemetry data in OpenSearch Dashboards \(see [Access and Analyze Observability Data](access-and-analyze-observability-data-dad5b01.md), based on custom dashboards or the Discover view. Indices match the following pattern: `logs-json-.*` 
+You can analyze the ingested data in OpenSearch Dashboards \(see [Access and Analyze Observability Data](access-and-analyze-observability-data-dad5b01.md), based on custom dashboards or the Discover view. Indices match the following pattern: `logs-json-.*` 
 
 > ### Note:  
 > There are OpenSearch specifics restricting ingestion, such as mapping conflicts. Mapping conflicts in OpenSearch occur when indices have conflicting field mappings, leading to ambiguity in data interpretation and query failures. Resolving these conflicts involves aligning field types, analyzers, and other properties across indices to ensure consistent data handling and accurate search results. Cloud Logging performs basic sanitation and unification steps to prevent mapping conflicts. However, sending type-aligned data is mandatory to prevent mapping conflicts.

docs/prerequisites-41d8559.md

@@ -171,7 +171,7 @@ Set `sp.signature_private_key` and `sp.signature_private_key_password` if you se
 <tr>
 <td valign="top">
 
-Add `exchange_key` to sign tokens, or remove line. Provide a random key with an even character length \(minimum length: 32\) of alphanumeric characters \(A-Z, a-z, 0-9\). The system generates a randome key f the key is not provided.
+Add `exchange_key` to sign tokens, or remove line. Provide a random key with an even character length \(minimum length: 32\) of alphanumeric characters \(A-Z, a-z, 0-9\). The system generates a random key if the key is not specified.
 
 </td>
 </tr>