fix spelling and english syntax error

Author: OlivierJourdan

www/en/modules/ROOT/pages/event-sources.adoc

@@ -3,11 +3,11 @@
 
 == User Interface
 
-The first source of events you come across when starting with {lv} are the events generated by the UI when a user of your application use the mouse or the keybard.
+The first source of events you come across when starting with {lv} is the events generated by the UI when a user of your application uses the mouse or the keyboard.
 
-The {es} is the way to detect the event and execute the appropriate caode.
+The {es} is the way to detect the event and execute the appropriate code.
 
-NOTE: Before the introduction of the {es} (a long time ago), LabVIEW developpers had to periodically poll the controls to detect interactions with the {ui} 😓.
+NOTE: Before the introduction of the {es} (a long time ago), LabVIEW developers had to periodically poll controls to detect interactions with the {ui} 😓.
 
 Example code: *01a - Event Sources - User Interface.vi*
 
@@ -20,11 +20,11 @@ image::04-event-sources-ui-dg.png[]
 == User Events a.k.a Custom Events
 
 [quote,John Medland. MLUG October 2020]
-User Events, the worst named feature in {lv}
+User Events, the worst-named feature in {lv}
 
 Behind this name, you'll find the way to create and generate events programmatically.
 
-NOTE: This source of events is the corner stones of many event driven architectures. The https://www.dqmh.org[DQMH framework] is probably one of the most popular framework based on the {lv} user event feature.
+NOTE: This source of events is the cornerstone of many event-driven architectures. The https://www.dqmh.org[DQMH framework] is probably one of the most popular frameworks based on the {lv} user event feature.
 
 Example code: *01b - Event Sources - Custom Events.vi*
 
@@ -37,11 +37,11 @@ image::06-event-sources-user-event-dg.png[]
 == Event Callback
 
 This source of event doesn't involve the use of an {es}.
-Once registred to an event the Callback VI is executed each time the event occurs.
+Once registered to an event, the Callback VI is executed each time the event occurs.
 
-NOTE: This kind of event breaks the usal data flow we are used to
+NOTE: This kind of event breaks the usual data flow we are used to
 
-// List examples of situation where event callback can be useful  
+// List examples of situations wherethe  event callback can be useful  
 
 Example code: *01c - Event Sources - Event Callback.vi*
 
@@ -56,11 +56,11 @@ image::09-event-sources-callback-vi.png[]
 
 == Daqmx
 
-This source of event is problably the less known.
+This source of the event is probably the least known.
 With it, you can handle acquistion event in the {es}.
-It makes straigtforward the use of the other sources of events in the loop that handle the acquistion.
+It makes the use of other event sources in the loop that handle acquisition straightforward.
 
-IMPORTANT: This example requieres the NI Daqmx driver to be executed.
+IMPORTANT: This example requires the NI Daqmx driver to be executed.
 
 Example code: *01d - Event Sources - Daqmx Event.vi*