diff --git a/faq.md b/faq.md
index 3dfa42b95e65a..190aee51a8f86 100644
--- a/faq.md
+++ b/faq.md
@@ -160,7 +160,7 @@ Once you reconnect, the subscription will still be there and it will be position
 ### I want some produce lock, i.e., to pessimistically or optimistically lock a specified topic so only one producer can write at a time and all further producers know they have to reprocess data before trying again to write a topic.
 To ensure only one producer is connected, you just need to use the same "producerName", the broker will ensure that no 2 producers with same name are publishing on a given topic.
 
-### I tested the performance using PerformanceProducer between two server node with 10,000Mbits NIC(and I tested tcp throughput can be larger than 1GB/s). I saw that the max msg throughput is around 1000,000 msg/s when using little msg_size(such as 64/128Bytes), when I increased the msg_size to 1028 or larger , then the msg/s will decreased sharply to 150,000msg/s, and both has max throughput around   1600Mbit/s, which is far from 1GB/s.  And I'm curious that the throughput between producer and broker why can't excess 1600Mbit/s ?  It seems that the Producer executor only use one thread, is this the reason？Then I start two producer client jvm, the throughput increased not much, just about little beyond 1600Mbit/s. Any other reasons?
+### I tested the performance using PerformanceProducer between two server node with 10,000Mbits NIC(and I tested tcp throughput can be larger than 1GB/s). I saw that the max msg throughput is around 1000,000 msg/s when using little msg_size(such as 64/128Bytes), when I increased the msg_size to 1028 or larger, then the msg/s will decreased sharply to 150,000msg/s, and both has max throughput around   1600Mbit/s, which is far from 1GB/s.  And I'm curious that the throughput between producer and broker why can't excess 1600Mbit/s ?  It seems that the Producer executor only use one thread, is this the reason？Then I start two producer client jvm, the throughput increased not much, just about little beyond 1600Mbit/s. Any other reasons?
 Most probably, when increasing the payload size, you're reaching the disk max write rate on a single bookie.
 
 There are few tricks that can be used to increase throughput (other than just partitioning)
diff --git a/site2/docs/client-libraries-dotnet.md b/site2/docs/client-libraries-dotnet.md
index ff56f163d54a5..2d14e15757940 100644
--- a/site2/docs/client-libraries-dotnet.md
+++ b/site2/docs/client-libraries-dotnet.md
@@ -8,7 +8,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/docs/deploy-aws.md b/site2/docs/deploy-aws.md
index d431a2bb81f66..d8d6d6ab844a2 100644
--- a/site2/docs/deploy-aws.md
+++ b/site2/docs/deploy-aws.md
@@ -175,7 +175,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/docs/developing-binary-protocol.md b/site2/website-next/docs/developing-binary-protocol.md
index d52a092416f9e..03eb78050a2ed 100644
--- a/site2/website-next/docs/developing-binary-protocol.md
+++ b/site2/website-next/docs/developing-binary-protocol.md
@@ -43,7 +43,7 @@ Payload commands have this basic structure:
 | `totalSize`                        | Required  | The size of the frame, counting everything that comes after it (in bytes)                   | 4               |
 | `commandSize`                      | Required  | The size of the protobuf-serialized command                                                 | 4               |
 | `message`                          | Required  | The protobuf message serialized in a raw binary format (rather than in protobuf format)     |                 |
-| `magicNumberOfBrokerEntryMetadata` | Optional  | A 2-byte byte array (`0x0e02`) identifying the broker entry metadata   <br /> **Note**: `magicNumberOfBrokerEntryMetadata` , `brokerEntryMetadataSize`, and `brokerEntryMetadata` should be used **together**.                     | 2               |
+| `magicNumberOfBrokerEntryMetadata` | Optional  | A 2-byte byte array (`0x0e02`) identifying the broker entry metadata   <br /> **Note**: `magicNumberOfBrokerEntryMetadata`, `brokerEntryMetadataSize`, and `brokerEntryMetadata` should be used **together**.                     | 2               |
 | `brokerEntryMetadataSize`          | Optional  | The size of the broker entry metadata                                                       | 4               |
 | `brokerEntryMetadata`              | Optional  | The broker entry metadata stored as a binary protobuf message                               |                 |
 | `magicNumber`                      | Required  | A 2-byte byte array (`0x0e01`) identifying the current format                               | 2               |
