Event payload lives in the LogRecord body

docs/general/events.md

@@ -3,13 +3,34 @@ linkTitle: Events
 aliases: [docs/specs/semconv/general/events-general]
 --->
 
-# Semantic Conventions for Event Attributes
+# Semantic Conventions for Events
 
 **Status**: [Experimental][DocumentStatus]
 
-This document describes the attributes of standalone Events that are represented
+This document describes the characteristics of standalone Events that are represented
 in the data model by `LogRecord`s.
 
+Semantically, an Event is a named occurrence at an instant in time. It simply signals that
+"this thing happened at this time" and provides additional specifics about the occurrence.
+Examples of Events might include things like uncaught exceptions, button clicks, user logout,
+network connection severed, etc.
+
+In OpenTelemetry, Events are implemented as a specific type of `LogRecord` that conforms to
+the conventions included here, and Events
+[have their own api](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/event-api.md).
+The api abstracts away knowledge of `LogRecord` so that users are merely dealing with Event
+semantics.
+
+In addition to a required name, an Event may contain a _payload_, which can be either structured or unstructured.
+In its implementation, the Event _payload_ will constitute the `Body` of the `LogRecord`.
+Like all other OpenTelemetry signals, an Event has optional attribute metadata that helps describe
+the event context.
+
+Over time, some Events will be specified by OpenTelemetry and will have documented payload structure,
+field semantics, and stability and requirement levels. Other events may be user-defined and carry
+bespoke user semantics. The name of the Event determines if an established payload structure is applicable
+or not.
+
 The following semantic conventions for events are defined:
 
 * **[General](#general-event-attributes): General semantic attributes that may be used in describing Events.**
@@ -18,8 +39,8 @@ The following semantic conventions for events are defined:
 ## General event attributes
 
 Events are recorded as LogRecords that are shaped in a special way: Event
-LogRecords have the attribute `event.name` that uniquely identifies the event.
-Events with same `event.name` are structurally similar to one another. Events
+LogRecords MUST have the attribute `event.name` that uniquely identifies the event.
+Events with the same `event.name` are structurally similar to one another. Events
 may also have other LogRecord attributes.
 
 When recording events from an existing system as OpenTelemetry Events, it is