Update 4290-logger-enabled.md

oteps/logs/4290-logger-enabled.md

@@ -10,14 +10,15 @@ The consumers of OpenTelemetry clients want to:
 4. Filter out log and event records when they are not inside a recording span.
 5. Have fine-grained control of logging pipelines without using an OpenTelemetry Collector (e.g. mobile devices, serverless, IoT).
 6. Efficiently support high-performance logging destionation like user_events and ETW.
+7. Add sampling for logging.
 
 ## Explanation
 
 For (1) (2), the user can use the Logs API `Logger.Enabled` function, which tells the user wheteher a `Logger` for given arguments is going to emit a log record.
 
 For (3) (4), the user can declarativly configure the Logs SDK using `LoggerConfigurator` to set the `disabled`, `minimum_severity_level`, `disabled_not_recorded_spans` of a `LoggerConfig`.
 
-For (5) (6), the user can hook to `Logger.Enabled` Logs API calls by adding to the Logs SDK a `LogRecordProcessor` implementing `OnEnabled`.
+For (5) (6) (7), the user can hook to `Logger.Enabled` Logs API calls by adding to the Logs SDK a `LogRecordProcessor` implementing `OnEnabled`.
 
 ## Internal details