anchor.diff:  
   ==== Configuring Custom Serialization for Bucket4j library classes
   If you configure nothing, then by default Java serialization will be used for serialization Bucket4j library classes. Java serialization can be rather slow and should be avoided in general.
  -``Bucket4j`` provides https://docs.hazelcast.org/docs/3.0/manual/html/ch03s03.html[custom serializers] for all library classes that could be transferred over network.
  +``Bucket4j`` provides https://docs.hazelcast.org/docs/3.0/manual/html/ch03s03.html[custom serializers] for all library classes that could be transferred over the network.
   To let Hazelcast know about fast serializers you should register them programmatically in the serialization config:
   [source, java]
   ----
  
positive.code: 
      // 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 
      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).
  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:
  
negative.code: [[bucket4j-hazelcast, Bucket4j-Hazelcast]]
  === Hazelcast integration
  ==== Dependencies
  To use Bucket4j extension for Hazelcast with ``Hazelcast 4.x`` you need to add the following dependency:
  [source, xml, subs=attributes+]
  ----
  <dependency>
  