Minor typo fixes
Haven't made any more invasive changes
@@ -57,8 +57,8 @@ pickup the new storage nodes and start using them without rebalancing partitions
Pulsar mitigates this cost/size trade-off by providing Tiered Storage. Tiered Storage turns your Pulsar topics into real *infinite* streams,
by offloading older segments into a long term storage, such as AWS S3, GCS and HDFS, which is designed for storing cold data. To the end user,
-there is no perceivable difference between consuming streams whose data is tored in BookKeeper or in long term storage. All the underlying
-offloading mechanisms and metadata management are transprent to applications.
+there is no perceivable difference between consuming streams whose data is stored in BookKeeper or in long term storage. All the underlying
+offloading mechanisms and metadata management are transparent to applications.
Currently [S3](https://aws.amazon.com/s3/) is supported in 2.1. More offloaders (such as Google GCS, Azure Blobstore, and HDFS) are coming
in future releases.
@@ -67,16 +67,16 @@ If you are interested in this feature, you can checkout more details [here](cook
## Stateful Function
-The most challenging thing that stream processing engines facing is managing *state*. So does Pulsar Functions. As the goal for Pulsar Functions
-is to simplify developing stream native processing logic, we also want to provide an easiest way for Pulsar Functions to manage its state.
+The greatest challenge that stream processing engines face is managing *state*. So does Pulsar Functions. As the goal for Pulsar Functions
+is to simplify developing stream native processing logic, we also want to provide an easier way for Pulsar Functions to manage their state.
We introduced a set of [State API](/docs/functions-state/#api) for Pulsar Functions to store their state. It integrates with the table service
in Apache BookKeeper for storing the state.
-It is released as a developer preview feature in Pulsar Functions Java SDK. We would like to collect feedbacks to improve it in future releases.
+It is released as a developer preview feature in Pulsar Functions Java SDK. We would like to collect feedback to improve it in future releases.
## Schemas
-Pulsar 2.0 introduces the native support for schemas in Pulsar. It means you can declare how message data looks and have Pulsar enforce that
+Pulsar 2.0 introduces native support for schemas in Pulsar. It means you can declare how message data looks and have Pulsar enforce that
producers can only publish valid data on the topics. In 2.0, Pulsar only supports `String`, `bytes` and `JSON` schemas. We introduced the
support for [Avro](https://avro.apache.org/) and [Protobuf](https://developers.google.com/protocol-buffers/) in this release.
