X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=README.md;h=bdf89a06bb217deda27914be5a16712d89083fd2;hb=8d06f2dbd79d29cd5492dfba04c89a9aeb827082;hp=41ce2a7a42db54ec8d5714ca52b5dd5669a65fb9;hpb=23116fec3d781003b9519de16777877a6020c17c;p=connect-rs.git

diff --git a/README.md b/README.md
index 41ce2a7..bdf89a0 100644
--- a/README.md
+++ b/README.md
@@ -8,8 +8,12 @@
 [docs-badge]: https://docs.rs/connect/badge.svg
 [docs-url]: https://docs.rs/connect
 
-This Rust crate provides a reliable, fault-tolerant, and brokerless message-queue abstraction over
-asynchronous network streams.
+This Rust crate provides a simple brokerless message-queue abstraction over asynchronous network
+streams.
+
+## Examples
+Please use the [example programs](https://github.com/sachanganesh/connect-rs/tree/main/examples)
+provided to help understand crate usage.
 
 ## Why?
 When building networked applications, developers shouldn't have to focus on repeatedly solving
@@ -17,18 +21,6 @@ the problem of reliable, fault-tolerant message delivery over byte-streams. By u
 queue abstraction, crate users can focus on core application logic and leave the low-level
 networking and message-queue guarantees to the abstraction.
 
-## Protobuf
-This crate relies on the use of [Protocol Buffers](https://developers.google.com/protocol-buffers)
-due to it being widely adopted and industry-proven. All messages are Protobuf messages that
-are packed into a Protobuf `Any` type and then sent over the wire. Message recipients must
-decide what Protobuf message type it is, and correspondingly unpack the `Any` into a particular
-message type.
-
-## Examples
-Please use the [examples](https://github.com/sachanganesh/connect-rs/tree/main/examples)
-provided to help understand crate usage.
-
-
 ## Feature Status
 
 | Feature                                             	| Status 	|