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 01:44:31 UTC

[pulsar] branch master updated: [fix][doc] Fix truncated notes #16230

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 f3ab91831bf [fix][doc] Fix truncated notes #16230
f3ab91831bf is described below

commit f3ab91831bfa5470a711dec0f382da0c50fd7ad3
Author: Sherlock Xu <65...@users.noreply.github.com>
AuthorDate: Mon Jun 27 09:44:24 2022 +0800

    [fix][doc] Fix truncated notes #16230
---
 site2/docs/helm-upgrade.md                                  | 4 +---
 site2/website/versioned_docs/version-2.10.0/helm-upgrade.md | 4 +---
 site2/website/versioned_docs/version-2.5.1/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.5.2/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.6.0/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.6.1/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.6.2/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.6.3/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.6.4/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.7.0/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.7.1/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.7.2/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.7.3/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.7.4/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.8.0/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.8.1/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.8.2/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.8.3/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.9.0/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.9.1/helm-upgrade.md  | 4 +---
 site2/website/versioned_docs/version-2.9.2/helm-upgrade.md  | 4 +---
 21 files changed, 21 insertions(+), 63 deletions(-)

diff --git a/site2/docs/helm-upgrade.md b/site2/docs/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/docs/helm-upgrade.md
+++ b/site2/docs/helm-upgrade.md
@@ -10,12 +10,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.10.0/helm-upgrade.md b/site2/website/versioned_docs/version-2.10.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.10.0/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.10.0/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.5.1/helm-upgrade.md b/site2/website/versioned_docs/version-2.5.1/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/website/versioned_docs/version-2.5.1/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.5.1/helm-upgrade.md
@@ -10,12 +10,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.5.2/helm-upgrade.md b/site2/website/versioned_docs/version-2.5.2/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/website/versioned_docs/version-2.5.2/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.5.2/helm-upgrade.md
@@ -10,12 +10,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.6.0/helm-upgrade.md b/site2/website/versioned_docs/version-2.6.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.6.0/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.6.0/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.6.1/helm-upgrade.md b/site2/website/versioned_docs/version-2.6.1/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website/versioned_docs/version-2.6.1/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.6.1/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.6.2/helm-upgrade.md b/site2/website/versioned_docs/version-2.6.2/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website/versioned_docs/version-2.6.2/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.6.2/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.6.3/helm-upgrade.md b/site2/website/versioned_docs/version-2.6.3/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website/versioned_docs/version-2.6.3/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.6.3/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.6.4/helm-upgrade.md b/site2/website/versioned_docs/version-2.6.4/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website/versioned_docs/version-2.6.4/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.6.4/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.7.0/helm-upgrade.md b/site2/website/versioned_docs/version-2.7.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.7.0/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.7.0/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.7.1/helm-upgrade.md b/site2/website/versioned_docs/version-2.7.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.7.1/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.7.1/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.7.2/helm-upgrade.md b/site2/website/versioned_docs/version-2.7.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.7.2/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.7.2/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.7.3/helm-upgrade.md b/site2/website/versioned_docs/version-2.7.3/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.7.3/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.7.3/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.7.4/helm-upgrade.md b/site2/website/versioned_docs/version-2.7.4/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.7.4/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.7.4/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.8.0/helm-upgrade.md b/site2/website/versioned_docs/version-2.8.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.8.0/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.8.0/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.8.1/helm-upgrade.md b/site2/website/versioned_docs/version-2.8.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.8.1/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.8.1/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.8.2/helm-upgrade.md b/site2/website/versioned_docs/version-2.8.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.8.2/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.8.2/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.8.3/helm-upgrade.md b/site2/website/versioned_docs/version-2.8.3/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.8.3/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.8.3/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.9.0/helm-upgrade.md b/site2/website/versioned_docs/version-2.9.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.9.0/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.9.0/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.9.1/helm-upgrade.md b/site2/website/versioned_docs/version-2.9.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.9.1/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.9.1/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps:
diff --git a/site2/website/versioned_docs/version-2.9.2/helm-upgrade.md b/site2/website/versioned_docs/version-2.9.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website/versioned_docs/version-2.9.2/helm-upgrade.md
+++ b/site2/website/versioned_docs/version-2.9.2/helm-upgrade.md
@@ -11,12 +11,10 @@ We also recommend that you need to provide all values using the `helm upgrade --
 
 :::note
 
-You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely
+You can retrieve your previous `--set` arguments cleanly, with `helm get values <release-name>`. If you direct this into a file (`helm get values <release-name> > pulsar.yml`), you can safely pass this file through `-f`, namely `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
 
 :::
 
-pass this file through `-f`. Thus `helm upgrade <release-name> apache/pulsar -f pulsar.yaml`. This safely replaces the behavior of `--reuse-values`.
-
 ## Steps
 
 To upgrade Apache Pulsar to a newer version, follow these steps: