fix: apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: Berrysoft

content/docs/compio/buffers.md

@@ -4,7 +4,7 @@ Crate `compio-buf` is fundamental to `compio`. It provides abstractions for diff
 
 ## Buffer traits
 
-The trait `IoBuf` is the abstract of read-only buffers. Trait `IoBufMut` provides writing methods in addition, and supports extending the buffer. A write operation can only write into the allocated space, but cannot extend the vector automatically.
+The trait `IoBuf` is the abstract of read-only buffers. Trait `IoBufMut` provides writing methods in addition. It allows you to extend the buffer via explicit APIs, but I/O write operations themselves can only write into the already-allocated space and will not automatically grow the underlying vector.
 
 `IoBuf` & `IoBufMut` represent owned buffers. The IO operations always require the ownership of a buffer to avoid potential race conditions. Although the traits implement for arrays `[u8; N]`, it's not a good idea to use them as buffer type, because the move operation of them is relatively slow. Use `Vec<u8>` or `Box<[u8]>` instead.
 

content/docs/compio/driver.md

@@ -22,4 +22,4 @@ The `Proactor` provides a simple cancellation mechanism. The cancellation of an
 
 ## Shared FDs
 
-"File descriptors" in `compio` represents the file descriptors on Unix and handles on Windows. When the driver is holding the operations, it should also hold the reference of the related fds. Therefore, all fds are wrapped inside an `Rc`/`Arc`, depending on the feature `"sync"`. When a file or socket is cloned, the inner `Rc`/`Arc` is cloned, rather than duplicating (e.g., with `dup`) the fds or handles. When the method `close` is called on a file or socket, the future will wait for all related operations to complete. Therefore, it's not a good idea to close a cloned file or socket.
+"File descriptors" in `compio` represent the file descriptors on Unix and handles on Windows. When the driver is holding the operations, it should also hold the reference of the related fds. Therefore, all fds are wrapped inside an `Rc`/`Arc`, depending on the feature `"sync"`. When a file or socket is cloned, the inner `Rc`/`Arc` is cloned, rather than duplicating (e.g., with `dup`) the fds or handles. When the method `close` is called on a file or socket, the future will wait for all related operations to complete. Therefore, it's not a good idea to close a cloned file or socket.

content/docs/compio/net.md

@@ -1,5 +1,5 @@
 # Networking
 
-`compio-net` provides most networking affairs. TCP, UDP, Unix sockets are supported. The TLS support is in `compio-tls`, the QUIC support is in `compio-quic`, and the WebSocket support is in `compio-ws`. For high level HTTP support, see `cyper`.
+`compio-net` provides most networking affairs. TCP, UDP, Unix sockets are supported. The TLS support is in `compio-tls`, the QUIC support is in `compio-quic`, and the WebSocket support is in `compio-ws`. For high-level HTTP support, see `cyper`.
 
 Sockets in `compio` expose completion-based APIs. If it is too confusing to use, `PollFd` is provided for all kinds of socket resources, and exposes ready-based APIs.

content/docs/compio/net/sockets.md

@@ -24,4 +24,4 @@ Windows _does_ support Unix sockets, with some limitations. A Unix socket on Win
 
 ## Control messages of UDP sockets
 
-There are `send_msg*` and `recv_msg*` methods in `UdpSocket`. They retrieve ancillary data as raw buffers. The users are responsible to align the buffer correctly.
+There are `send_msg*` and `recv_msg*` methods in `UdpSocket`. They retrieve ancillary data as raw buffers. Users are responsible for aligning the buffer correctly.

content/docs/summary.ts

@@ -36,7 +36,7 @@ const compio: Section[] = [
   ['Signal', '/docs/compio/signal'],
   ['Process', '/docs/compio/process'],
   ['TLS', '/docs/compio/tls'],
-  ['WebSocket', "/docs/compio/ws"]
+  ['WebSocket', '/docs/compio/ws'],
   // [['QUIC', 'compio/quic'], [['HTTP 3', 'compio/quic/http3']]], // TODO(@AsakuraMizu): Write this
 ]