From commits-return-16561-archive-asf-public=cust-asf.ponee.io@pulsar.apache.org Sat Oct 27 16:06:57 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 79A4B180675 for ; Sat, 27 Oct 2018 16:06:57 +0200 (CEST) Received: (qmail 94749 invoked by uid 500); 27 Oct 2018 14:06:56 -0000 Mailing-List: contact commits-help@pulsar.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pulsar.apache.org Delivered-To: mailing list commits@pulsar.apache.org Received: (qmail 94740 invoked by uid 99); 27 Oct 2018 14:06:56 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Oct 2018 14:06:56 +0000 From: GitBox To: commits@pulsar.apache.org Subject: [GitHub] merlimat closed pull request #2862: fix typo in architecture docs Message-ID: <154064921599.31305.13834742924951528509.gitbox@gitbox.apache.org> Date: Sat, 27 Oct 2018 14:06:55 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit merlimat closed pull request #2862: fix typo in architecture docs URL: https://github.com/apache/pulsar/pull/2862 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/site/docs/latest/getting-started/ConceptsAndArchitecture.md b/site/docs/latest/getting-started/ConceptsAndArchitecture.md index fe48437a5e..961141abe4 100644 --- a/site/docs/latest/getting-started/ConceptsAndArchitecture.md +++ b/site/docs/latest/getting-started/ConceptsAndArchitecture.md @@ -249,7 +249,7 @@ At the highest level, a Pulsar {% popover instance %} is composed of one or more In a Pulsar cluster: * One or more {% popover brokers %} handles and load balances incoming messages from {% popover producers %}, dispatches messages to {% popover consumers %}, communicates with the Pulsar {% popover configuration store %} to handle various coordination tasks, stores messages in {% popover BookKeeper %} instances (aka {% popover bookies %}), relies on a cluster-specific {% popover ZooKeeper %} cluster for certain tasks, and more. -* A {% popover BookKeeper %} cluster consisting of one more or more {% popover bookies %} handles [persistent storage](#persistent-storage) of messages. +* A {% popover BookKeeper %} cluster consisting of one or more {% popover bookies %} handles [persistent storage](#persistent-storage) of messages. * A {% popover ZooKeeper %} cluster specific to that cluster handles The diagram below provides an illustration of a Pulsar cluster: diff --git a/site2/docs/concepts-architecture-overview.md b/site2/docs/concepts-architecture-overview.md index 2487ec7da1..11e57e010a 100644 --- a/site2/docs/concepts-architecture-overview.md +++ b/site2/docs/concepts-architecture-overview.md @@ -9,7 +9,7 @@ At the highest level, a Pulsar instance is composed of one or more Pulsar cluste In a Pulsar cluster: * One or more brokers handles and load balances incoming messages from producers, dispatches messages to consumers, communicates with the Pulsar configuration store to handle various coordination tasks, stores messages in BookKeeper instances (aka bookies), relies on a cluster-specific ZooKeeper cluster for certain tasks, and more. -* A BookKeeper cluster consisting of one more or more bookies handles [persistent storage](#persistent-storage) of messages. +* A BookKeeper cluster consisting of one or more bookies handles [persistent storage](#persistent-storage) of messages. * A ZooKeeper cluster specific to that cluster handles The diagram below provides an illustration of a Pulsar cluster: diff --git a/site2/website/versioned_docs/version-2.1.0-incubating/concepts-architecture-overview.md b/site2/website/versioned_docs/version-2.1.0-incubating/concepts-architecture-overview.md index 65ed4b8bd7..653bc5f2de 100644 --- a/site2/website/versioned_docs/version-2.1.0-incubating/concepts-architecture-overview.md +++ b/site2/website/versioned_docs/version-2.1.0-incubating/concepts-architecture-overview.md @@ -10,7 +10,7 @@ At the highest level, a Pulsar instance is composed of one or more Pulsar cluste In a Pulsar cluster: * One or more brokers handles and load balances incoming messages from producers, dispatches messages to consumers, communicates with the Pulsar configuration store to handle various coordination tasks, stores messages in BookKeeper instances (aka bookies), relies on a cluster-specific ZooKeeper cluster for certain tasks, and more. -* A BookKeeper cluster consisting of one more or more bookies handles [persistent storage](#persistent-storage) of messages. +* A BookKeeper cluster consisting of one or more bookies handles [persistent storage](#persistent-storage) of messages. * A ZooKeeper cluster specific to that cluster handles The diagram below provides an illustration of a Pulsar cluster: ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services