Improve readme

Author: kzu

readme.md

@@ -1,6 +1,10 @@
 ![Icon](https://raw.githubusercontent.com/devlooped/dotnet-eventgrid/main/img/icon-32.png) dotnet-eventgrid
 ============
 
+[![Version](https://img.shields.io/nuget/v/dotnet-eventgrid.svg?color=royalblue)](https://www.nuget.org/packages/dotnet-eventgrid)
+[![Downloads](https://img.shields.io/nuget/dt/dotnet-eventgrid.svg?color=darkmagenta)](https://www.nuget.org/packages/dotnet-eventgrid)
+[![License](https://img.shields.io/github/license/devlooped/dotnet-eventgrid.svg?color=blue)](https://github.com/devlooped/dotnet-eventgrid/blob/main/LICENSE)
+
 An Azure Function app with an EventGrid-trigger function that forwards events 
 to an Azure SignalR service, and an accompanying `dotnet` global tool to 
 connect to it and receive the streaming events in real-time.
@@ -13,7 +17,7 @@ I find the [Azure EventGrid Viewer](https://github.com/Azure-Samples/azure-event
 quite lacking and stagnating, it's [just a sample after all](https://docs.microsoft.com/en-us/samples/azure-samples/azure-event-grid-viewer/azure-event-grid-viewer/).
 Also, I'm much more into [dotnet global tools](https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools) 
 than web pages, having created a bunch of others like [dotnet-vs](https://github.com/devlooped/dotnet-vs), 
-[guit](https://github.com/devlooped/guit), [dotnet-file](https://github.com/devlooped/dotnet-file) and 
+[guit](https://github.com/devlooped/guit), [dotnet-eventgrid](https://github.com/devlooped/dotnet-eventgrid) and 
 [dotnet-config](https://github.com/devlooped/dotnet-config) ¯\_(ツ)_/¯
 
 ## Install
@@ -31,6 +35,11 @@ dotnet tool update -g dotnet-eventgrid
 ```
 
 <!-- #tool -->
+
+This tool provides a real-time view of Azure EventGrid events, by connecting to an Azure SignalR 
+service through an Azure Function app. The function app is triggered by EventGrid events and forwards 
+them to the SignalR service, which the tool connects to and receives the events in real-time.
+
 ## Usage
 
 ```

src/EventGrid/readme.md

@@ -1,70 +1,3 @@
 <!-- include ../../readme.md#tool -->
-<!-- #tool -->
-## Usage
 
-```
-Usage: eventgrid [url] -[property]* +[property[=minimatch]]*
-      +all                    Render all properties
-      -property               Exclude a property
-      +property[=minimatch]   Include a property, optionally filtering
-                              with the given the minimatch expression.
-      jq=expression           When rendering event data containing JSON,
-                              apply the given JQ expression. Learn more at
-                              https://stedolan.github.io/jq/
-
-Examples:
-- Include all event properties, for topic ending in 'System'
-      eventgrid https://mygrid.com +all +topic=**/System
-
-- Exclude data property and filter for specific event types
-      eventgrid https://mygrid.com -data +eventType=Login
-
-- Filter using synthetized path property '{domain}/{topic}/{subject}/{eventType}'
-      eventgrid https://mygrid.com +path=MyApp/**/Login
-
-- Filter using synthetized path property for a specific event and user (subject)
-      eventgrid https://mygrid.com +path=MyApp/*/1bQUI/Login
-
-- Render sponsorship action, sponsorable login and sponsor login from GH webhook JSON event data:
-      eventgrid https://mygrid.com jq="{ action: .action, sponsorable: .sponsorship.sponsorable.login, sponsor: .sponsorship.sponsor.login }"
-```
-
-*eventgrid* also supports [.netconfig](https://dotnetconfig.org) for configuring 
-arguments:
-
-```gitconfig
-[eventgrid]
-    url = https://events.mygrid.com
-
-    # filters that events must pass to be rendered
-    filter = path=MyApp/**/Login
-    filter = eventType=*System*
-
-    # properties to include in the event rendering
-    include = EventType
-    include = Subject
-
-    # properties to exclude from event rendering
-    exclude = data
-
-    # apply jq when rendering JSON data payloads
-    jq = "{ action: .action, sponsor: .sponsorship.sponsor.login }"
-```
-
-The `url` is the address of your deployed function app, which can optionally 
-have an `?key=[access-key]` query string with the same value specified in the 
-Function App configuration settings with the name `AccessKey`. If present, it 
-will be used as a shared secret to authorize the SignalR stream connection. 
-It's passed as the `X-Authorization` custom header and checked by the function 
-during SignalR connection negotiation.
-
-Keep in mind that the built-in EventGrid format for `topic` is rather unwieldy: 
-`/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventGrid/domains/{domainName}/topics/{topicName}`. 
-For this reason, we also provide a synthetized `path` property with the much 
-simpler format `{domain}/{topic}/{subject}/{eventType}`, which makes filtering 
-with the [minimatch](https://github.com/isaacs/minimatch) format much more 
-convenient.
-
-<!-- #tool -->
-<!-- ../../readme.md#tool -->
 <!-- exclude -->`