You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/06/27 06:01:37 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#a16a209)
This is an automated email from the ASF dual-hosted git repository.
urfree 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 fbe4692bd4a Docs sync done from apache/pulsar(#a16a209)
fbe4692bd4a is described below
commit fbe4692bd4aef26d926084d898ac0e1c613eeb03
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Mon Jun 27 06:01:31 2022 +0000
Docs sync done from apache/pulsar(#a16a209)
---
site2/website-next/docs/getting-started-helm.md | 2 +-
site2/website-next/docs/helm-upgrade.md | 4 +---
site2/website-next/docs/reference-configuration.md | 1 +
site2/website-next/docs/txn-why.md | 2 +-
.../versioned_docs/version-2.10.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.10.0/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.10.0/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.5.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.5.0/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.5.1/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.5.1/helm-upgrade.md | 4 +---
.../website-next/versioned_docs/version-2.5.2/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.5.2/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.5.2/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.6.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.6.0/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.6.0/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.6.1/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.6.1/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.6.1/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.6.2/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.6.2/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.6.2/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.6.3/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.6.3/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.6.3/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.6.4/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.6.4/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.6.4/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.7.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.7.0/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.7.0/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.7.1/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.7.1/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.7.1/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.7.2/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.7.2/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.7.2/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.7.3/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.7.3/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.7.3/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.7.4/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.7.4/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.7.4/kubernetes-helm.md | 2 +-
.../website-next/versioned_docs/version-2.8.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.0/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.8.0/kubernetes-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.0/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.8.1/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.1/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.8.1/kubernetes-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.1/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.8.2/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.2/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.8.2/kubernetes-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.2/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.8.3/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.8.3/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.8.3/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.9.0/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.9.0/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.9.0/kubernetes-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.9.0/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.9.1/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.9.1/kubernetes-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/txn-why.md | 2 +-
.../website-next/versioned_docs/version-2.9.2/getting-started-helm.md | 2 +-
site2/website-next/versioned_docs/version-2.9.2/helm-upgrade.md | 4 +---
site2/website-next/versioned_docs/version-2.9.2/txn-why.md | 2 +-
70 files changed, 70 insertions(+), 111 deletions(-)
diff --git a/site2/website-next/docs/getting-started-helm.md b/site2/website-next/docs/getting-started-helm.md
index 85906fb81ce..9a65b7596f2 100644
--- a/site2/website-next/docs/getting-started-helm.md
+++ b/site2/website-next/docs/getting-started-helm.md
@@ -427,7 +427,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/docs/helm-upgrade.md b/site2/website-next/docs/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/website-next/docs/helm-upgrade.md
+++ b/site2/website-next/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-next/docs/reference-configuration.md b/site2/website-next/docs/reference-configuration.md
index c5c636fd043..d8e3bf07aa8 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -334,6 +334,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated backlog size is greater
|replicatorPrefix| Replicator prefix used for replicator producer name and cursor name pulsar.repl||
|transactionBufferClientOperationTimeoutInMills|The transaction buffer client's operation timeout in milliseconds.|3000|
|transactionCoordinatorEnabled|Whether to enable transaction coordinator in broker.|true|
+|maxActiveTransactionsPerCoordinator| Max number of active transactions per transaction coordinator.|0|
|transactionMetadataStoreProviderClassName|The class name of transactionMetadataStoreProvider.|org.apache.pulsar.transaction.coordinator.impl.MLTransactionMetadataStoreProvider|
|transactionBufferSnapshotMaxTransactionCount|Transaction buffer takes a snapshot after the number of transaction operations reaches this value.|1000|
|transactionBufferSnapshotMinTimeInMillis| The interval between two snapshots that the transaction buffer takes (in milliseconds).|5000|
diff --git a/site2/website-next/docs/txn-why.md b/site2/website-next/docs/txn-why.md
index c4f607db8bc..8daf5bce559 100644
--- a/site2/website-next/docs/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.10.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.10.0/getting-started-helm.md
index 4b864a5c2de..9e32b3315a1 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.10.0/getting-started-helm.md
@@ -428,7 +428,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.10.0/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.10.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.10.0/txn-why.md b/site2/website-next/versioned_docs/version-2.10.0/txn-why.md
index 1b489d4886c..e7273379f79 100644
--- a/site2/website-next/versioned_docs/version-2.10.0/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.5.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.5.0/getting-started-helm.md
index 0523caa9644..fa521910b2e 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/getting-started-helm.md
@@ -383,7 +383,7 @@ Then proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you will be redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using Pulsar Manager.
+4. After successfully creating an environment, you will be redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor the cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.0/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.5.0/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.1/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.5.1/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.1/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.5.1/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.5.2/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.5.2/getting-started-helm.md
index 0eaea46496b..4dab89971de 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/getting-started-helm.md
@@ -424,7 +424,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.5.2/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.5.2/helm-upgrade.md
index 4923b9c02cd..9713557f8ba 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.5.2/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.5.2/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.6.0/getting-started-helm.md
index 8cf9c4e6946..be450cab178 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/getting-started-helm.md
@@ -397,7 +397,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.0/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.6.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.6.0/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.6.0/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.1/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.6.1/getting-started-helm.md
index 7bc1ceac11b..cb4c6945f20 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/getting-started-helm.md
@@ -402,7 +402,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.1/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.6.1/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.6.1/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.6.1/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.2/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.6.2/getting-started-helm.md
index 7bc1ceac11b..cb4c6945f20 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/getting-started-helm.md
@@ -402,7 +402,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.2/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.6.2/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.6.2/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.6.2/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.3/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.6.3/getting-started-helm.md
index 7bc1ceac11b..cb4c6945f20 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/getting-started-helm.md
@@ -402,7 +402,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.3/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.6.3/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.6.3/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.6.3/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.4/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.6.4/getting-started-helm.md
index e0b5e9a9340..406276c62cd 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/getting-started-helm.md
@@ -405,7 +405,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.6.4/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.6.4/helm-upgrade.md
index 3063efbe644..3ae1cdf2ba2 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.6.4/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.6.4/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.7.0/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.0/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.7.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.7.0/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.7.0/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.1/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.7.1/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.1/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.7.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.7.1/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.7.1/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.2/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.7.2/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.2/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.7.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.7.2/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.7.2/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.3/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.7.3/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.3/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.7.3/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.7.3/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.7.3/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.4/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.7.4/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.7.4/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.7.4/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.7.4/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.7.4/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.8.0/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.0/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.8.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.0/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.8.0/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.0/txn-why.md b/site2/website-next/versioned_docs/version-2.8.0/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.1/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.8.1/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.1/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.8.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.1/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.8.1/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.1/txn-why.md b/site2/website-next/versioned_docs/version-2.8.1/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.2/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.8.2/getting-started-helm.md
index b61c70deea6..65a9fc04fe5 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/getting-started-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.2/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.8.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.2/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.8.2/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.2/txn-why.md b/site2/website-next/versioned_docs/version-2.8.2/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.3/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.8.3/getting-started-helm.md
index 7919e3005e4..22ab38b5187 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.8.3/getting-started-helm.md
@@ -425,7 +425,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.8.3/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.8.3/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.8.3/txn-why.md b/site2/website-next/versioned_docs/version-2.8.3/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.8.3/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.9.0/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.9.0/getting-started-helm.md
index d11a69d67bd..98a3097d436 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/getting-started-helm.md
@@ -428,7 +428,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.0/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.9.0/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.9.0/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.9.0/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.0/txn-why.md b/site2/website-next/versioned_docs/version-2.9.0/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.9.1/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.9.1/getting-started-helm.md
index d11a69d67bd..98a3097d436 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/getting-started-helm.md
@@ -428,7 +428,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.1/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.9.1/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/helm-upgrade.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.9.1/kubernetes-helm.md b/site2/website-next/versioned_docs/version-2.9.1/kubernetes-helm.md
index 335e67e6d5a..a9f768e6a96 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/kubernetes-helm.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/kubernetes-helm.md
@@ -422,7 +422,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.1/txn-why.md b/site2/website-next/versioned_docs/version-2.9.1/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/txn-why.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.9.2/getting-started-helm.md b/site2/website-next/versioned_docs/version-2.9.2/getting-started-helm.md
index d11a69d67bd..98a3097d436 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/getting-started-helm.md
+++ b/site2/website-next/versioned_docs/version-2.9.2/getting-started-helm.md
@@ -428,7 +428,7 @@ Then you can proceed with the following steps:
- Type `http://pulsar-mini-broker:8080` for the field `Service URL` in the popup window.
- Click `Confirm` button in the popup window.
-4. After successfully created an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
+4. After successfully creating an environment, you are redirected to the `tenants` page of that environment. Then you can create `tenants`, `namespaces` and `topics` using the Pulsar Manager.
## Step 5: Use Prometheus and Grafana to monitor cluster
diff --git a/site2/website-next/versioned_docs/version-2.9.2/helm-upgrade.md b/site2/website-next/versioned_docs/version-2.9.2/helm-upgrade.md
index 1ebe4b46c30..e39cf974073 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/helm-upgrade.md
+++ b/site2/website-next/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:
diff --git a/site2/website-next/versioned_docs/version-2.9.2/txn-why.md b/site2/website-next/versioned_docs/version-2.9.2/txn-why.md
index 6420bdafef3..1ed87699776 100644
--- a/site2/website-next/versioned_docs/version-2.9.2/txn-why.md
+++ b/site2/website-next/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