Clarify "Emit a LogRecord" API (open-telemetry#3383)

We discussed in Log SIG today and the current was unclear since it could
be interpreted as API taking LogRecord as an input. This is not the
case. The effect of making this API call is to emit a LogRecord to the
pipeline, but the API does not take a LogRecord as an input. The input
parameters are described in a subsequent paragraph.

specification/logs/bridge-api.md

@@ -111,9 +111,7 @@ The `Logger` MUST provide functions to:
 
 #### Emit a LogRecord
 
-`LogRecord`s encapsulate the fields identified in the [`LogRecord`
-data model](data-model.md#log-and-event-record-definition) and are emitted to the processing pipeline using
-this API.
+The effect of calling this API is to emit a `LogRecord` to the processing pipeline.
 
 The API MUST accept the following parameters: