fix: Fix minor typos (#2619)

Signed-off-by: Marcel Ribeiro-Dantas <mribeirodantas@seqera.io>
Co-authored-by: Ilkka Seppälä <iluwatar@users.noreply.github.com>

circuit-breaker/src/main/java/com/iluwatar/circuitbreaker/App.java

@@ -29,7 +29,7 @@ import lombok.extern.slf4j.Slf4j;
 /**
  * <p>
  * The intention of the Circuit Builder pattern is to handle remote failures robustly, which is to
- * mean that if a service is dependant on n number of other services, and m of them fail, we should
+ * mean that if a service is dependent on n number of other services, and m of them fail, we should
  * be able to recover from that failure by ensuring that the user can still use the services that
  * are actually functional, and resources are not tied up by uselessly by the services which are not
  * working. However, we should also be able to detect when any of the m failing services become

circuit-breaker/src/test/java/com/iluwatar/circuitbreaker/DefaultCircuitBreakerTest.java

@@ -74,7 +74,7 @@ class DefaultCircuitBreakerTest {
       }
     };
     var circuitBreaker = new DefaultCircuitBreaker(mockService, 1, 1, 100);
-    //Call with the paramater start_time set to huge amount of time in past so that service
+    //Call with the parameter start_time set to huge amount of time in past so that service
     //replies with "Ok". Also, state is CLOSED in start
     var serviceStartTime = System.nanoTime() - 60 * 1000 * 1000 * 1000;
     var response = circuitBreaker.attemptRequest();