small typos (comments)
authorHernâni Marques <hernani@pep.foundation>
Wed, 14 Dec 2016 17:27:30 +0100
changeset 1489e1a35c0169c0
parent 1488 16829200236d
child 1490 e375c22bc587
small typos (comments)
src/sync.h
     1.1 --- a/src/sync.h	Wed Dec 14 17:08:28 2016 +0100
     1.2 +++ b/src/sync.h	Wed Dec 14 17:27:30 2016 +0100
     1.3 @@ -5,7 +5,7 @@
     1.4  
     1.5  In the engine, KeySync is implemented through a state machine [1]. KeySync
     1.6  state machine is driven [2] by events, triggering actions [3] and transitions
     1.7 -to new states. Events happens on decryption of email messages, on key
     1.8 +to new states. Events happen on decryption of email messages, on key
     1.9  generation, on user interaction through the app and in case of timeout when
    1.10  staying too long in some particular states.
    1.11  
    1.12 @@ -26,7 +26,7 @@
    1.13  collected from decrypted messages. They are jobs to be processed by the state
    1.14  machine.
    1.15  
    1.16 -KeySync messages can be emitted by multiple session, and could naturally come
    1.17 +KeySync messages can be emitted by multiple sessions, and could naturally come
    1.18  from different threads. They must be serialized in a locked queue. Attached
    1.19  sessions inject [8] KeySync messages in the queue. Protocol loop retrieves [9]
    1.20  them from the queue. KeySync message is received [10] by the state machine,
    1.21 @@ -38,7 +38,7 @@
    1.22  passed as a parameter of the call to the blocking queue retrieve operation on 
    1.23  next protocol loop iteraton.
    1.24  
    1.25 -[1] sync/device_group.fsm , src/sync_fsm.c (generated)
    1.26 +[1] sync/devicegroup.fsm , src/sync_fsm.c (generated)
    1.27  [2] src/sync_driver.c (generated)
    1.28  [3] src/sync_actions.c , src/sync_send_actions.c (generated)
    1.29  [4] register_sync_callbacks()