Clarify that ReadableLogRecord and ReadWriteLogRecord can be represented using a single type

CHANGELOG.md

@@ -20,6 +20,8 @@ release.
 
 - Refine description of Instrumentation Scope.
   ([#3855](https://github.com/open-telemetry/opentelemetry-specification/pull/3855))
+- Clarify that `ReadableLogRecord` and `ReadWriteLogRecord` can be represented using a single type.
+  ([#3898](https://github.com/open-telemetry/opentelemetry-specification/pull/3898))
 
 ### Events
 

specification/logs/sdk.md

@@ -129,8 +129,7 @@ the responsibility of the `LoggerProvider` instead.
 
 ## Additional LogRecord interfaces
 
-In addition to the [definition for LogRecord](data-model.md#log-and-event-record-definition), the
-following `LogRecord`-like interfaces are defined in the SDK:
+In this document we refer to `ReadableLogRecord` and `ReadWriteLogRecord`, defined as follows.
 
 ### ReadableLogRecord
 
@@ -150,7 +149,8 @@ the [transformation to non-OTLP formats](../common/mapping-to-non-otlp.md#droppe
 specification.
 
 Note: Typically this will be implemented with a new interface or (immutable)
-value type.
+value type. The SDK may also use a single type to represent both `ReadableLogRecord`
+and `ReadWriteLogRecord`.
 
 ### ReadWriteLogRecord