This is an automated email from the ASF dual-hosted git repository.
mgrigorov pushed a commit to branch branch-1.11
in repository https://gitbox.apache.org/repos/asf/avro.git
The following commit(s) were added to refs/heads/branch-1.11 by this push:
new dfa129bd0 docs: Fix a few typos (#1871)
dfa129bd0 is described below
commit dfa129bd0af995659f0af80074ffcfa560ac826c
Author: Tim Gates <[email protected]>
AuthorDate: Fri Sep 16 18:09:22 2022 +1000
docs: Fix a few typos (#1871)
* docs: Fix a few typos
There are small typos in:
- doc/content/en/docs/++version++/Specification/_index.md
- lang/py/avro/tether/tether_task.py
Fixes:
- Should read `correspondence` rather than `correspondance`.
- Should read `containing` rather than `containg`.
Signed-off-by: Tim Gates <[email protected]>
* Update tether_task.py
Signed-off-by: Tim Gates <[email protected]>
(cherry picked from commit 8d4a22bdf1726c9782752251518b685013c43c9f)
---
doc/content/en/docs/++version++/Specification/_index.md | 2 +-
lang/py/avro/tether/tether_task.py | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/content/en/docs/++version++/Specification/_index.md
b/doc/content/en/docs/++version++/Specification/_index.md
index 49bdaf77f..c98aea481 100755
--- a/doc/content/en/docs/++version++/Specification/_index.md
+++ b/doc/content/en/docs/++version++/Specification/_index.md
@@ -564,7 +564,7 @@ A transport is a system that supports:
* **transmission of request messages**
* **receipt of corresponding response messages**
-Servers may send a response message back to the client corresponding to a
request message. The mechanism of correspondance is transport-specific. For
example, in HTTP it is implicit, since HTTP directly supports requests and
responses. But a transport that multiplexes many client threads over a single
socket would need to tag messages with unique identifiers.
+Servers may send a response message back to the client corresponding to a
request message. The mechanism of correspondence is transport-specific. For
example, in HTTP it is implicit, since HTTP directly supports requests and
responses. But a transport that multiplexes many client threads over a single
socket would need to tag messages with unique identifiers.
Transports may be either stateless or stateful. In a stateless transport,
messaging assumes no established connection state, while stateful transports
establish connections that may be used for multiple messages. This distinction
is discussed further in the [handshake](#handshake) section below.
diff --git a/lang/py/avro/tether/tether_task.py
b/lang/py/avro/tether/tether_task.py
index 070ae57bc..dc138d07d 100644
--- a/lang/py/avro/tether/tether_task.py
+++ b/lang/py/avro/tether/tether_task.py
@@ -318,8 +318,8 @@ class TetherTask(abc.ABC):
Parameters
------------------------------------------------------
- data - Sould containg the bytes encoding the serialized data
- - I think this gets represented as a tring
+ data - Should contain the bytes encoding the serialized data
+ - I think this gets represented as a string
count - how many input records are provided in the binary stream
"""
try:
