You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by li...@apache.org on 2022/06/27 05:18:45 UTC

[pulsar] branch master updated: [hotfix][txn-why][docs] Corrected typo (#16185)

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

liuyu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new a16a2093edc [hotfix][txn-why][docs] Corrected typo (#16185)
a16a2093edc is described below

commit a16a2093edc3531b350597838b0d17627bbe0dbb
Author: mans2singh <ma...@users.noreply.github.com>
AuthorDate: Mon Jun 27 01:18:38 2022 -0400

    [hotfix][txn-why][docs] Corrected typo (#16185)
---
 site2/docs/txn-why.md                                  | 2 +-
 site2/website/versioned_docs/version-2.10.0/txn-why.md | 2 +-
 site2/website/versioned_docs/version-2.8.0/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.8.1/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.8.2/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.8.3/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.9.0/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.9.1/txn-why.md  | 2 +-
 site2/website/versioned_docs/version-2.9.2/txn-why.md  | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/site2/docs/txn-why.md b/site2/docs/txn-why.md
index c4f607db8bc..8daf5bce559 100644
--- a/site2/docs/txn-why.md
+++ b/site2/docs/txn-why.md
@@ -41,4 +41,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.10.0/txn-why.md b/site2/website/versioned_docs/version-2.10.0/txn-why.md
index 1b489d4886c..e7273379f79 100644
--- a/site2/website/versioned_docs/version-2.10.0/txn-why.md
+++ b/site2/website/versioned_docs/version-2.10.0/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.8.0/txn-why.md b/site2/website/versioned_docs/version-2.8.0/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.8.0/txn-why.md
+++ b/site2/website/versioned_docs/version-2.8.0/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.8.1/txn-why.md b/site2/website/versioned_docs/version-2.8.1/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.8.1/txn-why.md
+++ b/site2/website/versioned_docs/version-2.8.1/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.8.2/txn-why.md b/site2/website/versioned_docs/version-2.8.2/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.8.2/txn-why.md
+++ b/site2/website/versioned_docs/version-2.8.2/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.8.3/txn-why.md b/site2/website/versioned_docs/version-2.8.3/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.8.3/txn-why.md
+++ b/site2/website/versioned_docs/version-2.8.3/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.9.0/txn-why.md b/site2/website/versioned_docs/version-2.9.0/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.9.0/txn-why.md
+++ b/site2/website/versioned_docs/version-2.9.0/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.9.1/txn-why.md b/site2/website/versioned_docs/version-2.9.1/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.9.1/txn-why.md
+++ b/site2/website/versioned_docs/version-2.9.1/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file
diff --git a/site2/website/versioned_docs/version-2.9.2/txn-why.md b/site2/website/versioned_docs/version-2.9.2/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website/versioned_docs/version-2.9.2/txn-why.md
+++ b/site2/website/versioned_docs/version-2.9.2/txn-why.md
@@ -42,4 +42,4 @@ In Pulsar, the highest level of message delivery guarantee is using an [idempote
 
 - Consumers need to rely on more mechanisms to acknowledge (ack) messages once. 
   
-  For example, consumers are required to store the MessgeID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessgeID in memory when the topic is loaded again.
\ No newline at end of file
+  For example, consumers are required to store the MessageID along with its acked state. After the topic is unloaded, the subscription can recover the acked state of this MessageID in memory when the topic is loaded again.
\ No newline at end of file