diff --git a/site2/website-next/versioned_docs/version-2.1.1-incubating/deploy-aws.md b/site2/website-next/versioned_docs/version-2.1.1-incubating/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.1.1-incubating/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.1.1-incubating/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.2.1/deploy-aws.md b/site2/website-next/versioned_docs/version-2.2.1/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.3.0/deploy-aws.md b/site2/website-next/versioned_docs/version-2.3.0/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.3.1/deploy-aws.md b/site2/website-next/versioned_docs/version-2.3.1/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.3.2/deploy-aws.md b/site2/website-next/versioned_docs/version-2.3.2/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.4.0/deploy-aws.md b/site2/website-next/versioned_docs/version-2.4.0/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.4.0/io-quickstart.md b/site2/website-next/versioned_docs/version-2.4.0/io-quickstart.md
index 10a03809e1749..acab1ebfe4321 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/io-quickstart.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/io-quickstart.md
@@ -522,7 +522,7 @@ Now that we have a MySQL running locally. In this section, we will configure a J
    
    To run a JDBC sink connector, you need to prepare a yaml config file including the information that Pulsar IO runtime needs to know. For example, how Pulsar IO can find the MySQL cluster, what is the JDBCURL and the table that Pulsar IO will use for writing messages to.
 
-   Create a _pulsar-mysql-jdbc-sink.yaml_ file , copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
+   Create a _pulsar-mysql-jdbc-sink.yaml_ file, copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
 
    ```text
    
diff --git a/site2/website-next/versioned_docs/version-2.4.1/deploy-aws.md b/site2/website-next/versioned_docs/version-2.4.1/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.4.1/io-quickstart.md b/site2/website-next/versioned_docs/version-2.4.1/io-quickstart.md
index 10a03809e1749..acab1ebfe4321 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/io-quickstart.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/io-quickstart.md
@@ -522,7 +522,7 @@ Now that we have a MySQL running locally. In this section, we will configure a J
    
    To run a JDBC sink connector, you need to prepare a yaml config file including the information that Pulsar IO runtime needs to know. For example, how Pulsar IO can find the MySQL cluster, what is the JDBCURL and the table that Pulsar IO will use for writing messages to.
 
-   Create a _pulsar-mysql-jdbc-sink.yaml_ file , copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
+   Create a _pulsar-mysql-jdbc-sink.yaml_ file, copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
 
    ```text
    
diff --git a/site2/website-next/versioned_docs/version-2.4.2/deploy-aws.md b/site2/website-next/versioned_docs/version-2.4.2/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.5.2/deploy-aws.md b/site2/website-next/versioned_docs/version-2.5.2/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.6.1/client-libraries-dotnet.md b/site2/website-next/versioned_docs/version-2.6.1/client-libraries-dotnet.md
index ade664cd95277..4e0afe3d2ff6b 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/client-libraries-dotnet.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website-next/versioned_docs/version-2.6.2/client-libraries-dotnet.md b/site2/website-next/versioned_docs/version-2.6.2/client-libraries-dotnet.md
index ade664cd95277..4e0afe3d2ff6b 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/client-libraries-dotnet.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website-next/versioned_docs/version-2.6.4/client-libraries-dotnet.md b/site2/website-next/versioned_docs/version-2.6.4/client-libraries-dotnet.md
index c35abb42f8927..e83d5a1ec550f 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/client-libraries-dotnet.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client to create Pulsar producers and consumers in C#.
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website-next/versioned_docs/version-2.6.4/deploy-aws.md b/site2/website-next/versioned_docs/version-2.6.4/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.7.0/deploy-aws.md b/site2/website-next/versioned_docs/version-2.7.0/deploy-aws.md
index d516144a8d1fb..09c0440e9164d 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/deploy-aws.md
@@ -214,7 +214,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website-next/versioned_docs/version-2.8.2/client-libraries-dotnet.md b/site2/website-next/versioned_docs/version-2.8.2/client-libraries-dotnet.md
index ade664cd95277..4e0afe3d2ff6b 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/client-libraries-dotnet.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website-next/versioned_docs/version-2.8.2/deploy-aws.md b/site2/website-next/versioned_docs/version-2.8.2/deploy-aws.md
index 7ae3bb0fbb8b7..6323051fde416 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/deploy-aws.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/deploy-aws.md
@@ -210,7 +210,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md b/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
index 404123bed8481..b7be9f6674ac5 100644
--- a/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
+++ b/site2/website/blog/2020-06-18-Apache-Pulsar-2-6-0.md
@@ -66,7 +66,7 @@ Consumer<byte[]> consumer = pulsarClient.newConsumer(Schema.BYTES)
         .build())
     .subscribe();
 
