kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From guozh...@apache.org
Subject kafka git commit: MINOR: Fix homophone typo in Design documentation
Date Fri, 06 Nov 2015 23:28:15 GMT
Repository: kafka
Updated Branches:
  refs/heads/trunk a9e4ce79f -> 09ff68673


MINOR: Fix homophone typo in Design documentation

Noticed that there was a small typo in section 4.1 of the Design documentation on the [website](https://kafka.apache.org/documentation.html#majordesignelements)
('new' vs. 'knew'). This patch corrects that.

Author: Chris Pinola <chris@pinola.co>

Reviewers: Guozhang Wang

Closes #391 from chrnola/minor/design-doc-typo


Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/09ff6867
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/09ff6867
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/09ff6867

Branch: refs/heads/trunk
Commit: 09ff68673843109eedc5caae4bf46e62d1868aab
Parents: a9e4ce7
Author: Chris Pinola <chris@pinola.co>
Authored: Fri Nov 6 15:34:04 2015 -0800
Committer: Guozhang Wang <wangguoz@gmail.com>
Committed: Fri Nov 6 15:34:04 2015 -0800

----------------------------------------------------------------------
 docs/design.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/09ff6867/docs/design.html
----------------------------------------------------------------------
diff --git a/docs/design.html b/docs/design.html
index b7a6e7d..347f602 100644
--- a/docs/design.html
+++ b/docs/design.html
@@ -27,7 +27,7 @@ It also meant the system would have to handle low-latency delivery to handle
mor
 <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.
 


Mime
View raw message