From b76184198fd38adf2526bfde28e953d774229900 Mon Sep 17 00:00:00 2001 From: Andre Noll Date: Wed, 27 Apr 2011 00:53:42 +0200 Subject: [PATCH] manual: Fix two typos. --- web/manual.m4 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/web/manual.m4 b/web/manual.m4 index 30fe922f..5be89378 100644 --- a/web/manual.m4 +++ b/web/manual.m4 @@ -1533,7 +1533,7 @@ From these observations it is clear that there are three different FEC parameters: The slice size, the number of data slices k, and the total number of slices n. It is crucial to choose the slice size such that no fragmentation of network packets takes place because -FEC only guards against losses and reodering but fails if slices are +FEC only guards against losses and reordering but fails if slices are received partially. FEC decoding in paralash is performed through the fecdec filter which @@ -2032,7 +2032,7 @@ detection of duplicate or reordered packets. Being a connectionless protocol, only minimal internal state about the connection is maintained, which means that there is no protection against packet loss or network congestion. Error checking and correction (if at all) -are performed in the application.' +are performed in the application. *DCCP*. The _Datagram Congestion Control Protocol_ combines the connection-oriented state maintenance known from TCP with the -- 2.30.2