doc: update kernel README with new version number

docs/src/ostd/README.md

@@ -7,10 +7,10 @@
 > 子曰：
 > "从心所欲，不逾矩。"
 
-With Asterinas OSTD,
+With the Asterinas OSTD (Operating System Standard Library), 
 you don't have to learn the dark art of unsafe Rust programming
 and risk shooting yourself in the foot.
-You will be doing whatever your heart desired
+You will be doing whatever your heart desires,
 and be confident that your kernel will never crash
 or be hacked due to undefined behaviors,
 even if today marks your Day 1 as a Rust programmer.
@@ -58,28 +58,27 @@ by leveraging OSTD.
 Adopting a minimalist philosophy,
 OSTD has a small codebase.
 At its core lies the `ostd` crate,
-currently encompassing about 10K lines of code
----a figure that is even smaller than those of many microkernels.
+currently encompassing about 10K lines of code - a figure 
+that is even smaller than those of many microkernels.
 As OSTD evolves,
 its codebase will expand,
 albeit at a relatively slow rate
 in comparison to the OS services layered atop it.
 
-OSTD's efficiency is measurable
+The OSTD's efficiency is measurable
 through the performance metrics of its APIs
 and the system calls of Asterinas Kernel.
 No intrinsic limitations have been identified within Rust
 or the framekernel architecture
 that could hinder kernel performance.
 
-Soundness,
-unlike the other three requirements,
+Soundness, unlike the other three requirements,
 is not as easily quantified or proved.
 While formal verification stands as the gold standard,
 it requires considerable resources and time
 and is not an immediate priority.
 As a more pragmatic approach,
 we will explain why the high-level design is sound
-in the [soundness analysis]()
-and rely on the many eyes of the community
-to catch any potential flaws in the implementation.
+in the soundness analysis and rely on the many 
+eyes of the community to catch any potential flaws 
+in the implementation.