-consumer.reconsumeLater(message, 10 , TimeUnit.SECONDS);
+consumer.reconsumeLater(message, 10, TimeUnit.SECONDS);
 ```
 
 For more information about PIP-58, see [here](https://github.com/apache/pulsar/wiki/PIP-58-%3A-Support-Consumers--Set-Custom-Retry-Delay). <br> For more information about implementation details, see [PR-6449](https://github.com/apache/pulsar/pull/6449).
diff --git a/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md b/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md
index e74b4799442a6..3bf2f93bb78c1 100644
--- a/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md
+++ b/site2/website/blog/2020-11-09-Apache-Pulsar-2-6-2.md
@@ -42,7 +42,7 @@ Consumers using the `Key_Shared` subscription would encounter disorder messages
 2. Connect Producer and publish 500 messages with key `(i % 10)`
 3. Connect Consumer2 to same subscription and start to receive
   - receiverQueueSize: 1
-  - since https://github.com/apache/pulsar/pull/7106 , Consumer2 can't receive (expected)
+  - since https://github.com/apache/pulsar/pull/7106, Consumer2 can't receive (expected)
 4. Producer publish more 500 messages with same key generation algorithm
 5. After that, Consumer1 start to receive
 6. Check Consumer2 message ordering
diff --git a/site2/website/release-notes.md b/site2/website/release-notes.md
index dedcc1310f22b..849294e82066b 100644
--- a/site2/website/release-notes.md
+++ b/site2/website/release-notes.md
@@ -3372,7 +3372,7 @@ This is the second of Apache Pulsar since entering the ASF incubator.
 
 Major changes in this release include:
 
- * [#620](https://github.com/apache/incubator-pulsar/pull/620) [#717](https://github.com/apache/incubator-pulsar/pull/717) [#718](https://github.com/apache/incubator-pulsar/pull/718) Reader API support for C++ , Python & Websocket Proxy
+ * [#620](https://github.com/apache/incubator-pulsar/pull/620) [#717](https://github.com/apache/incubator-pulsar/pull/717) [#718](https://github.com/apache/incubator-pulsar/pull/718) Reader API support for C++, Python & Websocket Proxy
  * [#634](https://github.com/apache/incubator-pulsar/pull/634) Added [Message dispatch throttling](https://github.com/apache/incubator-pulsar/wiki/PIP-3:-Message-dispatch-throttling)
  * [#731](https://github.com/apache/incubator-pulsar/pull/731) Added [End to End Encryption](https://github.com/apache/incubator-pulsar/wiki/PIP-4:-Pulsar-End-to-End-Encryption)
  * [#732](https://github.com/apache/incubator-pulsar/pull/732) Support for [Event Time](https://github.com/apache/incubator-pulsar/wiki/PIP-5:-Event-time) for messages
diff --git a/site2/website/versioned_docs/version-2.4.0/io-quickstart.md b/site2/website/versioned_docs/version-2.4.0/io-quickstart.md
index 832c5bfd5d374..11bccc8f5b6ca 100644
--- a/site2/website/versioned_docs/version-2.4.0/io-quickstart.md
+++ b/site2/website/versioned_docs/version-2.4.0/io-quickstart.md
@@ -441,7 +441,7 @@ Now that we have a MySQL running locally. In this section, we will configure a J
    
     To run a JDBC sink connector, you need to prepare a yaml config file including the information that Pulsar IO runtime needs to know. For example, how Pulsar IO can find the MySQL cluster, what is the JDBCURL and the table that Pulsar IO will use for writing messages to.
 
-    Create a _pulsar-mysql-jdbc-sink.yaml_ file , copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
+    Create a _pulsar-mysql-jdbc-sink.yaml_ file, copy the following contents to this file, and place the file in the `pulsar/connectors` folder.
 
     ```text
     configs:
