Improve package readme and description

Author: kzu

readme.md

@@ -1,7 +1,8 @@
 ![Icon](https://raw.githubusercontent.com/devlooped/WebSocketeer/main/assets/img/icon.png) WebSocketeer
 ============
 
-High-performance intuitive API for Azure Web PubSub protobuf subprotocol
+A thin, intuitive, idiomatic and high-performance API for 
+Azure Web PubSub [protobuf subprotocol](https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-protobuf-webpubsub-subprotocol).
 
 [![Version](https://img.shields.io/nuget/v/WebSocketeer.svg?color=royalblue)](https://www.nuget.org/packages/WebSocketeer)
 [![Downloads](https://img.shields.io/nuget/dt/WebSocketeer.svg?color=green)](https://www.nuget.org/packages/WebSocketeer)

src/WebSocketeer/WebSocketeer.csproj

@@ -5,7 +5,7 @@
     <RootNamespace>Devlooped.Net</RootNamespace>
     <PackageId>WebSocketeer</PackageId>
     <ImplicitUsings>true</ImplicitUsings>
-    <Description>High-performance intuitive API for Azure Web PubSub protobuf subprotocol</Description>
+    <Description>A thin, intuitive, idiomatic and high-performance layer for Azure Web PubSub protobuf subprotocol.</Description>
   </PropertyGroup>
 
   <ItemGroup>

src/readme.md

@@ -1,23 +1,5 @@
-Azure Web PubSub [protobuf subprotocol](https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-protobuf-webpubsub-subprotocol) 
-is super awesome and general purpose and I can see endless applications 
-for this new service from Azure. The message-based nature of its "API" is 
-not very intuitive or idiomatic for a dotnet developer though, I think. 
-
-I wanted to create a super thin layer on top that didn't incur unnecessary 
-allocations or buffer handling or extra threads, since that would detract 
-from the amazing work on performance that .NET 5 (and 6!) are bringing to 
-the table. I use the [best practices](https://docs.microsoft.com/en-us/aspnet/core/grpc/performance?view=aspnetcore-5.0#send-binary-payloads) 
-for sending binary payloads using low-level (and quite new!) protobuf 
-APIs for avoiding unnecessary buffer creation/handling.
-
-In order to also squeeze every bit of performance, this project uses the 
-protobuf subprotocol exclusively, even though there is support in the service 
-for [JSON](https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-json-webpubsub-subprotocol) 
-payloads.
-
-The actual binary payloads you send/receive can of course be decoded into 
-any format you need, including JSON if you just encode/decode it as UTF8 bytes.
-
+A thin, intuitive, idiomatic and high-performance API for 
+Azure Web PubSub [protobuf subprotocol](https://docs.microsoft.com/en-us/azure/azure-web-pubsub/reference-protobuf-webpubsub-subprotocol).
 
 # Usage