diff --git a/COPYRIGHT.txt b/COPYRIGHT.txt
index d9364bb5c..0742a4df9 100644
--- a/COPYRIGHT.txt
+++ b/COPYRIGHT.txt
@@ -463,6 +463,7 @@ Thomas Deblock
 Thomas Prelle
 Thomas Thornton
 Tim Loes
+tisonkun
 Timo Roeseler
 Tin Nguyen
 Tom Bentley
diff --git a/README.md b/README.md
index 1f4025eb6..3dcd9aeba 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ English | [Chinese](README_ZH.md) | [Japanese](README_JA.md) | [Korean](README_K
 
 # Debezium
 
-Debezium is an open source project that provides a low latency data streaming platform for change data capture (CDC). You setup and configure Debezium to monitor your databases, and then your applications consume events for each row-level change made to the database. Only committed changes are visible, so your application doesn't have to worry about transactions or changes that are rolled back. Debezium provides a single model of all change events, so your application does not have to worry about the intricacies of each kind of database management system. Additionally, since Debezium records the history of data changes in durable, replicated logs, your application can be stopped and restarted at any time, and it will be able to consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely.
+Debezium is an open source project that provides a low latency data streaming platform for change data capture (CDC). You set up and configure Debezium to monitor your databases, and then your applications consume events for each row-level change made to the database. Only committed changes are visible, so your application doesn't have to worry about transactions or changes that are rolled back. Debezium provides a single model of all change events, so your application does not have to worry about the intricacies of each kind of database management system. Additionally, since Debezium records the history of data changes in durable, replicated logs, your application can be stopped and restarted at any time, and it will be able to consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely.
 
 Monitoring databases and being notified when data changes has always been complicated. Relational database triggers can be useful, but are specific to each database and often limited to updating state within the same database (not communicating with external processes). Some databases offer APIs or frameworks for monitoring changes, but there is no standard so each database's approach is different and requires a lot of knowledged and specialized code. It still is very challenging to ensure that all changes are seen and processed in the same order while minimally impacting the database.