Update info in Cargo.toml and README.md

Signed-off-by: Quanyi Ma <[email protected]>

Cargo.toml

@@ -1,13 +1,25 @@
 [package]
 name = "dagrs"
-authors = ["Quanyi Ma <[email protected]>", "Zhilei Qiu <[email protected]>"]
-version = "0.3.0"
+authors = [
+    "Quanyi Ma <[email protected]>",
+    "Xiaolong Fu <[email protected]>",
+    "Zhilei Qiu <[email protected]>",
+]
+version = "0.4.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
-description = "The DAG engine, named dagrs, is designed to execute multiple tasks with graph-like dependencies. It offers high performance and asynchronous execution, providing a convenient programming interface for Rust developers."
+description = "Dagrs follows the concept of Flow-based Programming and is suitable for the execution of multiple tasks with graph-like dependencies. Dagrs has the characteristics of high performance and asynchronous execution. It provides users with a convenient programming interface."
 readme = "README.md"
-repository = "https://github.com/open-rust-initiative/dagrs"
-keywords = ["DAG", "task", "async", "parallel", "concurrent"]
+repository = "https://github.com/dagrs-dev/dagrs"
+keywords = [
+    "DAG",
+    "task",
+    "async",
+    "parallel",
+    "concurrent",
+    "tokio",
+    "flow-based-programming",
+]
 
 [workspace]
 members = [".", "derive"]

README.md

@@ -9,14 +9,14 @@ Dagrs follows the concept of Flow based Programming, and aims to provide users w
 
 ### Dagrs's role in your project
 
-When you orchestrate multitasking applications asynchronously, you can make them scale better by reducing the cost of performing multiple operations simultaneously. 
-However, writing correct asynchronous code and managing communication between different tasks is annoying. 
+When you orchestrate multitasking applications asynchronously, you can make them scale better by reducing the cost of performing multiple operations simultaneously.
+However, writing correct asynchronous code and managing communication between different tasks is annoying.
 Dagrs provides convenient task abstraction and asynchronous running & communication mechanisms to reduce development costs.
 
 The development of `dagrs` follows the concept of Flow-based Programming.
 
 ### Flow based Programming
-[Flow-based Programming](https://en.wikipedia.org/wiki/Flow-based_programming)(FBP) was invented by J. Paul Morrison in the early 1970s. It was initially implemented in software for a Canadian bank. 
+[Flow-based Programming](https://en.wikipedia.org/wiki/Flow-based_programming)(FBP) was invented by J. Paul Morrison in the early 1970s. It was initially implemented in software for a Canadian bank.
 Over the years, it’s had various names but has always maintained its core principles of reducing development time and managing processes efficiently.
 
 FBP treats applications as networks of 'black box' processes that communicate by sending and receiving data, referred to as Information Packets, over predefined connections. It’s a component-oriented approach that fits well with modular software architecture.
@@ -99,9 +99,8 @@ Freighter is licensed under this Licensed:
 
 ## Contact us
 
-QIUZHILEI email: [email protected]/QZL2503687@gmail.com
+Email: Quanyi Ma <[email protected]>, Xiaolong Fu <njufxl@gmail.com>
 
 ### Discord
 
 Welcome to join our discord channel https://discord.gg/4JzaNkRP
-