diff --git a/draft-lopez-opsawg-yang-provenance.md b/draft-lopez-opsawg-yang-provenance.md
index 41bcf89..b385417 100644
--- a/draft-lopez-opsawg-yang-provenance.md
+++ b/draft-lopez-opsawg-yang-provenance.md
@@ -61,7 +61,7 @@ When datasets are made available as an online data flow, provenance can be asses
 
 The original use case for this provenance mechanism is associated with {{YANGmanifest}}, in order to provide a proof of the origin and integrity of the provided metadata, and therefore the examples in this document use the modules described there, but it soon became clear that it could be extended to any YANG datamodel to support provenance evidence. An analysis of other potential use cases suggested the interest of defining an independent, generally applicable mechanism.
 
-Provenance verification by signatures incorporated in the YANG data elements can be applied to any data processing pipeline, whether they rely on an online flow or use some kind of data store (such as data lakes or time-series databases). The application of recorded data for ML training or validation constitute the most relevant examples of these scenarios.
+Provenance verification by signatures incorporated in the YANG data elements can be applied to any data processing pipeline, whether they rely on an online flow or use some kind of data store, such as data lakes or time-series databases. The application of recorded data for ML training or validation constitute the most relevant examples of these scenarios.
 
 This document provides a mechanism for including digital signatures within YANG data. It applies COSE {{RFC9052}} to make the signature compact and reduce the resources required for calculating it. This mechanism is applicable to any serialization of the YANG data supporting a clear method for canonicalization, but this document considers three base ones: CBOR, JSON and XML.