fix heading levels in the readme and bump version

diff --git a/Cargo.lock b/Cargo.lock
index 01e4369b11430c7128b2d7c0e4407cdbdfc7114e..b4a31548fd23047e5f5e8920a7f949293fb4a6d0 100644 (file)
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -257,7 +257,7 @@ dependencies = [
 
 [[package]]
 name = "connect"
-version = "0.0.4"
+version = "0.0.5"
 dependencies = [
  "anyhow",
  "async-channel",

diff --git a/Cargo.toml b/Cargo.toml
index 55ce619e4f877bab55e7198da7d2980fa4f5fa30..c488d929936a4559faedbdc60b323c9068d1dd08 100644 (file)
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "connect"
-version = "0.0.4"
+version = "0.0.5"
 edition = "2018"
 authors = ["Sachandhan Ganesh <sachan.ganesh@gmail.com>"]
 description = "message queue abstraction over async network streams"

diff --git a/README.md b/README.md
index 4c6a834aa47454710b9ba9bfc9e4156b2bb4ceb1..aedb3e706397a952576dbe0c2e6568bc0b0e3f57 100644 (file)
--- a/README.md
+++ b/README.md
@@ -9,14 +9,14 @@ 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
+## 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
+## Examples
 Please use the [examples](https://github.com/sachanganesh/connect-rs/tree/main/examples)
 provided to help understand crate usage.