Apply suggestions from code review

Co-authored-by: Grace Cai <qqzczy@126.com>

ticdc/ticdc-avro-protocol.md

@@ -196,7 +196,7 @@ The following is a configuration example:
 cdc cli changefeed create --pd=http://127.0.0.1:2379 --changefeed-id="kafka-avro-enable-extension" --sink-uri="kafka://127.0.0.1:9092/topic-name?kafka-version=2.6.0&protocol=avro&avro-decimal-handling-mode=string&avro-bigint-unsigned-handling-mode=string" --schema-registry=http://127.0.0.1:8081
 ```
 
-Most SQL Types are mapped to the base Column data format. Some other SQL types extend the base data format to provide more information.
+Most SQL types are mapped to the base Column data format. Some other SQL types extend the base data format to provide more information.
 
 BIT(64)
 
@@ -251,7 +251,7 @@ Avro does not generate DDL events downstream. It checks whether a schema changes
 
 Note that, even if a schema change passes the compatibility check and a new version is registered, the data producers and consumers still need to perform an upgrade to ensure normal running of the system.
 
-Assume that the default compatibility policy of Confluent Schema Registry is `BACKWARD` and add a non-empty column to the source table. In this situation, Avro generates a new schema but fails to register it with Schema Registry due to compatibility issues. At this time, the changefeed enters error state.
+Assume that the default compatibility policy of Confluent Schema Registry is `BACKWARD` and add a non-empty column to the source table. In this situation, Avro generates a new schema but fails to register it with Schema Registry due to compatibility issues. At this time, the changefeed enters an error state.
 
 For more information about schemas, refer to [Schema Registry related documents](https://docs.confluent.io/platform/current/schema-registry/avro.html).