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

private-class-data/README.md

@@ -1,11 +1,13 @@
 ---
-title: Private Class Data
+title: "Private Class Data Pattern in Java: Safeguarding Data Integrity with Encapsulation"
+shortTitle: Private Class Data
+description: "Explore the Private Class Data pattern in Java, ideal for enhancing data security and integrity in object-oriented programming. Learn how it prevents unintended data manipulation with encapsulation."
 category: Structural
 language: en
 tag:
-    - Abstraction
-    - Encapsulation
-    - Security
+  - Abstraction
+  - Encapsulation
+  - Security
 ---
 
 ## Also known as
@@ -13,11 +15,11 @@ tag:
 * Data Hiding
 * Encapsulation
 
-## Intent
+## Intent of Private Class Data Design Pattern
 
-The Private Class Data design pattern aims to restrict access to the internal state of an object by providing controlled access through methods, thereby increasing security and reducing accidental data corruption.
+The Private Class Data design pattern in Java focuses on restricting access to the internal state of an object, enhancing security and reducing risks of data corruption through controlled method access.
 
-## Explanation
+## Detailed Explanation of Private Class Data Pattern with Real-World Examples
 
 Real-world example
 
@@ -31,7 +33,7 @@ Wikipedia says
 
 > Private class data is a design pattern in computer programming used to encapsulate class attributes and their manipulation.
 
-**Programmatic Example**
+## Programmatic Example of Private Class Data Pattern in Java
 
 Imagine you are cooking a stew for your family dinner. You want to stop your family members from tasting the stew while you're still preparing it. If they do, there might not be enough stew left for dinner.
 
@@ -123,7 +125,7 @@ Program output:
 08:00:08.213 [main] INFO com.iluwatar.privateclassdata.ImmutableStew -- Mixing the immutable stew we find: 2 potatoes, 4 carrots, 3 meat and 6 peppers
 ```
 
-## Applicability
+## When to Use the Private Class Data Pattern in Java
 
 Use the Private Class Data pattern when
 
@@ -131,13 +133,13 @@ Use the Private Class Data pattern when
 * When you need to limit the visibility of the internal data of an object to prevent unintended modification.
 * In scenarios where multiple classes need to share access to some common data without exposing it directly.
 
-## Known Uses
+## Real-World Applications of Private Class Data Pattern in Java
 
 * Java Beans, where properties are accessed via getters and setters.
 * In many Java libraries where the internal state is hidden from the user to ensure consistency and security.
 * Enterprise applications where sensitive data needs to be protected from direct access.
 
-## Consequences
+## Benefits and Trade-offs of Private Class Data Pattern
 
 Benefits:
 
@@ -150,13 +152,13 @@ Trade-offs:
 * Performance Overhead: Additional method calls (getters/setters) can introduce slight performance overhead.
 * Complexity: May increase the complexity of the class design due to the additional layer of methods for data access.
 
-## Related Patterns
+## Related Java Design Patterns
 
 * [Proxy](https://java-design-patterns.com/patterns/proxy/): Both patterns restrict access to the underlying object but Proxy controls access to the object itself, while Private Class Data controls access to the data.
 * [Singleton](https://java-design-patterns.com/patterns/singleton/): Ensures that a class has only one instance and provides a global point of access to it; often used to manage shared data with controlled access.
 * [Decorator](https://java-design-patterns.com/patterns/decorator/): Adds behavior to an object without altering its structure; can be combined with Private Class Data to manage additional state privately.
 
-## Credits
+## References and Credits
 
 * [Clean Code: A Handbook of Agile Software Craftsmanship](https://amzn.to/3UJTZJk)
 * [Design Patterns: Elements of Reusable Object-Oriented Software](https://amzn.to/3w0pvKI)