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/08/29 06:21:41 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#ac640d9)
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 b000ff6aea0 Docs sync done from apache/pulsar(#ac640d9)
b000ff6aea0 is described below
commit b000ff6aea0a27bce48f55c2d16a1caa9799d35d
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Mon Aug 29 06:21:35 2022 +0000
Docs sync done from apache/pulsar(#ac640d9)
---
site2/website-next/docs/client-libraries-cpp.md | 16 +++++----------
site2/website-next/docs/client-libraries-dotnet.md | 22 ++++++++++++++++++++
site2/website-next/docs/client-libraries-go.md | 22 ++++----------------
site2/website-next/docs/client-libraries-java.md | 20 +++---------------
site2/website-next/docs/client-libraries-node.md | 15 +++++---------
site2/website-next/docs/client-libraries-python.md | 24 ++++++++++++++++++++--
.../docs/getting-started-standalone.md | 2 +-
site2/website-next/docs/reference-configuration.md | 12 ++---------
site2/website-next/docs/standalone.md | 2 +-
site2/website-next/sidebars.json | 20 +-----------------
.../static/swagger/restApiVersions.json | 8 ++++----
.../getting-started-standalone.md | 2 +-
.../version-2.10.0-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.10.1-deprecated/standalone.md | 2 +-
.../version-2.10.x/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.10.x/standalone.md | 2 +-
.../version-2.3.2/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.3.2/standalone.md | 2 +-
.../version-2.4.0/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.4.0/standalone.md | 2 +-
.../version-2.4.1/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.4.1/standalone.md | 2 +-
.../version-2.4.2/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.4.2/standalone.md | 2 +-
.../version-2.5.0/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.5.0/standalone.md | 2 +-
.../version-2.5.1/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.5.1/standalone.md | 2 +-
.../version-2.5.2/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.5.2/standalone.md | 2 +-
.../version-2.6.0/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.6.0/standalone.md | 2 +-
.../version-2.6.1/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.6.1/standalone.md | 2 +-
.../version-2.6.2/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.6.2/standalone.md | 2 +-
.../version-2.6.3/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.6.3/standalone.md | 2 +-
.../version-2.6.4/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.6.4/standalone.md | 2 +-
.../version-2.7.0/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.7.0/standalone.md | 2 +-
.../version-2.7.1/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.7.1/standalone.md | 2 +-
.../version-2.7.2/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.7.2/standalone.md | 2 +-
.../version-2.7.3/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.7.3/standalone.md | 2 +-
.../version-2.7.4/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.7.4/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.8.0-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.8.1-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.8.2-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.8.3-deprecated/standalone.md | 2 +-
.../version-2.8.x/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.8.x/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.9.0-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.9.1-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.9.2-deprecated/standalone.md | 2 +-
.../getting-started-standalone.md | 2 +-
.../version-2.9.3-deprecated/standalone.md | 2 +-
.../version-2.9.x/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.9.x/standalone.md | 2 +-
71 files changed, 130 insertions(+), 153 deletions(-)
diff --git a/site2/website-next/docs/client-libraries-cpp.md b/site2/website-next/docs/client-libraries-cpp.md
index 235af0804bf..c4dcafe43a7 100644
--- a/site2/website-next/docs/client-libraries-cpp.md
+++ b/site2/website-next/docs/client-libraries-cpp.md
@@ -341,30 +341,24 @@ ${PULSAR_HOME}/pulsar-client-cpp/build/lib/Release/pulsar.dll
## Connection URLs
-To connect Pulsar using client libraries, you need to specify a Pulsar protocol URL.
+To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
-Pulsar protocol URLs are assigned to specific clusters, you can use the Pulsar URI scheme. The default port is `6650`. The following is an example for localhost.
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
```http
-
pulsar://localhost:6650
-
```
-In a Pulsar cluster in production, the URL looks as follows.
+If you have multiple brokers, separate `IP:port` by commas:
```http
-
-pulsar://pulsar.us-west.example.com:6650
-
+pulsar://localhost:6550,localhost:6651,localhost:6652
```
-If you use TLS authentication, you need to add `ssl`, and the default port is `6651`. The following is an example.
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
```http
-
pulsar+ssl://pulsar.us-west.example.com:6651
-
```
## Create a producer
diff --git a/site2/website-next/docs/client-libraries-dotnet.md b/site2/website-next/docs/client-libraries-dotnet.md
index d8c3ad5b4b6..a0e4f89629c 100644
--- a/site2/website-next/docs/client-libraries-dotnet.md
+++ b/site2/website-next/docs/client-libraries-dotnet.md
@@ -54,6 +54,28 @@ To install the Pulsar C# client library, following these steps:
```
+## Connection URLs
+
+To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
+
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
+
+```http
+pulsar://localhost:6650
+```
+
+If you have multiple brokers, separate `IP:port` by commas:
+
+```http
+pulsar://localhost:6550,localhost:6651,localhost:6652
+```
+
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
+
+```http
+pulsar+ssl://pulsar.us-west.example.com:6651
+```
+
## Client
This section describes some configuration examples for the Pulsar C# client.
diff --git a/site2/website-next/docs/client-libraries-go.md b/site2/website-next/docs/client-libraries-go.md
index 4f64ea8f6e0..f9e74dcdf06 100644
--- a/site2/website-next/docs/client-libraries-go.md
+++ b/site2/website-next/docs/client-libraries-go.md
@@ -53,36 +53,22 @@ $ ./test_example
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
-Pulsar protocol URLs are assigned to specific clusters, use the `pulsar` scheme and have a default port of 6650. Here's an example for `localhost`:
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
```http
-
pulsar://localhost:6650
-
-```
-
-If you have multiple brokers, you can set the URL as below.
-
-```
-
-pulsar://localhost:6550,localhost:6651,localhost:6652
-
```
-A URL for a production Pulsar cluster may look something like this:
+If you have multiple brokers, separate `IP:port` by commas:
```http
-
-pulsar://pulsar.us-west.example.com:6650
-
+pulsar://localhost:6550,localhost:6651,localhost:6652
```
-If you're using [TLS](security-tls-authentication.md) authentication, the URL will look like something like this:
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
```http
-
pulsar+ssl://pulsar.us-west.example.com:6651
-
```
## Create a client
diff --git a/site2/website-next/docs/client-libraries-java.md b/site2/website-next/docs/client-libraries-java.md
index 26f9f784200..e4978f01037 100644
--- a/site2/website-next/docs/client-libraries-java.md
+++ b/site2/website-next/docs/client-libraries-java.md
@@ -71,36 +71,22 @@ dependencies {
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
-You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The default port is `6650`. The following is an example of `localhost`.
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
```http
-
pulsar://localhost:6650
-
```
-If you have multiple brokers, the URL is as follows.
+If you have multiple brokers, separate `IP:port` by commas:
```http
-
pulsar://localhost:6550,localhost:6651,localhost:6652
-
-```
-
-A URL for a production Pulsar cluster is as follows.
-
-```http
-
-pulsar://pulsar.us-west.example.com:6650
-
```
-If you use [TLS](security-tls-authentication.md) authentication, the URL is as follows.
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
```http
-
pulsar+ssl://pulsar.us-west.example.com:6651
-
```
## Client
diff --git a/site2/website-next/docs/client-libraries-node.md b/site2/website-next/docs/client-libraries-node.md
index f67c46b390a..ab2df8a6331 100644
--- a/site2/website-next/docs/client-libraries-node.md
+++ b/site2/website-next/docs/client-libraries-node.md
@@ -47,30 +47,25 @@ Also, this library works only in Node.js 10.x or later because it uses the [`nod
:::
## Connection URLs
+
To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
-Pulsar protocol URLs are assigned to specific clusters, use the `pulsar` scheme and have a default port of 6650. Here is an example for `localhost`:
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
```http
-
pulsar://localhost:6650
-
```
-A URL for a production Pulsar cluster may look something like this:
+If you have multiple brokers, separate `IP:port` by commas:
```http
-
-pulsar://pulsar.us-west.example.com:6650
-
+pulsar://localhost:6550,localhost:6651,localhost:6652
```
-If you are using [TLS encryption](security-tls-transport.md) or [TLS Authentication](security-tls-authentication.md), the URL looks like this:
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
```http
-
pulsar+ssl://pulsar.us-west.example.com:6651
-
```
## Create a client
diff --git a/site2/website-next/docs/client-libraries-python.md b/site2/website-next/docs/client-libraries-python.md
index e5b11345de2..bbfd91625f4 100644
--- a/site2/website-next/docs/client-libraries-python.md
+++ b/site2/website-next/docs/client-libraries-python.md
@@ -25,9 +25,7 @@ You can install the [`pulsar-client`](https://pypi.python.org/pypi/pulsar-client
To install the `pulsar-client` library as a pre-built package using the [pip](https://pip.pypa.io/en/stable/) package manager:
```shell
-
$ pip install pulsar-client==@pulsar:version_number@
-
```
### Optional dependencies
@@ -64,6 +62,28 @@ $ cd pulsar/pulsar-client-cpp/python
$ sudo python setup.py install
```
+## Connection URLs
+
+To connect to Pulsar using client libraries, you need to specify a [Pulsar protocol](developing-binary-protocol.md) URL.
+
+You can assign Pulsar protocol URLs to specific clusters and use the `pulsar` scheme. The following is an example of `localhost` with the default port `6650`:
+
+```http
+pulsar://localhost:6650
+```
+
+If you have multiple brokers, separate `IP:port` by commas:
+
+```http
+pulsar://localhost:6550,localhost:6651,localhost:6652
+```
+
+If you use [TLS](security-tls-authentication.md) authentication, add `+ssl` in the scheme:
+
+```http
+pulsar+ssl://pulsar.us-west.example.com:6651
+```
+
## API Reference
The complete Python API reference is available at [api/python](/api/python).
diff --git a/site2/website-next/docs/getting-started-standalone.md b/site2/website-next/docs/getting-started-standalone.md
index cf90e1a4e1c..31b80a8a33e 100644
--- a/site2/website-next/docs/getting-started-standalone.md
+++ b/site2/website-next/docs/getting-started-standalone.md
@@ -277,7 +277,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message on a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/docs/reference-configuration.md b/site2/website-next/docs/reference-configuration.md
index 7b082fcbf56..402a446831a 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -4,14 +4,6 @@ title: Pulsar configuration
sidebar_label: "Pulsar configuration"
---
-You can manage Pulsar configuration by configuration files in the [`conf`](https://github.com/apache/pulsar/tree/master/conf) directory of a Pulsar [installation](getting-started-standalone.md).
+You can manage Pulsar configuration by configuration files in the [`conf`](https://github.com/apache/pulsar/tree/master/conf) directory of a Pulsar [installation](https://pulsar.apache.org/docs/next/getting-started-standalone).
-- [BookKeeper](./reference-configuration-bookkeeper.md)
-- [Broker](./reference-configuration-broker.md)
-- [Client](./reference-configuration-client.md)
-- [Log4j](./reference-configuration-log4j.md)
-- [Log4j shell](./reference-configuration-log4j-shell.md)
-- [Standalone](./reference-configuration-standalone.md)
-- [WebSocket](./reference-configuration-websocket.md)
-- [Pulsar proxy](./reference-configuration-pulsar-proxy.md)
-- [ZooKeeper](./reference-configuration-zookeeper.md)
\ No newline at end of file
+For a full list of the configuration of different components, see [Pulsar Reference](https://pulsar.apache.org/reference).
diff --git a/site2/website-next/docs/standalone.md b/site2/website-next/docs/standalone.md
index e68dc1c04c9..3fb9d4f0af1 100644
--- a/site2/website-next/docs/standalone.md
+++ b/site2/website-next/docs/standalone.md
@@ -232,7 +232,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/sidebars.json b/site2/website-next/sidebars.json
index 70df7fb4024..7c51ae83678 100644
--- a/site2/website-next/sidebars.json
+++ b/site2/website-next/sidebars.json
@@ -341,25 +341,7 @@
"items": [
"reference-terminology",
"reference-cli-tools",
- {
- "type": "category",
- "label": "Pulsar Configuration",
- "link": {
- "type": "doc",
- "id": "reference-configuration"
- },
- "items": [
- "reference-configuration-bookkeeper",
- "reference-configuration-broker",
- "reference-configuration-client",
- "reference-configuration-log4j",
- "reference-configuration-log4j-shell",
- "reference-configuration-standalone",
- "reference-configuration-websocket",
- "reference-configuration-pulsar-proxy",
- "reference-configuration-zookeeper"
- ]
- },
+ "reference-configuration",
"reference-metrics",
"reference-rest-api-overview"
]
diff --git a/site2/website-next/static/swagger/restApiVersions.json b/site2/website-next/static/swagger/restApiVersions.json
index 8d35bd4d0b0..fd6c61bd8fb 100644
--- a/site2/website-next/static/swagger/restApiVersions.json
+++ b/site2/website-next/static/swagger/restApiVersions.json
@@ -193,7 +193,7 @@
]
}
],
- "2.6.1": [
+ "2.6.2": [
{
"version": "v2",
"fileName": [
@@ -209,7 +209,7 @@
]
}
],
- "2.6.2": [
+ "2.6.1": [
{
"version": "v2",
"fileName": [
@@ -225,7 +225,7 @@
]
}
],
- "2.7.0": [
+ "2.7.1": [
{
"version": "v2",
"fileName": [
@@ -241,7 +241,7 @@
]
}
],
- "2.7.1": [
+ "2.7.0": [
{
"version": "v2",
"fileName": [
diff --git a/site2/website-next/versioned_docs/version-2.10.0-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.10.0-deprecated/getting-started-standalone.md
index f3688c496d5..c60ba7e5ced 100644
--- a/site2/website-next/versioned_docs/version-2.10.0-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.0-deprecated/getting-started-standalone.md
@@ -291,7 +291,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.10.0-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.10.0-deprecated/standalone.md
index 0a10f3ae213..3d463d63555 100644
--- a/site2/website-next/versioned_docs/version-2.10.0-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.0-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.10.1-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.10.1-deprecated/getting-started-standalone.md
index f3688c496d5..c60ba7e5ced 100644
--- a/site2/website-next/versioned_docs/version-2.10.1-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.1-deprecated/getting-started-standalone.md
@@ -291,7 +291,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.10.1-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.10.1-deprecated/standalone.md
index 0a10f3ae213..3d463d63555 100644
--- a/site2/website-next/versioned_docs/version-2.10.1-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.1-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.10.x/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.10.x/getting-started-standalone.md
index f3688c496d5..c60ba7e5ced 100644
--- a/site2/website-next/versioned_docs/version-2.10.x/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.x/getting-started-standalone.md
@@ -291,7 +291,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.10.x/standalone.md b/site2/website-next/versioned_docs/version-2.10.x/standalone.md
index 0a10f3ae213..3d463d63555 100644
--- a/site2/website-next/versioned_docs/version-2.10.x/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.10.x/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.3.2/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.3.2/getting-started-standalone.md
index 36a36150ca9..1994800630b 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/getting-started-standalone.md
@@ -222,7 +222,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.3.2/standalone.md b/site2/website-next/versioned_docs/version-2.3.2/standalone.md
index 71b977366ec..c05b94a5aeb 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/standalone.md
@@ -222,7 +222,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.0/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.4.0/getting-started-standalone.md
index 13ac662b6ba..28b04bcc192 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/getting-started-standalone.md
@@ -222,7 +222,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.0/standalone.md b/site2/website-next/versioned_docs/version-2.4.0/standalone.md
index 705f31eb76a..16f3f2c6b79 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/standalone.md
@@ -222,7 +222,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.1/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.4.1/getting-started-standalone.md
index b517e118dff..3b4f8b065ab 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.1/standalone.md b/site2/website-next/versioned_docs/version-2.4.1/standalone.md
index 24ab7c9b78a..fb510051b17 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.2/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.4.2/getting-started-standalone.md
index 13619ef4865..5d6cc59ca50 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/getting-started-standalone.md
@@ -231,7 +231,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.2/standalone.md b/site2/website-next/versioned_docs/version-2.4.2/standalone.md
index 970c2f1cab9..6de554859a6 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/standalone.md
@@ -231,7 +231,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.0/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.5.0/getting-started-standalone.md
index b517e118dff..3b4f8b065ab 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.0/standalone.md b/site2/website-next/versioned_docs/version-2.5.0/standalone.md
index 24ab7c9b78a..fb510051b17 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.1/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.5.1/getting-started-standalone.md
index 5ffb6424f00..95782fc6ca8 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.1/standalone.md b/site2/website-next/versioned_docs/version-2.5.1/standalone.md
index 21a9111c9df..2ff2d6059a2 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.2/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.5.2/getting-started-standalone.md
index d8c67f9c1be..b8fe606a581 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.2/standalone.md b/site2/website-next/versioned_docs/version-2.5.2/standalone.md
index 9e5d8dc571c..233394260c0 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/standalone.md
@@ -232,7 +232,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.0/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.6.0/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.0/standalone.md b/site2/website-next/versioned_docs/version-2.6.0/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.1/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.6.1/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.1/standalone.md b/site2/website-next/versioned_docs/version-2.6.1/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.2/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.6.2/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.2/standalone.md b/site2/website-next/versioned_docs/version-2.6.2/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.3/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.6.3/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.3/standalone.md b/site2/website-next/versioned_docs/version-2.6.3/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.4/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.6.4/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.4/standalone.md b/site2/website-next/versioned_docs/version-2.6.4/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.0/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.7.0/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.0/standalone.md b/site2/website-next/versioned_docs/version-2.7.0/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.1/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.7.1/getting-started-standalone.md
index 0db73dda6aa..dad19d422f3 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.1/standalone.md b/site2/website-next/versioned_docs/version-2.7.1/standalone.md
index 3563964ffd1..220af52ce68 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.2/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.7.2/getting-started-standalone.md
index 5ffb6424f00..95782fc6ca8 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.2/standalone.md b/site2/website-next/versioned_docs/version-2.7.2/standalone.md
index 21a9111c9df..2ff2d6059a2 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.3/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.7.3/getting-started-standalone.md
index 8a5cd8e92f0..4dfcf27b54e 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.3/standalone.md b/site2/website-next/versioned_docs/version-2.7.3/standalone.md
index 53d59c1fedd..d8dd985f30d 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.4/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.7.4/getting-started-standalone.md
index 8a5cd8e92f0..4dfcf27b54e 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/getting-started-standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.4/standalone.md b/site2/website-next/versioned_docs/version-2.7.4/standalone.md
index 53d59c1fedd..d8dd985f30d 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/standalone.md
@@ -230,7 +230,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.0-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.8.0-deprecated/getting-started-standalone.md
index c9475dd1c94..0e40286d71d 100644
--- a/site2/website-next/versioned_docs/version-2.8.0-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.0-deprecated/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.0-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.8.0-deprecated/standalone.md
index cdb53d88a5f..d114c017d7c 100644
--- a/site2/website-next/versioned_docs/version-2.8.0-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.0-deprecated/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.1-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.8.1-deprecated/getting-started-standalone.md
index c9475dd1c94..0e40286d71d 100644
--- a/site2/website-next/versioned_docs/version-2.8.1-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.1-deprecated/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.1-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.8.1-deprecated/standalone.md
index cdb53d88a5f..d114c017d7c 100644
--- a/site2/website-next/versioned_docs/version-2.8.1-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.1-deprecated/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.2-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.8.2-deprecated/getting-started-standalone.md
index c9475dd1c94..0e40286d71d 100644
--- a/site2/website-next/versioned_docs/version-2.8.2-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.2-deprecated/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.2-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.8.2-deprecated/standalone.md
index cdb53d88a5f..d114c017d7c 100644
--- a/site2/website-next/versioned_docs/version-2.8.2-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.2-deprecated/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.3-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.8.3-deprecated/getting-started-standalone.md
index c9475dd1c94..0e40286d71d 100644
--- a/site2/website-next/versioned_docs/version-2.8.3-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.3-deprecated/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.3-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.8.3-deprecated/standalone.md
index cdb53d88a5f..d114c017d7c 100644
--- a/site2/website-next/versioned_docs/version-2.8.3-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.3-deprecated/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.x/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.8.x/getting-started-standalone.md
index fd7a6f24995..cea47efd08d 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/getting-started-standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.x/standalone.md b/site2/website-next/versioned_docs/version-2.8.x/standalone.md
index e06d49c591f..25afa11a91b 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/standalone.md
@@ -236,7 +236,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.0-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.9.0-deprecated/getting-started-standalone.md
index 712b2fd2146..436355aa832 100644
--- a/site2/website-next/versioned_docs/version-2.9.0-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.0-deprecated/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.0-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.9.0-deprecated/standalone.md
index 21c5be422d0..32970bfcfe2 100644
--- a/site2/website-next/versioned_docs/version-2.9.0-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.0-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.1-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.9.1-deprecated/getting-started-standalone.md
index 712b2fd2146..436355aa832 100644
--- a/site2/website-next/versioned_docs/version-2.9.1-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.1-deprecated/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.1-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.9.1-deprecated/standalone.md
index 21c5be422d0..32970bfcfe2 100644
--- a/site2/website-next/versioned_docs/version-2.9.1-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.1-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.2-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.9.2-deprecated/getting-started-standalone.md
index ffc80807d73..90e3f820e74 100644
--- a/site2/website-next/versioned_docs/version-2.9.2-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.2-deprecated/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.2-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.9.2-deprecated/standalone.md
index 98a8d911a64..798ba379d2d 100644
--- a/site2/website-next/versioned_docs/version-2.9.2-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.2-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.3-deprecated/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.9.3-deprecated/getting-started-standalone.md
index ffc80807d73..90e3f820e74 100644
--- a/site2/website-next/versioned_docs/version-2.9.3-deprecated/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.3-deprecated/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.3-deprecated/standalone.md b/site2/website-next/versioned_docs/version-2.9.3-deprecated/standalone.md
index 98a8d911a64..798ba379d2d 100644
--- a/site2/website-next/versioned_docs/version-2.9.3-deprecated/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.3-deprecated/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.x/getting-started-standalone.md b/site2/website-next/versioned_docs/version-2.9.x/getting-started-standalone.md
index 8192f374300..9137ba29142 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/getting-started-standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/getting-started-standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.x/standalone.md b/site2/website-next/versioned_docs/version-2.9.x/standalone.md
index 6236f405140..9bff74d92c1 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/standalone.md
@@ -233,7 +233,7 @@ If the message has been successfully consumed, you will see a confirmation like
:::tip
-As you have noticed that we do not explicitly create the `my-topic` topic, to which we consume the message. When you consume a message to a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
+As you have noticed that we do not explicitly create the `my-topic` topic, from which we consume the message. When you consume a message from a topic that does not yet exist, Pulsar creates that topic for you automatically. Producing a message to a topic that does not exist will automatically create that topic for you as well.
:::