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>

Author: mribeirodantas

README.md

@@ -1,4 +1,4 @@
-<!-- the line below needs to be an empty line C: (its because kramdown isnt
+<!-- the line below needs to be an empty line C: (its because kramdown isn't
  that smart and dearly wants an empty line before a heading to be able to
  display it as such, e.g. website) -->
 

aggregator-microservices/information-microservice/src/main/java/com/iluwatar/information/microservice/InformationController.java

@@ -34,7 +34,7 @@
 public class InformationController {
 
  /**
- * Endpoint to retrieve a product's informations.
+ * Endpoint to retrieve a product's information.
  *
  * @return product inventory.
  */

caching/src/main/java/com/iluwatar/caching/database/DbManagerFactory.java

@@ -25,7 +25,7 @@
 package com.iluwatar.caching.database;
 
 /**
- * Creates the database connection accroding the input parameter.
+ * Creates the database connection according the input parameter.
  */
 public final class DbManagerFactory {
  /**

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

@@ -29,7 +29,7 @@
 /**
  * <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 @@ public String call() throws RemoteServiceException {
  }
  };
  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();

commander/README.md

@@ -18,7 +18,7 @@ This pattern can be used when we need to make commits into 2 (or more) databases
 
 ## Explanation
 Handling distributed transactions can be tricky, but if we choose to not handle it carefully, there could be unwanted consequences. Say, we have an e-commerce website which has a Payment microservice and a Shipping microservice. If the shipping is available currently but payment service is not up, or vice versa, how would we deal with it after having already received the order from the user?
-We need a mechanism in place which can handle these kinds of situations. We have to direct the order to either one of the services (in this example, shipping) and then add the order into the database of the other service (in this example, payment), since two databses cannot be updated atomically. If currently unable to do it, there should be a queue where this request can be queued, and there has to be a mechanism which allows for a failure in the queueing as well. All this needs to be done by constant retries while ensuring idempotence (even if the request is made several times, the change should only be applied once) by a commander class, to reach a state of eventual consistency.
+We need a mechanism in place which can handle these kinds of situations. We have to direct the order to either one of the services (in this example, shipping) and then add the order into the database of the other service (in this example, payment), since two databases cannot be updated atomically. If currently unable to do it, there should be a queue where this request can be queued, and there has to be a mechanism which allows for a failure in the queueing as well. All this needs to be done by constant retries while ensuring idempotence (even if the request is made several times, the change should only be applied once) by a commander class, to reach a state of eventual consistency.
 
 ## Credits
 

currying/README.md

@@ -183,7 +183,7 @@ Cons
 * As shown in the programmatic example above, curried functions with several parameters have a cumbersome type signature (in Java).
 
 ## Related patterns
-* [Builder patter](https://java-design-patterns.com/patterns/builder/)
+* [Builder pattern](https://java-design-patterns.com/patterns/builder/)
 
 ## Credits
 * [Currying in Java](https://www.baeldung.com/java-currying)

data-mapper/src/main/java/com/iluwatar/datamapper/DataMapperException.java

@@ -25,7 +25,7 @@
 package com.iluwatar.datamapper;
 
 /**
- * Using Runtime Exception for avoiding dependancy on implementation exceptions. This helps in
+ * Using Runtime Exception for avoiding dependency on implementation exceptions. This helps in
  * decoupling.
  *
  * @author amit.dixit

embedded-value/src/main/java/com/iluwatar/embedded/value/App.java

@@ -62,7 +62,7 @@ public static void main(String[] args) throws Exception {
 
  // Create table for orders - Orders(id, name, orderedBy, city, state, pincode).
  // We can see that table is different from the Order object we have.
- // We're mapping ShippingAddress into city, state, pincode colummns of the database and not creating a separate table.
+ // We're mapping ShippingAddress into city, state, pincode columns of the database and not creating a separate table.
  if (dataSource.createSchema()) {
  LOGGER.info("TABLE CREATED");
  LOGGER.info("Table \"Orders\" schema:\n" + dataSource.getSchema());
@@ -95,7 +95,7 @@ public static void main(String[] args) throws Exception {
  dataSource.removeOrder(1);
  LOGGER.info("\nOrders Query: {}", dataSource.queryOrders().collect(Collectors.toList()) + "\n");
 
- //After successfull demonstration of the pattern, drop the table
+ //After successful demonstration of the pattern, drop the table
  if (dataSource.deleteSchema()) {
  LOGGER.info("TABLE DROPPED");
  } else {

event-queue/src/main/java/com/iluwatar/event/queue/Audio.java

@@ -144,7 +144,7 @@ private void update() {
  clip.open(audioStream);
  clip.start();
  } catch (LineUnavailableException e) {
- LOGGER.trace("Error occoured while loading the audio: The line is unavailable", e);
+ LOGGER.trace("Error occurred while loading the audio: The line is unavailable", e);
  } catch (IOException e) {
  LOGGER.trace("Input/Output error while loading the audio", e);
  } catch (IllegalArgumentException e) {