It's a distributed request tracing specification & set of libraries implementing the said spec
This is too often a mistake - not knowingly. It's like proof reading, I always think my writing is correct until someone else points out mistakes.
I just want to see what I'm getting into, not a vocabulary or jargon lesson, at least at first.
That would lead us to then wonder why it was done that way, etc... and drive interest.
But I didn't see (perhaps I missed it) about tracing inside a single instance where I want the individual method call to be traced to know which method call was expensive within that instance.
These can be local or cross-service.
I guess the documentation focusses on the "distributed" part of tracing but it works perfectly well for local spans too.
The readme says absolutely nothing (e.g. "The OpenTelemetry specification describes the cross-language requirements and expectations for all OpenTelemetry implementations." and goes on to describe how to submit changes or on which proprietary platform meeting minutes can be found) and the Overview document goes into depths about terminology (what a trace is, what a span within a trace is, how to link spans, etc.).
Nowhere does it say if this is supposed to, for example, replace proprietary crash reporting in apps so that we can know what is being reported back to the mothership, or if this is something completely different.