svn commit: r1546673 - in /kafka/site/08: design.html introduction.html

[ju...@apache.org]

Author: junrao
Date: Sat Nov 30 01:23:26 2013
New Revision: 1546673

URL: http://svn.apache.org/r1546673
Log:
KAFKA-1153; typos in documentationl; patched by Dan Hoffman; reviewed by Joe Stein and Jun Rao

Modified:
    kafka/site/08/design.html
    kafka/site/08/introduction.html

Modified: kafka/site/08/design.html
URL: http://svn.apache.org/viewvc/kafka/site/08/design.html?rev=1546673&r1=1546672&r2=1546673&view=diff
==============================================================================
--- kafka/site/08/design.html (original)
+++ kafka/site/08/design.html Sat Nov 30 01:23:26 2013
@@ -10,9 +10,9 @@ It also meant the system would have to h
 <p>
 We wanted to support partitioned, distributed, real-time processing of these feeds to create new, derived feeds. This motivated our partitioning and consumer model.
 <p>
-Finally in cases where the stream is fed into other data systems for serving we new the system would have to be able to guarantee fault-tolerance in the presence of machine failures.
+Finally in cases where the stream is fed into other data systems for serving we knew the system would have to be able to guarantee fault-tolerance in the presence of machine failures.
 <p>
-Supporting these uses led use to a design with a number of unique elements, more akin to a database log then a traditional messaging system. We will outline some elements of the design in the following sections.
+Supporting these uses led us to a design with a number of unique elements, more akin to a database log then a traditional messaging system. We will outline some elements of the design in the following sections.
 
 <h3><a id="persistence">4.2 Persistence</a></h3>
 <h4>Don't fear the filesystem!</h4>

Modified: kafka/site/08/introduction.html
URL: http://svn.apache.org/viewvc/kafka/site/08/introduction.html?rev=1546673&r1=1546672&r2=1546673&view=diff
==============================================================================
--- kafka/site/08/introduction.html (original)
+++ kafka/site/08/introduction.html Sat Nov 30 01:23:26 2013
@@ -69,7 +69,7 @@ A traditional queue retains messages in-
 <p>
 Kafka does it better. By having a notion of parallelism&mdash;the partition&mdash;within the topics, Kafka is able to provide both ordering guarantees and load balancing over a pool of consumer processes. This is achieved by assigning the partitions in the topic to the consumers in the consumer group so that each partition is consumed by exactly one consumer in the group. By doing this we ensure that the consumer is the only reader of that partition and consumes the data in order. Since there are many partitions this still balances the load over many consumer instances. Note however that there cannot be more consumer instances than partitions.
 <p>
-Not that partitioning means Kafka only provides a total order over messages <i>within</i> a partition. This combined with the ability to partition data by key is sufficient for the vast majority of applications. However, if you require a total order over messages this can be achieved with a topic that has only one partition, though this will mean only one consumer process.
+Kafka only provides a total order over messages <i>within</i> a partition. This combined with the ability to partition data by key is sufficient for the vast majority of applications. However, if you require a total order over messages this can be achieved with a topic that has only one partition, though this will mean only one consumer process.
 
 <h4>Guarantees</h4>