diff --git a/content/docs/next-release/apis.md b/content/docs/next-release/apis.md
index e092f0ae..9dcf966c 100644
--- a/content/docs/next-release/apis.md
+++ b/content/docs/next-release/apis.md
@@ -35,7 +35,7 @@ The OTLP data is accepted in these formats: (1) binary gRPC, (2) Protobuf over H
 
 **Deprecated**: we recommend the OpenTelemetry protocol.
 
-Since Jaeger v1.11, the official protocol between applicationss and **jaeger-collector**s is `jaeger.api_v2.CollectorService` gRPC endpoint defined in [collector.proto] IDL file. The same endpoint can be used to submit trace data from SDKs directly to **jaeger-collector**.
+Since Jaeger v1.11, the official protocol between user applications and **jaeger-collector**s is `jaeger.api_v2.CollectorService` gRPC endpoint defined in [collector.proto] IDL file. The same endpoint can be used to submit trace data from SDKs directly to **jaeger-collector**.
 
 ### Thrift over HTTP (stable)
 
diff --git a/content/docs/next-release/faq.md b/content/docs/next-release/faq.md
index 2491cfdc..8b83ee6c 100644
--- a/content/docs/next-release/faq.md
+++ b/content/docs/next-release/faq.md
@@ -20,7 +20,7 @@ Please refer to the [Troubleshooting](../troubleshooting/) guide.
 
 Since the Jaeger client libraries [are deprecated](../client-libraries) and the OpenTelemetry SDKs are phasing out support for Jaeger Thrift format, the **jaeger-agent** is no longer required and no longer supported. See the [Architecture](../architecture) page for alternative deployment options.
 
-Sometimes it is still desireable to run a **host agent**:
+Sometimes it is still desirable to run a **host agent**:
 
   * If we want SDKs to send trace data directly to **jaeger-collector**s, we must provide them with a URL of the HTTP endpoint. It means that our applications require additional configuration containing this parameter, especially if we are running multiple Jaeger installations (e.g. in different availability zones or regions) and want the data sent to a nearby installation. In contrast, when using the host agent, the libraries require no additional configuration because the agent is always accessible via `localhost`. It acts as a sidecar and proxies the requests to the appropriate **jaeger-collector**s.
   * A host agent can be configured to enrich the tracing data with infrastructure-specific metadata by adding extra tags to the spans, such as the current zone, region, etc. If the host agent is running as a host daemon, it will be shared by all applications running on the same host. If the host agent is running as a true sidecar, i.e. one per application, it can provide additional functionality such as strong authentication, multi-tenancy (see [this blog post](https://medium.com/jaegertracing/jaeger-and-multitenancy-99dfa1d49dc0)), pod name, etc.