Update blog/docs/articles/kubevirt_meets_eventing.md

Co-authored-by: Calum Murray <cmurray@redhat.com>

Author: matzew

blog/docs/articles/kubevirt_meets_eventing.md

@@ -271,7 +271,7 @@ This tailored event will perfectly serve our use case and makes the processing f
 
 With almost all our necessary components ready-to-go it is time to bring the use case "Monitoring Virtual Machines with Knative Eventing" to life. The final missing pieces are the function, deployed as a Knative Service (`ksvc`), and the corresponding `triggers`. The `triggers` will do the routing of events from the Broker to a Sink (in our case, the deployed function). Think of it like: "When an event matching this filter arrives in the broker, send it to this service (e.g. a function)."
 
-Remember, we want our CMDB database automatically and event-driven updated based on virtuial machine creation or deletion operations. Important is, that we are only interested in specific data which should be feet into the DB.
+Remember, we want our CMDB database automatically updated based on virtual machine creation or deletion operations. Crucially, we are only interested in specific data which should be fed into the DB.
 
 The following output shows a so-far empty PostgreSQL DB. Notce that the columns are matching the jsonata expressions from the configured `EventTransform` CR.