[kafka] branch trunk updated: MINOT: Fix punctuation marks (#12613)

[mj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mjsax pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 74718059896 MINOT: Fix punctuation marks (#12613)
74718059896 is described below

commit 747180598964f7af7195aa6584541cd947a5426b
Author: liuzc9 <90...@users.noreply.github.com>
AuthorDate: Thu Dec 29 04:52:47 2022 +0800

    MINOT: Fix punctuation marks (#12613)
    
    Reviewers: Divij Vaidya <di...@amazon.com>, Matthias J. Sax <ma...@confluent.io>
---
 docs/streams/architecture.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/streams/architecture.html b/docs/streams/architecture.html
index e561231c311..f0561296148 100644
--- a/docs/streams/architecture.html
+++ b/docs/streams/architecture.html
@@ -68,8 +68,8 @@
     <p>
         Slightly simplified, the maximum parallelism at which your application may run is bounded by the maximum number of stream tasks, which itself is determined by
         maximum number of partitions of the input topic(s) the application is reading from. For example, if your input topic has 5 partitions, then you can run up to 5
-        applications instances. These instances will collaboratively process the topic’s data. If you run a larger number of app instances than partitions of the input
-        topic, the “excess” app instances will launch but remain idle; however, if one of the busy instances goes down, one of the idle instances will resume the former’s
+        applications instances. These instances will collaboratively process the topic's data. If you run a larger number of app instances than partitions of the input
+        topic, the "excess" app instances will launch but remain idle; however, if one of the busy instances goes down, one of the idle instances will resume the former's
         work.
     </p>