summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2019-10-17 07:02:05 -0700
committerKaz Kylheku <kaz@kylheku.com>2019-10-17 07:02:05 -0700
commitbaebc1360bfe784bf60bf97c798a0a49ff1634a1 (patch)
tree358dac378797d4c475518d5c86846055949ab0b7
parent800b8dd3570c254996649c29370da72c79033276 (diff)
downloadtxr-baebc1360bfe784bf60bf97c798a0a49ff1634a1.tar.gz
txr-baebc1360bfe784bf60bf97c798a0a49ff1634a1.tar.bz2
txr-baebc1360bfe784bf60bf97c798a0a49ff1634a1.zip
doc: grammar fix in datagram streams.
* txr.1: Subject-verb number agreement; also removing superfluous adverb.
-rw-r--r--txr.12
1 files changed, 1 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index 3b430094..126fd8c9 100644
--- a/txr.1
+++ b/txr.1
@@ -59136,7 +59136,7 @@ functions which are usually used for datagram programming.
Datagram I/O assumes that the datagram datagram socket is connected to a
specific remote peer, and that peer is implicitly used for all I/O.
-Datagram streams solves the message framing problem essentially by
+Datagram streams solve the message framing problem by
considering a single datagram to be an entire stream. On input, a datagram
stream holds an entire datagram in a buffer. The stream ends
(experiences the EOF condition) after the last byte of this buffer