Update P-OSOE-Event.004.en.html

bt5/erp5_osoe_theory_data/PathTemplateItem/web_page_module/P-OSOE-Event.004.en.html

@@ -45,7 +45,7 @@
             <strong>Phone Call</strong>
             &quot; to write a summary of your conversation during the call; Most CRM systems allow you to directly send emails from the central system to any email address using &quot;
             <strong>Mail message</strong>
-            &quot;, moreover you can also ingest the mails you receive; When you receive many letters or faxes, you can scan them and add them to &quot;
+            &quot;, moreover, you can also ingest the mails you receive; When you receive many letters or faxes, you can scan them and add them to &quot;
             <strong>Letter</strong>
             &quot; and &quot;
             <strong>Fax</strong>
@@ -57,7 +57,7 @@
             <strong>Site Message</strong>
             &quot;, eg, site message is usually used for to send a message to all users of the ERP system etc.
             <br />
-            Depends on your business you might have more kinds of interactions.
+            Depending on your business, you might have more kinds of interactions.
           </p> 
       <p>
             In our example of communicating by emails, the <strong>Event Type</strong>
@@ -68,7 +68,7 @@
             Besides different types, the interactions also have different natures.<br />
             The nature of an event is classified by its objective: complaint, announcement, advertisement, information, inquiry, spam, etc. We need to classify the events by their natures: an email sent to complain doesn't have the same meaning with an email sent to advertise.
             <br />
-            Depends on your business field, the user of the CRM system will choose to classify the events with their own categories.
+            Depending on your business field, the user of the CRM system will choose to classify the events with their own categories.
           </p> 
       <p>
             In our example of the mail message sent by VIFIB manager, the <strong>Event Type</strong>
@@ -76,7 +76,7 @@
           </p> </details> </section><section class="illustration"> 
     <h1>One sender/ multiple receivers</h1> <img src="user-Events.One.Sender.Multiple.Receivers?format=png" type="image/png" alt="Events: one sender multiple receivers" title="Events: one sender multiple receivers" /> <details open="open"> 
       <p>
-            An Event, which is representing a movement of resource (information, inquiry, etc.), is going from someone to one or more recipients. In a CRM, we distinguish the Events not only by their contents, but also by their senders.<br />
+            An Event, which represents a movement of resource (information, inquiry, etc.), is going from someone to one or more recipients. In a CRM, we distinguish the Events not only by their contents, but also by their senders.<br />
             The Event always has only one sender, but can have an infinite number of receivers. The same message sent by two persons to one same receiver will be represented as two different Events, while the same message sent from one person to many others will be represented as a single Event.
           </p> 
       <p>In our example, the email sent by the VIFIB manager to his contacts is one single Event because of the same sender, while all those replies are different Events, even though the contents might be the same.</p> </details> </section><section class="illustration"> 
@@ -89,7 +89,7 @@
             <strong>Outgoing events</strong>
             go from your organisation to external persons.
             <br />
-            This distinction is really important since you won't handle the same way the preparation of outgoing events and how you take care of incoming events.
+            This distinction is really important since you would not handle the preparation of outgoing events the same way as how you take care of incoming events.
           </p> 
       <p>In our example, the Mail Message sent by VIFIB manager is an outgoing Event, while the replies from the his contacts are incoming Events.</p> </details> </section><section class="illustration"> 
     <h1>Keeping track of interactions: Event origin</h1> <img src="user-Events.Keep.Tracks.Of.Interactions.Event.Origin?format=png" type="image/png" alt="Keep track of interactions by 'Event Origin'" title="Keep track of interactions by 'Event Origin'" /> <details open="open"> 
@@ -99,7 +99,7 @@
             <strong>&quot;Follow Up&quot;</strong>
             , you can easily keep track of interactions between your organisation and the external contacts.
           </p> 
-      <p> <strong>Firstly, by using &quot;Event Origin&quot;, even complex interaction can also be shown clearly</strong> </p> 
+      <p> <strong>Firstly, by using &quot;Event Origin&quot;, even complex interactions can be shown clearly.</strong> </p> 
       <p>
             A <strong>single interaction</strong>
             happens between only two persons, but it can have various event types (as shown in the left side), according to the needs of the sender and receiver.
@@ -108,7 +108,7 @@
             However, for <strong>complex interactions</strong>
             (as shown in the right side), we can have many interlocutors within it, done by different persons inside and outside our organisation, using various communication tools. In this case, if we list the events related to one person, we will only have a partial view of the conversation.
           </p> 
-      <p>As we can see in both tables with records of detail discussions happened between VIFIB staff and its customers in subject of a new product offer, the event N°1 is the reason why the customer replied and created the event N°2. So we can say that the event N°1 is the origin of the event N°2.</p> 
+      <p>As we can see in both tables with records of detailed discussions between VIFIB staff and its customers in subject of a new product offer, the event N°1 is the reason why the customer replied and created the event N°2. So we can say that the event N°1 is the origin of the event N°2.</p> 
       <p>
             So using <strong>&quot;Event Origin&quot;</strong>
             can correctly and precisely represent the relation between events.
@@ -117,11 +117,11 @@
       <p> <strong>Secondly,</strong>
             an Event can also
             <strong>&quot;Follow Up&quot;</strong>
-            a Ticket, which is a record in the CRM all Events and documents related to the same subject. We will introduce it in the next tutorial.
+            a Ticket, which is a record in the CRM linking all Events and documents related to the same subject. We will introduce it in the next tutorial.
           </p> 
       <p>
             Back to our example, as you can see in the above screenshot, in the detail page of a Event which is a reply email from one contact who got the original mail message from our VIFIB manager, it shows the <strong>Event Origin</strong>
-            ( &quot;SlapOS Ongoing!&quot;) and the Ticket which this Event
+            ( &quot;SlapOS Ongoing!&quot;) and the Ticket with the corresponding Event
             <strong>Follow Up</strong>
             ( &quot;Beta Developer Program&quot;). So these two features help us present complex interactions in a clear way.
             <br /> </p> </details> </section><section class="illustration">