[chore] Correct typos in the OTel-Arrow README (open-telemetry#30767)

**Description:** The project name is OpenTelemetry Project with Apache
Arrow. The abbreviation OTel-Arrow should not be used in the ways it
was, it is only suitable as the name of the repository and various
configuration field names.

exporter/otelarrowexporter/README.md

@@ -1,4 +1,4 @@
-# OTel Arrow Exporter
+# OpenTelemetry Protocol with Apache Arrow Exporter
 
 <!-- status autogenerated section -->
 | Status        |           |
@@ -99,7 +99,8 @@ Several helper files are leveraged to provide additional capabilities automatica
 ### Arrow-specific Configuration
 
 In the `arrow` configuration block, the following settings enable and
-disable the use of OTel Arrow as opposed to standard OTLP.
+disable the use of OpenTelemetry Protocol with Apache Arrow as opposed
+to standard OTLP.
 
 - `disabled` (default: false): disables use of Arrow, causing the exporter to use standard OTLP
 - `disable_downgrade` (default: false): prevents this exporter from using standard OTLP.
@@ -196,15 +197,15 @@ for general information about the choice of Zstd by default, for other
 general compression configuration and benchmark information.
 
 For the OpenTelemetry Protocol with Apache Arrow streams specifically,
-gRPC-level the Zstd compression level can be configured.  However, there
-is an important caveat: the gRPC-Go library requires that compressor
-implementations be registered statically.  These libraries use
-compressors named `zstdarrow1`, `zstdarrow2`, ..., `zstdarrow10`,
+gRPC-level the Zstd compression level can be configured.  However,
+there is an important caveat: the gRPC-Go library requires that
+compressor implementations be registered statically.  These libraries
+use compressors named `zstdarrow1`, `zstdarrow2`, ..., `zstdarrow10`,
 supporting 10 configurable compression levels.  Note, however that
 these configurations are static and only one unique configuration is
-possible per level.  It is possible to configure multiple OTel-Arrow
-exporters with different Zstd configuration simply by using distinct
-levels.
+possible per level.  It is possible to configure multiple
+OpenTelemetry Protocol with Apache Arrow exporters with different Zstd
+configuration simply by using distinct levels.
 
 Under `arrow`, the `zstd` sub-configuration has the following fields: