Original text:
A network incident refers to an unexpected interruption of a network service, degradation of a network service quality, or sub-health of a <del> network service.  Different data sources including alarms, metrics </del>  and other anomaly information can be aggregated into few amount of network incidents by data correlation analysis and the service impact analysis. This document defines YANG Modules for the network incident lifecycle <del> management.  The YANG modules are meant to provide a standard way to report, diagnose, and resolve network incidents for the sake of </del>  network service health and root cause analysis. 1. RFC8969 defines a framework for Automating Service and Network <del> Management with YANG to full life cycle network management.  A set of YANG data models have already been developed in IETF for Network performance monitoring and fault monitoring,e.g.,A YANG RFC7950 data model for alarm management RFC8632 defines a standard interface for alarm management.  A data model for Network and VPN Service </del>  Performance Monitoring RFC9375 defines a standard interface for network performance management.  In addition, distributed tracing <del> mechanism defined in W3C-Trace-Context can also be used to analyze and debug operations, such as configuration transactions, across multiple distributed systems. </del>  <del> However these YANG data models for network maintenance are based on </del>  specific data source information and manage alarms and performance metrics data separately by different layers in various different management systems.  In addition, the frequency and quantity of

Reviewer comments:
We remove incident type yang model, so the number of yang modules we proposed is reduced from 2 into 1. So I think the text still needs some tweak, besides this, all good changes.

Revised text:
A network incident refers to an unexpected interruption of a network service, degradation of a network service quality, or sub-health of a  <ins> network service.  Different data sources including alarms, metrics, </ins> and other anomaly information can be aggregated into few amount of network incidents by data correlation analysis and the service impact analysis. This document defines YANG Modules for the network incident lifecycle  <ins> management.  These YANG modules are meant to provide a standard way to report, diagnose, and resolve network incidents for the sake of </ins> network service health and root cause analysis. 1. RFC8969 defines a framework for Automating Service and Network  <ins> Management with YANG RFC7950 to full life cycle network management. A set of YANG data models have already been developed in IETF for network performance monitoring and fault monitoring, e.g., a YANG data model for alarm management RFC8632 defines a standard interface for alarm management.  A data model for Network and VPN Service </ins> Performance Monitoring RFC9375 defines a standard interface for network performance management.  In addition, distributed tracing  <ins> mechanism defined in W3C-Trace-Context can be used to analyze and debug operations, such as configuration transactions, across multiple distributed systems. </ins>  <ins> However, these YANG data models for network maintenance are based on </ins> specific data source information and manage alarms and performance metrics data separately by different layers in various different management systems.  In addition, the frequency and quantity of