docs: Content SEO updates (#2990)

* update yaml frontmatter format

* update abstract document

* update abstract factory

* use the new pattern template

* acyclic visitor seo

* adapter seo

* ambassador seo

* acl seo

* aaa seo

* async method invocation seo

* balking seo

* bridge seo

* builder seo

* business delegate and bytecode seo

* caching seo

* callback seo

* chain seo

* update headings

* circuit breaker seo

* client session + collecting parameter seo

* collection pipeline seo

* combinator SEO

* command seo

* cqrs seo

* commander seo

* component seo

* composite seo

* composite entity seo

* composite view seo

* context object seo

* converter seo

* crtp seo

* currying seo

* dao seo

* data bus seo

* data locality seo

* data mapper seo

* dto seo

* decorator seo

* delegation seo

* di seo

* dirty flag seo

* domain model seo

* double buffer seo

* double checked locking seo

* double dispatch seo

* dynamic proxy seo

* event aggregator seo

* event-based asynchronous seo

* eda seo

* event queue seo

* event sourcing seo

* execute around seo

* extension objects seo

* facade seo

* factory seo

* factory kit seo

* factory method seo

* fanout/fanin seo

* feature toggle seo

* filterer seo

* fluent interface seo

* flux seo

* flyweight seo

* front controller seo

* function composition seo

* game loop seo

* gateway seo

* guarded suspension seo

* half-sync/half-async seo

* health check seo

* hexagonal seo

* identity map seo

* intercepting filter seo

* interpreter seo

* iterator seo

* layers seo

* lazy loading seo

* leader election seo

* leader/followers seo

* lockable object seo

* rename and add seo for marker interface

* master-worker seo

* mediator seo

* memento seo

* metadata mapping seo

* microservice aggregator seo

* api gw seo

* microservices log aggregration seo

* mvc seo

* mvi seo

* mvp seo

* mvvm seo

* monad seo

* monitor seo

* monostate seo

* multiton seo

* mute idiom seo

* naked objects & notification seo

* null object seo

* object mother seo

* object pool seo

* observer seo

* optimistic locking seo

* page controller seo

* page object seo

* parameter object seo

* partial response seo

* pipeline seo

* poison pill seo

* presentation model seo

* private class data seo

* producer-consumer seo

* promise seo

* property seo

* prototype seo

* proxy seo

* queue-based load leveling seo

* reactor seo

* registry seo

* repository seo

* RAII seo

* retry seo

* role object seo

* saga seo

* separated interface seo

* serialized entity seo

* serialized lob seo

* servant seo

* server session seo

* service layer seo

* service locator seo

* service to worker seo

* sharding seo

* single table inheritance seo

* singleton seo

* spatial partition seo

* special case seo

* specification seo

* state seo

* step builder seo

* strangler seo

* strategy seo

* subclass sandbox seo

* table module seo

* template method seo

* throttling seo

* tolerant reader seo

* trampoline seo

* transaction script seo

* twin seo

* type object seo

* unit of work seo

* update method seo

* value object seo

* version number seo

* virtual proxy seo

* visitor seo

* seo enhancements

* seo improvements

* SEO enhancements

* SEO improvements

* SEO additions

* SEO improvements

* more SEO improvements

* rename hexagonal + SEO improvements

* SEO improvements

* more SEO stuff

* SEO improvements

* SEO optimizations

* SEO enhancements

* enchance SEO

* improve SEO

* SEO improvements

* update headers

fluent-interface/README.md

@@ -1,13 +1,15 @@
 ---
-title: Fluent Interface
+title: "Fluent Interface Pattern in Java: Enhancing Code Expressiveness with Fluent APIs"
+shortTitle: Fluent Interface
+description: "Learn how to implement the Fluent Interface design pattern in Java. Explore method chaining and Fluent API with practical examples and improve your code readability and maintainability."
 category: Behavioral
 language: en
 tag: 
-    - API design
-    - Code simplification
-    - Decoupling
-    - Object composition
-    - Reactive
+  - API design
+  - Code simplification
+  - Decoupling
+  - Object composition
+  - Reactive
 ---
 
 ## Also known as
@@ -15,15 +17,15 @@ tag:
 * Fluent API
 * Method Chaining
 
-## Intent
+## Intent of Fluent Interface Design Pattern
 
-To provide an easily readable, flowing API by chaining method calls.
+The primary goal of the Fluent Interface pattern is to provide an easily readable and flowing API by chaining method calls, often referred to as method chaining. This approach is ideal for building complex objects step-by-step and improving the overall developer experience.
 
-## Explanation
+## Detailed Explanation of Fluent Interface Pattern with Real-World Examples
 
 Real-world example
 
-> Imagine you are at a coffee shop and you want to customize your coffee order. Instead of telling the barista everything at once, you specify each customization step-by-step in a way that flows naturally. For instance, you might say, "I'd like a large coffee, add two shots of espresso, no sugar, and top it with almond milk." This approach is similar to the Fluent Interface design pattern, where you chain together method calls to configure an object in a readable and intuitive manner. Just as you specify each part of your coffee order sequentially, a Fluent Interface allows you to chain method calls to build and configure objects step-by-step in code.
+> Imagine you are at a coffee shop customizing your order step-by-step. This approach is similar to how the Fluent Interface design pattern works in Java, allowing you to chain method calls to build and configure objects sequentially. Instead of telling the barista everything at once, you specify each customization step-by-step in a way that flows naturally. For instance, you might say, "I'd like a large coffee, add two shots of espresso, no sugar, and top it with almond milk." This approach is similar to the Fluent Interface design pattern, where you chain together method calls to configure an object in a readable and intuitive manner. Just as you specify each part of your coffee order sequentially, a Fluent Interface allows you to chain method calls to build and configure objects step-by-step in code.
 
 In plain words
 
@@ -33,7 +35,7 @@ Wikipedia says
 
 > In software engineering, a fluent interface is an object-oriented API whose design relies extensively on method chaining. Its goal is to increase code legibility by creating a  domain-specific language (DSL).
 
-**Programmatic Example**
+## Programmatic Example of Fluent Interface Pattern in Java
 
 We need to select numbers based on different criteria from the list. It's a great chance to  utilize fluent interface pattern to provide readable easy-to-use developer experience.
 
@@ -150,19 +152,19 @@ Program output:
 08:50:08.270 [main] INFO com.iluwatar.fluentinterface.app.App -- Last amongst first two negatives: -22
 ```
 
-## Applicability
+## When to Use the Fluent Interface Pattern in Java
 
-Use the Fluent Interface pattern when
+Use the Fluent Interface Pattern in Java when
 
 * Designing APIs that are heavily used and where readability of client code is of high importance.
 * Building complex objects step-by-step, and there is a need to make the code more intuitive and less error-prone.
 * Enhancing code clarity and reducing the boilerplate code, especially in configurations and object-building scenarios.
 
-## Tutorials
+## Fluent Interface Pattern Java Tutorials
 
 * [An Approach to Internal Domain-Specific Languages in Java (InfoQ)](http://www.infoq.com/articles/internal-dsls-java)
 
-## Known uses
+## Real-World Applications of Fluent Interface Pattern in Java
 
 * [Java 8 Stream API](http://www.oracle.com/technetwork/articles/java/ma14-java-se-8-streams-2177646.html)
 * [Google Guava FluentIterable](https://github.com/google/guava/wiki/FunctionalExplained)
@@ -171,11 +173,11 @@ Use the Fluent Interface pattern when
 * [Java Hamcrest](http://code.google.com/p/hamcrest/wiki/Tutorial)
 * Builders in libraries like Apache Camel for integration workflows.
 
-## Consequences
+## Benefits and Trade-offs of Fluent Interface Pattern
 
 Benefits:
 
-* Improved code readability and maintainability.
+* Adopting the Fluent Interface pattern in your Java projects can significantly enhance code readability and maintainability.
 * Encourages building immutable objects since methods typically return new instances.
 * Reduces the need for variables as the context is maintained in the chain.
 
@@ -185,12 +187,12 @@ Trade-offs:
 * Debugging can be challenging due to the chaining of method calls.
 * Overuse can lead to complex and hard-to-maintain code structures.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Builder](https://java-design-patterns.com/patterns/builder/): Often implemented using a Fluent Interface to construct objects step-by-step. The Builder Pattern focuses on constructing complex objects, while Fluent Interface emphasizes the method chaining mechanism.
 * [Chain of Responsibility](https://java-design-patterns.com/patterns/chain-of-responsibility/): Fluent Interfaces can be seen as a specific utilization of the Chain of Responsibility, where each method in the chain handles a part of the task and then delegates to the next method.
 
-## Credits
+## References and Credits
 
 * [Domain-Driven Design: Tackling Complexity in the Heart of Software](https://amzn.to/3UrXkh2)
 * [Domain Specific Languages](https://amzn.to/3R1UYDA)