diff --git a/yang-models/_3gpp-common-subscription-control.yang b/yang-models/_3gpp-common-subscription-control.yang
index 7229d5648dbc00c17e2a8b9c512fb8a12535b93c..c04ccb3d5213e9a8fa77b39a15f8d0887f47abb9 100755
--- a/yang-models/_3gpp-common-subscription-control.yang
+++ b/yang-models/_3gpp-common-subscription-control.yang
@@ -16,6 +16,7 @@ module _3gpp-common-subscription-control {
       Solution Set (SS) definitions
       3GPP TS 28.623";
   
+  revision 2023-08-12 { reference "CR-0258"; }
   revision 2022-11-03 { reference CR-0192;   }
   revision 2021-01-16 { reference "CR-0120"; }  
   revision 2020-08-26 { reference "CR-0106"; }
@@ -172,9 +173,8 @@ module _3gpp-common-subscription-control {
       
       list HeartbeatControl {
         description "MnS consumers (i.e. notification recipients) use heartbeat
-          notifications to monitor the communication channels between them and
-          data reporting MnS producers emitting notifications such as
-          notifyNewAlarm and notifyFileReady.
+          notifications to monitor the communication channels between 
+          themselves and MnS producers configured to emit notifications.
 
           A HeartbeatControl instance allows controlling the emission of
           heartbeat notifications by MnS producers. The recipients of heartbeat
@@ -205,7 +205,7 @@ module _3gpp-common-subscription-control {
 
           Creation and deletion of HeartbeatControl instances by MnS Consumers
           is optional; when not supported, the HeartbeatControl instances may be
-          created and deleted by the system or be pre-installed.
+          created and deleted by the system or be pre-installed. 
 
           Whether and when to emit heartbeat notifications is controlled by
           HeartbeatControl. Subscription for heartbeat is not supported via the
@@ -221,4 +221,4 @@ module _3gpp-common-subscription-control {
       }
     }
   } 
-}
\ No newline at end of file
+}