Updated documentation

Author: RobWin

resilience4j-documentation/src/docs/asciidoc/core_guides/circuitbreaker.adoc

@@ -101,7 +101,7 @@ In this example `map` is not invoked, because the CircuitBreaker is OPEN. The ca
 include::../../../../../resilience4j-circuitbreaker/src/test/java/io/github/resilience4j/circuitbreaker/CircuitBreakerTest.java[tags=shouldThrowCircuitBreakerOpenException]
 ----
 
-==== Reset
+===== Reset
 
 The CircuitBreaker supports resetting, returning to its original state while losing all the current metrics.
 

resilience4j-documentation/src/docs/asciidoc/implementation_details.adoc

@@ -12,7 +12,7 @@ The CircuitBreaker does not know anything about the backend's state by itself, b
 ----
 static <T> Supplier<T> decorateSupplier(CircuitBreaker circuitBreaker, Supplier<T> supplier){
     return () -> {
-        CircuitBreakerUtils.obtainPermission(circuitBreaker);
+        circuitBreaker.obtainPermission();
         long start = System.nanoTime();
         try {
             T returnValue = supplier.get();