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

circuit-breaker/README.md

@@ -1,27 +1,29 @@
 ---
-title: Circuit Breaker
+title: "Circuit Breaker Pattern in Java: Enhancing System Resilience"
+shortTitle: Circuit Breaker
+description: "Learn about the Circuit Breaker pattern in Java design, which ensures fault tolerance and prevents cascading failures in distributed systems and microservices architectures."
 category: Resilience
 language: en
 tag:
-    - Cloud distributed
-    - Fault tolerance
-    - Microservices
-    - Retry
+  - Cloud distributed
+  - Fault tolerance
+  - Microservices
+  - Retry
 ---
 
 ## Also known as
 
 * Fault Tolerance Switch
 
-## Intent
+## Intent of Circuit Breaker Design Pattern
 
-To prevent a system from repeatedly trying to execute an operation likely to fail, allowing it to recover from faults and prevent cascading failures.
+The Circuit Breaker pattern is a critical Java design pattern that helps ensure fault tolerance and resilience in microservices and distributed systems. Using Circuit Breaker, it is possible to prevent a system from repeatedly trying to execute an operation likely to fail, allowing it to recover from faults and prevent cascading failures.
 
-## Explanation
+## Detailed Explanation of Circuit Breaker Pattern with Real-World Examples
 
 Real-world example
 
-> Consider a real-world example of an e-commerce website that depends on multiple external payment gateways to process transactions. If one of the payment gateways becomes unresponsive or slow, the Circuit Breaker pattern can be used to detect the failure and prevent the system from repeatedly attempting to use the problematic gateway. Instead, it can quickly switch to alternative payment gateways or display an error message to the user, ensuring that the rest of the website remains functional and responsive. This avoids resource exhaustion and provides a better user experience by allowing transactions to be processed through other available services.
+> Consider a real-world example of an e-commerce website that depends on multiple external payment gateways to process transactions. If one of the payment gateways becomes unresponsive or slow, the Circuit Breaker pattern can be used to detect the failure and prevent the system from repeatedly attempting to use the problematic gateway. Instead, it can quickly switch to alternative payment gateways or display an error message to the user, ensuring that the rest of the website remains functional and responsive. This avoids resource exhaustion and provides a better user experience by allowing transactions to be processed through other available services. This way, the Circuit Breaker pattern handles external API failures, ensuring the system remains functional.
 
 In plain words
 
@@ -31,7 +33,9 @@ Wikipedia says
 
 > Circuit breaker is a design pattern used in modern software development. It is used to detect failures and encapsulates the logic of preventing a failure from constantly recurring, during maintenance, temporary external system failure or unexpected system difficulties.
 
-## Programmatic Example
+## Programmatic Example of Circuit Breaker Pattern in Java
+
+This Java example demonstrates how the Circuit Breaker pattern can manage remote service failures and maintain system stability.
 
 Imagine a web application that uses both local files/images and remote services to fetch data. Remote services can become slow or unresponsive, which may cause the application to hang due to thread starvation. The Circuit Breaker pattern can help detect such failures and allow the application to degrade gracefully.
 
@@ -172,13 +176,15 @@ Program output:
 
 This example demonstrates how the Circuit Breaker pattern can help maintain application stability and resilience by managing remote service failures.
 
-## Applicability
+## When to Use the Circuit Breaker Pattern in Java
+
+The Circuit Breaker pattern is applicable:
 
 * In distributed systems where individual service failures can lead to cascading system-wide failures
 * For applications that interact with third-party services or databases that might become unresponsive or slow
 * In microservices architectures where the failure of one service can affect the availability of others
 
-## Known Uses
+## Real-World Applications of Circuit Breaker Pattern in Java
 
 * Cloud-based services to gracefully handle the failure of external services
 * E-commerce platforms to manage high volumes of transactions and dependency on external APIs
@@ -186,12 +192,12 @@ This example demonstrates how the Circuit Breaker pattern can help maintain appl
 * [Spring Circuit Breaker module](https://spring.io/guides/gs/circuit-breaker)
 * [Netflix Hystrix API](https://github.com/Netflix/Hystrix)
 
-## Consequences
+## Benefits and Trade-offs of Circuit Breaker Pattern
 
 Benefits:
 
 * Prevents the system from performing futile operations that are likely to fail, thus saving resources
-* Helps in maintaining the stability and performance of the application during partial system failures
+* Helps in maintaining the system stability and performance of the application during partial system failures
 * Facilitates faster system recovery by avoiding the overwhelming of failing services with repeated requests
 
 Trade-Offs:
@@ -205,7 +211,7 @@ Trade-Offs:
 - Bulkhead: Can be used to isolate different parts of the system to prevent failures from spreading across the system
 - [Retry Pattern](https://github.com/iluwatar/java-design-patterns/tree/master/retry): Can be used in conjunction with the Circuit Breaker pattern to retry failed operations before opening the circuit
 
-## Credits
+## References and Credits
 
 * [Building Microservices: Designing Fine-Grained Systems](https://amzn.to/43Dx86g)
 * [Microservices Patterns: With examples in Java](https://amzn.to/3xaZwk0)