feat: improve readme

Author: owen2345

README.md

@@ -536,6 +536,8 @@ config.debug = true
     (Proc) => called after publishing a notification
 - ```.on_error_publish = ->(exception, {payload:}) { payload.delay(...).publish! }```
     (Proc) => called when failed publishing a notification (delayed_job or similar can be used for retrying)
+- ```.skip_cache = false```
+    (true/false*) => Allow to skip payload optimization (cache settings)
 - ```.transactions_max_buffer = 1``` (Integer, default 1) Controls the maximum quantity of notifications to be enqueued to the transaction-buffer before delivering them and thus adds the ability to rollback notifications if the transaction fails.        
     Once this quantity of notifications is reached, then all notifications of the current transaction will immediately be delivered (can be customized per transaction).    
     Note: There is no way to rollback delivered notifications if current transaction fails later.      

pub_sub_model_sync.gemspec

@@ -11,8 +11,11 @@ Gem::Specification.new do |spec|
   spec.authors       = ['Owen']
   spec.email         = ['owenperedo@gmail.com']
 
-  spec.summary       = 'Permit to sync models between apps through pub/sub'
-  spec.description   = 'Permit to sync models between apps through pub/sub'
+  spec.summary       = 'This gem permits to sync automatically models and custom data between multiple Rails
+    applications by publishing notifications via pubsub (Google PubSub, RabbitMQ, or Apache Kafka) and automatically
+    processed by all connected applications. Out of the scope, this gem includes transactions to keep Data consistency
+    by processing notifications in the order they were delivered.'
+  spec.description   = spec.summary
   spec.homepage      = 'https://github.com/owen2345/pub_sub_model_sync'
   spec.license       = 'MIT'