README.md in rufus-scheduler-3.0.7 vs README.md in rufus-scheduler-3.0.8

@@ -392,21 +392,25 @@
 
 This option is for repeat jobs (cron / every) only.
 
 It's used to specify the first time after which the repeat job should trigger for the first time.
 
-In the case of an "every" job, this will be the first time (module the scheduler frequency) the job triggers.
-For a "cron" job, it's the time after which the first schedule will trigger.
+In the case of an "every" job, this will be the first time (modulo the scheduler frequency) the job triggers.
+For a "cron" job, it's the time *after* which the first schedule will trigger.
 
 ```ruby
 scheduler.every '2d', :first_at => Time.now + 10 * 3600 do
   # ... every two days, but start in 10 hours
 end
 
 scheduler.every '2d', :first_in => '10h' do
   # ... every two days, but start in 10 hours
 end
+
+scheduler.cron '00 14 * * *', :first_in => '3d' do
+  # ... every day at 14h00, but start after 3 * 24 hours
+end
 ```
 
 :first, :first_at and :first_in all accept a point in time or a duration (number or time string). Use the symbol you think make your schedule more readable.
 
 Note: it's OK to change the first_at (a Time instance) directly:
@@ -1133,10 +1137,10 @@
 ```
 
 
 ## advanced lock schemes
 
-As seen above, rufus-scheduler proposes the :lockfile system out of the box. If in a group of schedulers only one is supposed to run, the lockfile mecha prevents schedulers that have not set/created the lockfile from running.
+As seen above, rufus-scheduler proposes the [:lockfile](#lockfile--mylockfiletxt) system out of the box. If in a group of schedulers only one is supposed to run, the lockfile mecha prevents schedulers that have not set/created the lockfile from running.
 
 There are situation where this is not sufficient.
 
 By overriding #lock and #unlock, one can customize how his schedulers lock.