From: scipio <scipio>
Date: Tue, 1 Apr 2008 17:00:51 +0000 (+0000)
Subject: Edits from David Gay.
X-Git-Tag: release_tinyos_2_1_0_0~472
X-Git-Url: https://oss.titaniummirror.com/gitweb/?p=tinyos-2.x.git;a=commitdiff_plain;h=2c0e71d50b57d3194611948f14645e5df2a6bc43

Edits from David Gay.
---

diff --git a/doc/txt/tep113.txt b/doc/txt/tep113.txt
index a251db7d..bd7de8ef 100644
--- a/doc/txt/tep113.txt
+++ b/doc/txt/tep113.txt
@@ -280,22 +280,22 @@ actively sending an acknowledgement.
 
 Only the PC-to-mote communication path supports acknowledgements.
 SerialP does not request acknowledgements from the PC for two reasons.
-First, acks are not perfect reliability: they are used on the PC-to-mote
-path to raise reliability to a usable level. In the case of the PC-to-mote
-path, the UART receive buffer is typically a single byte, so a high interrupt
-load can easily lose (and sometimes does) a byte. This is in contrast
-to the PC receive buffer, which is much larger and does not have to
-deal with overflow. Second, adding support for acks would increase
-the code size and complexity of the serial stack. As code space is
-often at a premium, this would add little needed functionality at significant
-cost. Of course, any application that
-requires perfect reliability may layer its own scheme on top of the
-serial protocol.
+First, acks are not perfect reliable: they are used on the
+PC-to-mote path to raise reliability to a usable level. In the case of
+the PC-to-mote path, the UART receive buffer is typically a single
+byte, so a high interrupt load can easily lose (and sometimes does) a
+byte. This is in contrast to the PC receive buffer, which is much
+larger and does not have to deal with overflow. Second, adding support
+for acks would increase the code size and complexity of the serial
+stack. As code space is often at a premium, this would add little
+needed functionality at significant cost. Of course, any application
+that requires perfect reliability may layer its own scheme on top of
+the serial protocol.
 
 The acknowledgement protocol is stop-and-wait to minimize buffering on
 the mote side. This is considered more important on memory constrained
 devices than increased throughput in the PC-to-mote direction, which
-most applications only use for occasional contro transmissions.
+most applications only use for occasional control transmissions.
 
 
 3.4 Dispatcher: SerialDispatcherC