@@ -12,31 +12,33 @@ const (
1212 //
1313 // Use `ProductionLimit` to get the current data
1414 //
15- // Use Case LPC , Scenario 1
15+ // Use Case LPP , Scenario 1
1616 DataUpdateLimit api.EventType = "cs-lpp-DataUpdateLimit"
1717
1818 // An incoming load control obligation limit needs to be approved or denied
1919 //
20- // Use `PendingProductionLimits` to get the currently pending write approval requests
21- // and invoke `ApproveOrDenyProductionLimit` for each
20+ // Use `PendingProductionLimits` and `PendingDeviceConfigurations` to get
21+ // the currently pending write approval requests and invoke
22+ // `ApproveOrDenyProductionLimit` or `ApproveOrDenyDeviceConfiguration` for
23+ // each
2224 //
23- // Use Case LPC , Scenario 1
25+ // Use Case LPP , Scenario 1
2426 WriteApprovalRequired api.EventType = "cs-lpp-WriteApprovalRequired"
2527
2628 // Failsafe limit for the produced active (real) power of the
2729 // Controllable System data update received
2830 //
2931 // Use `FailsafeProductionActivePowerLimit` to get the current data
3032 //
31- // Use Case LPC , Scenario 2
33+ // Use Case LPP , Scenario 2
3234 DataUpdateFailsafeProductionActivePowerLimit api.EventType = "cs-lpp-DataUpdateFailsafeProductionActivePowerLimit"
3335
3436 // Minimum time the Controllable System remains in "failsafe state" unless conditions
3537 // specified in this Use Case permit leaving the "failsafe state" data update received
3638 //
3739 // Use `FailsafeDurationMinimum` to get the current data
3840 //
39- // Use Case LPC , Scenario 2
41+ // Use Case LPP , Scenario 2
4042 DataUpdateFailsafeDurationMinimum api.EventType = "cs-lpp-DataUpdateFailsafeDurationMinimum"
4143
4244 // Indicates a notify heartbeat event the application should care of.
0 commit comments