Update doc

algesten · Jul 14, 2024 · 5b85c21 · 5b85c21
1 parent d8fa0b5
commit 5b85c21
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -2,11 +2,10 @@
 
 <image src="https://user-images.githubusercontent.com/227204/226143511-66fe5264-6ab7-47b9-9551-90ba7e155b96.svg" alt="str0m logo" ></image>
 
-A synchronous sans I/O WebRTC implementation in Rust.
+A Sans I/O WebRTC implementation in Rust.
 
 This is a [Sans I/O][sansio] implementation meaning the `Rtc` instance itself is not doing any network
-talking. Furthermore it has no internal threads or async tasks. All operations are synchronously
-happening from the calls of the public API.
+talking. Furthermore it has no internal threads or async tasks. All operations are happening from the calls of the public API.
 
 This is deliberately not a standard `RTCPeerConnection` API since that isn't a great fit for Rust.
 See more details in below section.

diff --git a/src/lib.rs b/src/lib.rs
@@ -1,10 +1,10 @@
 //! <image src="https://user-images.githubusercontent.com/227204/226143511-66fe5264-6ab7-47b9-9551-90ba7e155b96.svg" alt="str0m logo" ></image>
 //!
-//! A synchronous sans I/O WebRTC implementation in Rust.
+//! A Sans I/O WebRTC implementation in Rust.
 //!
 //! This is a [Sans I/O][sansio] implementation meaning the `Rtc` instance itself is not doing any network
-//! talking. Furthermore it has no internal threads or async tasks. All operations are synchronously
-//! happening from the calls of the public API.
+//! talking. Furthermore it has no internal threads or async tasks. All operations are happening from the 
+//! calls of the public API.
 //!
 //! This is deliberately not a standard `RTCPeerConnection` API since that isn't a great fit for Rust.
 //! See more details in below section.