Improving article (#358)

* Improving article
* Minor upgrade

Author: jabrena

docs/blog/2025/09/release-0.11.0.html

@@ -160,10 +160,11 @@ <h2> Why decouple Pure System prompts from specialized behaviors?</h2>
 <li><a href="https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-consultative-interaction.md"><code>@behaviour-consultative-interaction</code></a></li>
 <li><a href="https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-progressive-learning.md"><code>@behaviour-progressive-learning</code></a></li>
 </ul>
-<p>With this design change applied into the different system prompts, you can use them in your <code>Data pipelines</code> for different use cases such as <code>automatic coding</code>, <code>code refactoring</code>, <code>continuous profiling</code>, and more.</p>
+<hr />
+<p>After this design change applied into the different system prompts, you can use them in your <code>Data pipelines</code> for different use cases such as <code>automatic coding</code>, <code>code refactoring</code>, <code>continuous profiling</code>, and more.</p>
 <p><img src="/cursor-rules-java/images/data-pipeline-workflow.png" alt="" /></p>
 <h2>New UML state machine diagrams for better understanding in complex dependencies.</h2>
-<p>Sometimes you need to use complex dependencies in your projects, like Apache Kafka clients, and the team may not be strong enough in the early stages. If you don't have much experience with them, a good practice is to run a spike and review how the client works under the hood to mitigate risks.</p>
+<p>Sometimes you need to use complex dependencies in your projects, like Apache Kafka clients, and the team may not be strong enough in the early stages. If you don't have much experience with them, a good practice is to run a <code>spike</code> and review how the client works under the hood to mitigate risks.</p>
 <p>During the spike, you may need to visualize internal aspects of the clients, so why not generate a <code>UML state machine diagram</code> to gain more insights.</p>
 <p><strong>Examples:</strong></p>
 <pre><code>Create UML class diagrams with @171-java-diagrams without any questions from

docs/feed.xml

@@ -2,7 +2,7 @@
 <feed xmlns='http://www.w3.org/2005/Atom' xml:lang='en'>
   <id>https://jabrena.github.io/cursor-rules-java/</id>
   <title>Cursor Rules for Java</title>
-  <updated>2025-09-27T20:29:10+0200</updated>
+  <updated>2025-09-27T20:36:06+0200</updated>
   <link rel="alternate" type="text/html" href="https://jabrena.github.io/cursor-rules-java/" />
   <link rel='self' type='application/atom+xml' href='https://jabrena.github.io/cursor-rules-java//feed.xml' />
   <entry>

site-generator/content/blog/2025/09/release-0.11.0.md

@@ -100,13 +100,15 @@ With this evolution, software engineers now can combine pure system prompts and
 - [`@behaviour-consultative-interaction`](https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-consultative-interaction.md)
 - [`@behaviour-progressive-learning`](https://github.com/jabrena/cursor-rules-java/blob/main/.cursor/rules/behaviour-progressive-learning.md)
 
-With this design change applied into the different system prompts, you can use them in your `Data pipelines` for different use cases such as `automatic coding`, `code refactoring`, `continuous profiling`, and more.
+---
+
+After this design change applied into the different system prompts, you can use them in your `Data pipelines` for different use cases such as `automatic coding`, `code refactoring`, `continuous profiling`, and more.
 
 ![](/cursor-rules-java/images/data-pipeline-workflow.png)
 
 ## New UML state machine diagrams for better understanding in complex dependencies.
 
-Sometimes you need to use complex dependencies in your projects, like Apache Kafka clients, and the team may not be strong enough in the early stages. If you don't have much experience with them, a good practice is to run a spike and review how the client works under the hood to mitigate risks.
+Sometimes you need to use complex dependencies in your projects, like Apache Kafka clients, and the team may not be strong enough in the early stages. If you don't have much experience with them, a good practice is to run a `spike` and review how the client works under the hood to mitigate risks.
 
 During the spike, you may need to visualize internal aspects of the clients, so why not generate a `UML state machine diagram` to gain more insights.