This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 9ac64eebe91 [fix][doc] Drop color code (#611)
9ac64eebe91 is described below
commit 9ac64eebe910b22598b52b8880d2d50baa924346
Author: tison <[email protected]>
AuthorDate: Fri Jun 16 08:41:36 2023 +0800
[fix][doc] Drop color code (#611)
Signed-off-by: tison <[email protected]>
---
docs/concepts-messaging.md | 4 ++--
versioned_docs/version-2.10.x/concepts-messaging.md | 4 ++--
versioned_docs/version-2.11.x/concepts-messaging.md | 4 ++--
versioned_docs/version-2.2.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.2.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.3.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.3.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.3.2/concepts-messaging.md | 4 ++--
versioned_docs/version-2.4.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.4.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.4.2/concepts-messaging.md | 4 ++--
versioned_docs/version-2.5.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.5.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.5.2/concepts-messaging.md | 4 ++--
versioned_docs/version-2.6.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.6.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.6.2/concepts-messaging.md | 4 ++--
versioned_docs/version-2.6.3/concepts-messaging.md | 4 ++--
versioned_docs/version-2.6.4/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.0/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.1/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.2/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.3/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.4/concepts-messaging.md | 4 ++--
versioned_docs/version-2.7.5/concepts-messaging.md | 4 ++--
versioned_docs/version-2.8.x/concepts-messaging.md | 4 ++--
versioned_docs/version-2.9.x/concepts-messaging.md | 4 ++--
versioned_docs/version-3.0.x/concepts-messaging.md | 4 ++--
28 files changed, 56 insertions(+), 56 deletions(-)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index 7647680b27d..ddccef9391a 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -1079,9 +1079,9 @@ All message retention and expiry are managed at the
[namespace](#namespaces) lev
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, all of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
all of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.10.x/concepts-messaging.md
b/versioned_docs/version-2.10.x/concepts-messaging.md
index da3bfa1df27..73c46dda567 100644
--- a/versioned_docs/version-2.10.x/concepts-messaging.md
+++ b/versioned_docs/version-2.10.x/concepts-messaging.md
@@ -930,9 +930,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
all of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md
b/versioned_docs/version-2.11.x/concepts-messaging.md
index 01735effb82..29a2bcfb86f 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -1086,9 +1086,9 @@ All message retention and expiry are managed at the
[namespace](#namespaces) lev
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, all of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
all of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.2.0/concepts-messaging.md
b/versioned_docs/version-2.2.0/concepts-messaging.md
index f7307464539..cd575346837 100644
--- a/versioned_docs/version-2.2.0/concepts-messaging.md
+++ b/versioned_docs/version-2.2.0/concepts-messaging.md
@@ -887,9 +887,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.2.1/concepts-messaging.md
b/versioned_docs/version-2.2.1/concepts-messaging.md
index f7307464539..ffeb63a491b 100644
--- a/versioned_docs/version-2.2.1/concepts-messaging.md
+++ b/versioned_docs/version-2.2.1/concepts-messaging.md
@@ -887,9 +887,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
all of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.3.0/concepts-messaging.md
b/versioned_docs/version-2.3.0/concepts-messaging.md
index 41c4bf0d234..0868f453080 100644
--- a/versioned_docs/version-2.3.0/concepts-messaging.md
+++ b/versioned_docs/version-2.3.0/concepts-messaging.md
@@ -304,9 +304,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.3.1/concepts-messaging.md
b/versioned_docs/version-2.3.1/concepts-messaging.md
index 1617c223f26..fb48fc12034 100644
--- a/versioned_docs/version-2.3.1/concepts-messaging.md
+++ b/versioned_docs/version-2.3.1/concepts-messaging.md
@@ -304,9 +304,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.3.2/concepts-messaging.md
b/versioned_docs/version-2.3.2/concepts-messaging.md
index c9e7380e07c..55f51c1eafc 100644
--- a/versioned_docs/version-2.3.2/concepts-messaging.md
+++ b/versioned_docs/version-2.3.2/concepts-messaging.md
@@ -367,9 +367,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.4.0/concepts-messaging.md
b/versioned_docs/version-2.4.0/concepts-messaging.md
index bf38d84c3ac..e558d8b522d 100644
--- a/versioned_docs/version-2.4.0/concepts-messaging.md
+++ b/versioned_docs/version-2.4.0/concepts-messaging.md
@@ -380,9 +380,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.4.1/concepts-messaging.md
b/versioned_docs/version-2.4.1/concepts-messaging.md
index 685a3375afb..7ee04c51022 100644
--- a/versioned_docs/version-2.4.1/concepts-messaging.md
+++ b/versioned_docs/version-2.4.1/concepts-messaging.md
@@ -405,9 +405,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.4.2/concepts-messaging.md
b/versioned_docs/version-2.4.2/concepts-messaging.md
index 685a3375afb..7ee04c51022 100644
--- a/versioned_docs/version-2.4.2/concepts-messaging.md
+++ b/versioned_docs/version-2.4.2/concepts-messaging.md
@@ -405,9 +405,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.5.0/concepts-messaging.md
b/versioned_docs/version-2.5.0/concepts-messaging.md
index 2d10409bbf3..d2872e1a64c 100644
--- a/versioned_docs/version-2.5.0/concepts-messaging.md
+++ b/versioned_docs/version-2.5.0/concepts-messaging.md
@@ -409,9 +409,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.5.1/concepts-messaging.md
b/versioned_docs/version-2.5.1/concepts-messaging.md
index e83a9a5f294..374efed5a32 100644
--- a/versioned_docs/version-2.5.1/concepts-messaging.md
+++ b/versioned_docs/version-2.5.1/concepts-messaging.md
@@ -438,9 +438,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.5.2/concepts-messaging.md
b/versioned_docs/version-2.5.2/concepts-messaging.md
index e83a9a5f294..374efed5a32 100644
--- a/versioned_docs/version-2.5.2/concepts-messaging.md
+++ b/versioned_docs/version-2.5.2/concepts-messaging.md
@@ -438,9 +438,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.6.0/concepts-messaging.md
b/versioned_docs/version-2.6.0/concepts-messaging.md
index 67f2f676ce5..a7446178b00 100644
--- a/versioned_docs/version-2.6.0/concepts-messaging.md
+++ b/versioned_docs/version-2.6.0/concepts-messaging.md
@@ -470,9 +470,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.6.1/concepts-messaging.md
b/versioned_docs/version-2.6.1/concepts-messaging.md
index 31ea06a93f4..44dbe3225a5 100644
--- a/versioned_docs/version-2.6.1/concepts-messaging.md
+++ b/versioned_docs/version-2.6.1/concepts-messaging.md
@@ -489,9 +489,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.6.2/concepts-messaging.md
b/versioned_docs/version-2.6.2/concepts-messaging.md
index 31ea06a93f4..44dbe3225a5 100644
--- a/versioned_docs/version-2.6.2/concepts-messaging.md
+++ b/versioned_docs/version-2.6.2/concepts-messaging.md
@@ -489,9 +489,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.6.3/concepts-messaging.md
b/versioned_docs/version-2.6.3/concepts-messaging.md
index 31ea06a93f4..44dbe3225a5 100644
--- a/versioned_docs/version-2.6.3/concepts-messaging.md
+++ b/versioned_docs/version-2.6.3/concepts-messaging.md
@@ -489,9 +489,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.6.4/concepts-messaging.md
b/versioned_docs/version-2.6.4/concepts-messaging.md
index 78d8e725afe..30ccf0f34b3 100644
--- a/versioned_docs/version-2.6.4/concepts-messaging.md
+++ b/versioned_docs/version-2.6.4/concepts-messaging.md
@@ -486,9 +486,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.0/concepts-messaging.md
b/versioned_docs/version-2.7.0/concepts-messaging.md
index 88dd446d1ee..b5128e9c052 100644
--- a/versioned_docs/version-2.7.0/concepts-messaging.md
+++ b/versioned_docs/version-2.7.0/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.1/concepts-messaging.md
b/versioned_docs/version-2.7.1/concepts-messaging.md
index 88dd446d1ee..b5128e9c052 100644
--- a/versioned_docs/version-2.7.1/concepts-messaging.md
+++ b/versioned_docs/version-2.7.1/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.2/concepts-messaging.md
b/versioned_docs/version-2.7.2/concepts-messaging.md
index 52718ca3fc4..cec2d8a8f21 100644
--- a/versioned_docs/version-2.7.2/concepts-messaging.md
+++ b/versioned_docs/version-2.7.2/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.3/concepts-messaging.md
b/versioned_docs/version-2.7.3/concepts-messaging.md
index 88dd446d1ee..b5128e9c052 100644
--- a/versioned_docs/version-2.7.3/concepts-messaging.md
+++ b/versioned_docs/version-2.7.3/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.4/concepts-messaging.md
b/versioned_docs/version-2.7.4/concepts-messaging.md
index 88dd446d1ee..b5128e9c052 100644
--- a/versioned_docs/version-2.7.4/concepts-messaging.md
+++ b/versioned_docs/version-2.7.4/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.7.5/concepts-messaging.md
b/versioned_docs/version-2.7.5/concepts-messaging.md
index 88dd446d1ee..b5128e9c052 100644
--- a/versioned_docs/version-2.7.5/concepts-messaging.md
+++ b/versioned_docs/version-2.7.5/concepts-messaging.md
@@ -559,9 +559,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.8.x/concepts-messaging.md
b/versioned_docs/version-2.8.x/concepts-messaging.md
index 9675dd11e0b..9d130fc4c21 100644
--- a/versioned_docs/version-2.8.x/concepts-messaging.md
+++ b/versioned_docs/version-2.8.x/concepts-messaging.md
@@ -641,9 +641,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-2.9.x/concepts-messaging.md
b/versioned_docs/version-2.9.x/concepts-messaging.md
index 7285e21aaf7..cc0b926bb80 100644
--- a/versioned_docs/version-2.9.x/concepts-messaging.md
+++ b/versioned_docs/version-2.9.x/concepts-messaging.md
@@ -655,9 +655,9 @@ The diagram below illustrates both concepts:
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, *all* of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
*all* of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
diff --git a/versioned_docs/version-3.0.x/concepts-messaging.md
b/versioned_docs/version-3.0.x/concepts-messaging.md
index 7647680b27d..ddccef9391a 100644
--- a/versioned_docs/version-3.0.x/concepts-messaging.md
+++ b/versioned_docs/version-3.0.x/concepts-messaging.md
@@ -1079,9 +1079,9 @@ All message retention and expiry are managed at the
[namespace](#namespaces) lev
-With message retention, shown at the top, a <span style={{color: "
#89b557"}}>retention policy</span> applied to all topics in a namespace
dictates that some messages are durably stored in Pulsar even though they've
already been acknowledged. Acknowledged messages that are not covered by the
retention policy are <span style={{color: " #bb3b3e"}}>deleted</span>. Without
a retention policy, all of the <span style={{color: " #19967d"}}>acknowledged
messages</span> would be deleted.
+With message retention, shown at the top, a retention policy applied to all
topics in a namespace dictates that some messages are durably stored in Pulsar
even though they've already been acknowledged. Acknowledged messages that are
not covered by the retention policy are deleted. Without a retention policy,
all of the acknowledged messages would be deleted.
-With message expiry, shown at the bottom, some messages are <span
style={{color: " #bb3b3e"}}>deleted</span>, even though they <span
style={{color: " #337db6"}}>haven't been acknowledged</span>, because they've
expired according to the <span style={{color: " #e39441"}}>TTL applied to the
namespace</span> (for example because a TTL of 5 minutes has been applied and
the messages haven't been acknowledged but are 10 minutes old).
+With message expiry, shown at the bottom, some messages are deleted, even
though they haven't been acknowledged, because they've expired according to the
TTL applied to the namespace (for example because a TTL of 5 minutes has been
applied and the messages haven't been acknowledged but are 10 minutes old).
## Message deduplication
