summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorReynaldo H. Verdejo Pinochet <r.verdejo@partner.samsung.com>2013-10-14 22:03:50 -0700
committerReynaldo H. Verdejo Pinochet <r.verdejo@partner.samsung.com>2013-10-22 13:41:05 -0700
commitd9845843075c88de4beee79b87195bdb0b70dcde (patch)
tree3d08be2eebd3e23f163e5e7dc3a7ebc469ad12c6
parent1811d966b53b8bc19b63df0b1b4209d67a4cb838 (diff)
docs: Gram and nit fixes for part-element-source.txt
-rw-r--r--docs/design/part-element-source.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/design/part-element-source.txt b/docs/design/part-element-source.txt
index fc7f13dd1..8c98553c9 100644
--- a/docs/design/part-element-source.txt
+++ b/docs/design/part-element-source.txt
@@ -20,8 +20,8 @@ A source is said to be a live source when it has the following property:
* temporarily stopping reading from the source causes data to be lost.
In general when this property holds, the source also produces data at a fixed
-rate. Most sources have a limit to the rate at which they can deliver data, which
-might be faster or slower than the consumption rate. this property however does
+rate. Most sources have a limit on the rate at which they can deliver data, which
+might be faster or slower than the consumption rate. This property however does
not make them a live source.
Let's look at some example sources.
@@ -32,7 +32,7 @@ Let's look at some example sources.
for example) in which case you might need to use some buffering
(see part-buffering.txt).
- - http network element: you can PAUSE without data loss. Depending on the
+ - HTTP network element: you can PAUSE without data loss. Depending on the
available network bandwidth, consumption rate might be higher than production
rate in which case buffering should be used (see part-buffering.txt).
@@ -105,7 +105,7 @@ elements that cannot do random access, or at least very slowly. The
source usually prefers to push out a fixed size buffer.
Classes extending this base class will usually be scheduled in a push
-based mode. It the peer accepts to operate without offsets and withing
+based mode. If the peer accepts to operate without offsets and within
the limits of the allowed block size, this class can operate in getrange
based mode automatically.