[fix][doc] Fix incorrect layout issues (apache#15525)

site2/docs/getting-started-docker.md

@@ -32,9 +32,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > **Tip**  
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.10.0/getting-started-docker.md

@@ -33,9 +33,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > **Tip**  
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.3.1/getting-started-docker.md

@@ -47,9 +47,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > #### Automatically created namespace
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 
 ## Start publishing and consuming messages

site2/website/versioned_docs/version-2.3.2/getting-started-docker.md

@@ -50,9 +50,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.5.0/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.5.1/standalone-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.6.0/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.6.1/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.6.2/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.6.3/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.6.4/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.7.0/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.7.1/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.7.2/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.7.3/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.7.4/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.8.0/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.8.1/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.8.2/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.8.3/getting-started-docker.md

@@ -40,9 +40,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 
 > #### Tip
 > 
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.9.0/getting-started-docker.md

@@ -32,9 +32,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > **Tip**  
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.9.1/getting-started-docker.md

@@ -32,9 +32,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > **Tip**  
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker
 

site2/website/versioned_docs/version-2.9.2/getting-started-docker.md

@@ -32,9 +32,7 @@ If you start Pulsar successfully, you will see `INFO`-level log messages like th
 ```
 
 > **Tip**  
-> When you start a local standalone cluster, a `public/default`
-namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces.
-For more information, see [Topics](concepts-messaging.md#topics).
+> When you start a local standalone cluster, a `public/default` namespace is created automatically. The namespace is used for development purposes. All Pulsar topics are managed within namespaces. For more information, see [Topics](concepts-messaging.md#topics).
 
 ## Use Pulsar in Docker