update tracing

Author: miparnisari

README.md

@@ -16,7 +16,7 @@ Developers create a schema that models their permissions requirements and use a
 
 Examples in this repository include:
 
-- Schema
+- How to set up SpiceDB with tracing: see [tracing](./tracing)
 - CI/CD Workflows
 
 Have questions? Join our [Discord].

tracing/README.md

@@ -1,11 +1,11 @@
 # Description
 
-This docker compose sets up SpiceDB with an open-telemetry based stack for tracing (OTEL Collector, Tempo and Grafana).
+This docker compose sets up SpiceDB with an OTEL stack for tracing ([OTEL](https://opentelemetry.io/) Collector, [Tempo](https://grafana.com/docs/tempo/latest/) and [Grafana](https://grafana.com/)).
 This is for demonstration purposes and not meant to be used as a production observability setup.
 
-- SpiceDB is configured to send OTEL traces to an instance of the otel-collector
-- otel-collector exports traces to tempo, the latter acting as tracing backend
-- grafana is configured with tempo as datasource
+- SpiceDB is configured to send OTEL traces to an instance of the otel-collector.
+- otel-collector exports traces to Tempo, the latter acting as tracing backend.
+- Grafana is configured with Tempo as datasource.
 
 ## Usage
 
@@ -15,7 +15,7 @@ docker compose up
 
 Grafana will be available locally at http://localhost:3000 with Tempo set up as datasource for tracing.
 
-Issue some requests to spicedb so we can start collecting traces
+Issue some requests to SpiceDB using the [zed cli](https://github.com/authzed/zed) so we can generate some traces:
 
 ```bash
 zed context set example localhost:50051 foobar --insecure