From 98c5d2a18bf185142a98baaeb55d3859c4471ac3 Mon Sep 17 00:00:00 2001 From: Scott Kirkpatrick Date: Mon, 8 Nov 2021 13:07:21 -0500 Subject: [PATCH] Re-add typo fixes (#353) The typo fixes that were added by commit b5d9aaa were accidentally reverted by commit 1e680e3, this will add them back --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9651811..750726f 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ rather than in a separate language such as .proto. This means there's no separat process, and no context switching between different languages. Some other features of tarpc: -- Pluggable transport: any type impling `Stream + Sink` can be +- Pluggable transport: any type implementing `Stream + Sink` can be used as a transport to connect the client and server. - `Send + 'static` optional: if the transport doesn't require it, neither does tarpc! - Cascading cancellation: dropping a request will send a cancellation message to the server. @@ -55,7 +55,7 @@ Some other features of tarpc: [tracing](https://github.com/tokio-rs/tracing) primitives extended with [OpenTelemetry](https://opentelemetry.io/) traces. Using a compatible tracing subscriber like [Jaeger](https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-jaeger), - each RPC can be traced through the client, server, amd other dependencies downstream of the + each RPC can be traced through the client, server, and other dependencies downstream of the server. Even for applications not connected to a distributed tracing collector, the instrumentation can also be ingested by regular loggers like [env_logger](https://github.com/env-logger-rs/env_logger/).