[NO ISSUE] Update eventing-timers.adoc (#266)

Correct two typos

Author: BKaneAtWork

modules/eventing/pages/eventing-timers.adoc

@@ -153,7 +153,7 @@ Timers are not wall-clock accurate events. The timer implementation is designed
 
 Couchbase currently scans for active timers every 7 seconds this creates a maximum delay of 7 seconds + the time it takes too process timers ahead of the given timer on a given thread. Thus, in an Eventing system in a steady state you will typically experience an average timer firing delay of about 3-4 seconds after the scheduled time. 
 
-However, if timer is created and scheduled to close the wall clock of the system Couchbase may delay the actual scheduling by an additional 1 to 2 scan periods (up to a 14 second delay after the scheduled time) to avoid races. 
+However, if timer is created and scheduled too close the wall clock of the system, Couchbase may delay the actual scheduling by an additional 1 to 2 scan periods (up to a 14 second delay after the scheduled time) to avoid races. 
 
 The additional overall delay is an implementation artifact and may change between releases.