diff --git a/site2/website/versioned_docs/version-2.6.0/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.6.0/client-libraries-dotnet.md
index 544683bef84b1..6ee0331787a41 100644
--- a/site2/website/versioned_docs/version-2.6.0/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.6.0/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.6.2/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.6.2/client-libraries-dotnet.md
index b8ffb2a998875..8735d314a9efe 100644
--- a/site2/website/versioned_docs/version-2.6.2/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.6.2/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.7.0/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.7.0/client-libraries-dotnet.md
index c897936bd8952..f08816d81ced2 100644
--- a/site2/website/versioned_docs/version-2.7.0/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.7.0/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.7.0/deploy-aws.md b/site2/website/versioned_docs/version-2.7.0/deploy-aws.md
index 66b5836ba3a33..3b4d2c8db3f8c 100644
--- a/site2/website/versioned_docs/version-2.7.0/deploy-aws.md
+++ b/site2/website/versioned_docs/version-2.7.0/deploy-aws.md
@@ -176,7 +176,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/versioned_docs/version-2.7.2/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.7.2/client-libraries-dotnet.md
index d64245072503d..535d2c1221310 100644
--- a/site2/website/versioned_docs/version-2.7.2/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.7.2/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.7.2/deploy-aws.md b/site2/website/versioned_docs/version-2.7.2/deploy-aws.md
index 79ccf116e6f24..839addde614fc 100644
--- a/site2/website/versioned_docs/version-2.7.2/deploy-aws.md
+++ b/site2/website/versioned_docs/version-2.7.2/deploy-aws.md
@@ -176,7 +176,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/versioned_docs/version-2.7.3/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.7.3/client-libraries-dotnet.md
index a2306bdc500d6..4457d306ceb9b 100644
--- a/site2/website/versioned_docs/version-2.7.3/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.7.3/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.7.3/deploy-aws.md b/site2/website/versioned_docs/version-2.7.3/deploy-aws.md
index 47e100f1a057e..421e809ca4fae 100644
--- a/site2/website/versioned_docs/version-2.7.3/deploy-aws.md
+++ b/site2/website/versioned_docs/version-2.7.3/deploy-aws.md
@@ -176,7 +176,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/versioned_docs/version-2.7.4/deploy-aws.md b/site2/website/versioned_docs/version-2.7.4/deploy-aws.md
index e256c68af1a52..f07e7b81393e9 100644
--- a/site2/website/versioned_docs/version-2.7.4/deploy-aws.md
+++ b/site2/website/versioned_docs/version-2.7.4/deploy-aws.md
@@ -176,7 +176,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/versioned_docs/version-2.8.2/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.8.2/client-libraries-dotnet.md
index b5af9439101da..5b49f99ac7f9f 100644
--- a/site2/website/versioned_docs/version-2.8.2/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.8.2/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites
 
diff --git a/site2/website/versioned_docs/version-2.8.2/deploy-aws.md b/site2/website/versioned_docs/version-2.8.2/deploy-aws.md
index cf7f1760b6150..0da6380f6ea6a 100644
--- a/site2/website/versioned_docs/version-2.8.2/deploy-aws.md
+++ b/site2/website/versioned_docs/version-2.8.2/deploy-aws.md
@@ -176,7 +176,7 @@ Remember to enter this command just only once. If you attempt to enter this comm
 
 Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. 
 
-(Optional) If you want to use any [built-in IO connectors](io-connectors.md) , edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
+(Optional) If you want to use any [built-in IO connectors](io-connectors.md), edit the `Download Pulsar IO packages` task in the `deploy-pulsar.yaml` file and uncomment the connectors you want to use. 
 
 To run the playbook, enter this command:
 
diff --git a/site2/website/versioned_docs/version-2.9.0/client-libraries-dotnet.md b/site2/website/versioned_docs/version-2.9.0/client-libraries-dotnet.md
index 0c387f2a5087e..068d2169b2c3b 100644
--- a/site2/website/versioned_docs/version-2.9.0/client-libraries-dotnet.md
+++ b/site2/website/versioned_docs/version-2.9.0/client-libraries-dotnet.md
@@ -9,7 +9,7 @@ You can use the Pulsar C# client (DotPulsar) to create Pulsar producers and cons
 
 ## Installation
 
-You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio , see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
+You can install the Pulsar C# client library either through the dotnet CLI or through the Visual Studio. This section describes how to install the Pulsar C# client library through the dotnet CLI. For information about how to install the Pulsar C# client library through the Visual Studio, see [here](https://docs.microsoft.com/en-us/visualstudio/mac/nuget-walkthrough?view=vsmac-2019).
 
 ### Prerequisites