Update Jaeger readme to indicate future deprecation (#4270)

CONTRIBUTING.md

@@ -59,10 +59,6 @@ of Windows.
 * Visual Studio 2022+ or Visual Studio Code
 * .NET Framework 4.6.2+
 
-> **Note**
-> Visual Studio 2022 preview is **recommended** due to projects needing
-to target .NET preview versions.
-
 ### Public API
 
 It is critical to keep public API surface small and clean. This repository is

src/OpenTelemetry.Exporter.Jaeger/README.md

@@ -9,10 +9,12 @@ following the [OpenTelemetry specification](https://github.com/open-telemetry/op
 The exporter communicates to a Jaeger Agent through the Thrift protocol on
 the Compact Thrift API port, and as such only supports Thrift over UDP.
 
-## Getting Started
-
-Refer to the [Getting Started with
-Jaeger](../../docs/trace/getting-started-jaeger/README.md) tutorial.
+> **Note** This component is scheduled to be
+> [deprecated](https://github.com/open-telemetry/opentelemetry-specification/pull/2858)
+and users are advised to move to [OTLP
+Exporter](../OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md). The
+[getting started with Jaeger](../../docs/trace/getting-started-jaeger/README.md)
+tutorial shows how to use OTLP Exporter to export traces to Jaeger.
 
 ## Installation
 

src/OpenTelemetry.Extensions.Hosting/README.md

@@ -86,7 +86,7 @@ A fully functional example can be found
 ## Migrating from pre-release versions of OpenTelemetry.Extensions.Hosting
 
 Pre-release versions (all versions prior to 1.4.0) of
-`OpenTelemetry.Extenions.Hosting` contained signal-specific methods for
+`OpenTelemetry.Extensions.Hosting` contained signal-specific methods for
 configuring tracing and metrics:
 
 * `AddOpenTelemetryTracing`: Configure OpenTelemetry and register an