README.md in sidekiq-unique-jobs-7.0.0.beta2 vs README.md in sidekiq-unique-jobs-7.0.0.beta3

@@ -416,35 +416,35 @@
 The last one is log which can be be used with the lock `UntilExecuted` and `UntilExpired`. Now we write a log entry saying the job could not be pushed because it is a duplicate of another job with the same arguments
 
 ### log
 
 ```ruby
-sidekiq_options on_conflict: :log`
+sidekiq_options on_conflict: :log
 ```
 
 This strategy is intended to be used with `UntilExecuted` and `UntilExpired`. It will log a line about that this is job is a duplicate of another.
 
 ### raise
 
 ```ruby
-sidekiq_options on_conflict: :raise`
+sidekiq_options on_conflict: :raise
 ```
 
 This strategy is intended to be used with `WhileExecuting`. Basically it will allow us to let the server process crash with a specific error message and be retried without messing up the Sidekiq stats.
 
 ### reject
 
 ```ruby
-sidekiq_options on_conflict: :reject`
+sidekiq_options on_conflict: :reject
 ```
 
 This strategy is intended to be used with `WhileExecuting` and will push the job to the dead queue on conflict.
 
 ### replace
 
 ```ruby
-sidekiq_options on_conflict: :replace`
+sidekiq_options on_conflict: :replace
 ```
 
 This strategy is intended to be used with client locks like `UntilExecuted`.
 It will delete any existing job for these arguments from retry, schedule and
 queue and retry the lock again.
@@ -453,11 +453,11 @@
 always scheduled in the future. Currently only attempting to retry one time.
 
 ### Reschedule
 
 ```ruby
-sidekiq_options on_conflict: :reschedule`
+sidekiq_options on_conflict: :reschedule
 ```
 
 This strategy is intended to be used with `WhileExecuting` and will delay the job to be tried again in 5 seconds. This will mess up the sidekiq stats but will prevent exceptions from being logged and confuse your sysadmins.
 
 ### Custom Strategies
@@ -473,10 +473,10 @@
     end
   end
 end
 ```
 
-You can refer on all the startegies defined in `lib/sidekiq_unique_jobs/on_conflict`.
+You can refer to all the strategies defined in `lib/sidekiq_unique_jobs/on_conflict`.
 
 In order to make it available, you should call in your project startup:
 
 ```ruby
 # For rails application