anchor.diff:  
       // the starting type ID number for Bucket4j classes.
       // you free to choose any unused ID, but be aware that Bucket4j uses 2 types currently,
  -    // and may use more types in the future, so leave enough empty space after baseTypeIdNumber 
  +    // and may use more types in the future, so leave enough empty space after baseTypeIdNumber
       int baseTypeIdNumber = 10000;
  -    
  +
       HazelcastProxyManager.addCustomSerializers(serializationConfig, baseTypeIdNumber);
   ----
   
   ==== Support for externally managed Hazelcast without classpath access
   `bucket4j-hazelcast` requires putting Bucket4j jars to classpath of each node of Hazelcast cluster.
  -Sometimes you have no control over classpath because Hazelcast cluster is externally managed(Paas scenario).
  +Sometimes you have no control over classpath because the Hazelcast cluster is externally managed(Paas scenario).
   In such cases ```HazelcastProxyManager``` can not be used because it is implemented on top of https://docs.hazelcast.com/imdg/4.2/computing/entry-processor[EntryProcessor] functionality.
   
   .Bucket4j provides two alternatives for PaaS topology:
  
positive.code: This implementation requires 2 network hops if no contention happens, but in case of high contention on the key amount of hops is unpredictable.
  
  .Limitations of HazelcastLockBasedProxyManager and HazelcastCompareAndSwapBasedProxyManager
  * `HazelcastLockBasedProxyManager` does not provide async API because lack of `lockAsync` and `unlockAsync`  methods inside IMap API.
  * `HazelcastCompareAndSwapBasedProxyManager` does not provide async API because lack of `replaceAsync` and `putIfAbsentAsync` methods inside IMap API.
  
  If you wish to async API be supported by `HazelcastLockBasedProxyManager` and `HazelcastCompareAndSwapBasedProxyManager` ask Hazelcast maintainers to support the missed APIs mentioned above.
  
negative.code:     <version>{revnumber}</version>
  </dependency>
  ----
  If you are using a legacy version of Hazelcast ``3.x`` then you need to add the following dependency:
  [source, xml, subs=attributes+]
  ----
  <dependency>
  