anchor.diff:       *
        * @param numTokens The number of tokens to consume from the bucket, must be a positive number.
        *
  -     * @return {@link ConsumptionProbe} which describes both result of consumption and tokens remaining in the bucket after consumption.
  +     * @return {@link ConsumptionProbe} which describes both the result of consumption and tokens remaining in the bucket after consumption.
        */
       ConsumptionProbe tryConsumeAndReturnRemaining(long numTokens);
   ----
  
positive.code: [source, java]
  ----
      /**
       * Returns new copy of this bucket instance decorated by {@code listener}.
       * The created bucket will share same tokens with source bucket and vice versa.
       *
       * See javadocs for {@link BucketListener} in order to understand semantic of listener.
       *
       * @param listener the listener of bucket events.
       *
  
negative.code:      *     bucket.replaceConfiguration(newConfiguration, TokensInheritanceStrategy.AS_IS);
       * </code>
       * </pre>
       * It is obvious that a simple strategy - copying tokens by bandwidth index will not work well in this case, because it highly depends from order.
       * Instead of inventing the backward magic Bucket4j provides to you the ability to deap controll of this process by specifying identifiers for bandwidth,
       * so in case of multiple bandwidth configuratoin replacement code can copy available tokens by bandwidth ID. So it is better to rewrite the code above as following:
       * <pre>
       * <code>
       * Bucket bucket = Bucket.builder()
  