[CI] Publish Preview for PR #1 eaf1139

Author: github-actions[bot]

pull-1/sitemap.xml

@@ -2,22 +2,22 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/01-pattern.html</loc>
-<lastmod>2025-02-04T18:05:02.829Z</lastmod>
+<lastmod>2025-03-26T18:20:01.389Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/02-architecture.html</loc>
-<lastmod>2025-02-04T18:05:02.829Z</lastmod>
+<lastmod>2025-03-26T18:20:01.389Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/03-demo.html</loc>
-<lastmod>2025-02-04T18:05:02.829Z</lastmod>
+<lastmod>2025-03-26T18:20:01.389Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/developer-resources.html</loc>
-<lastmod>2025-02-04T18:05:02.829Z</lastmod>
+<lastmod>2025-03-26T18:20:01.389Z</lastmod>
 </url>
 <url>
 <loc>https://redhat-solution-patterns.github.io/solution-patterns/solution-pattern-event-mesh-for-microservices/index.html</loc>
-<lastmod>2025-02-04T18:05:02.829Z</lastmod>
+<lastmod>2025-03-26T18:20:01.389Z</lastmod>
 </url>
 </urlset>

pull-1/solution-pattern-event-mesh-for-microservices/02-architecture.html

@@ -177,7 +177,7 @@ <h2 id="tech_stack"><a class="anchor" href="#tech_stack"></a><a class="link" hre
 <li>
 <p><a href="https://www.redhat.com/en/technologies/cloud-computing/openshift">Red Hat OpenShift</a>
 &mdash; Orchestrate containerized applications.
-Based on <a href="https://kubernetes.io/">Kuberentes</a>.</p>
+Based on <a href="https://kubernetes.io/">Kubernetes</a>.</p>
 </li>
 <li>
 <p><a href="https://www.redhat.com/en/technologies/cloud-computing/openshift/serverless">Red Hat OpenShift Serverless</a>
@@ -267,7 +267,7 @@ <h3 id="_solution_breakdown"><a class="anchor" href="#_solution_breakdown"></a><
 This results in better alignment with business requirements, as it supports scenarios where multiple services collaborate and synchronize their operations, making the whole state eventually consistent, without the constraint of strict, synchronous consistency.</p>
 </li>
 <li>
-<p><strong>Avoidance of systemic issues</strong>:
+<p><strong>Improved Resilience</strong>:
 The <em>Event Mesh</em>'s error-handling mechanism, through retries and event persistence, aids in minimizing the impact of failures on the end user.
 This is crucial as it prevents bugs and outages from becoming visible to the user, thereby preserving the system&#8217;s perceived responsiveness.</p>
 </li>
@@ -290,11 +290,11 @@ <h3 id="_event_mesh_flow"><a class="anchor" href="#_event_mesh_flow"></a><a clas
 <div class="olist arabic">
 <ol class="arabic">
 <li>
-<p>An end-user application sends a request, which forms a <em>Command</em> type event, which is transferred to the <em>Event Mesh</em>.</p>
+<p>An end-user application sends an <em>HTTP</em> request to the <em>Event Mesh</em>. Such message can be understood as a <em>Command</em> type event.</p>
 </li>
 <li>
 <p>The <em>Event Mesh</em> (Broker) persists the event in a queue (e.g. Kafka).
-After successful persistence <em>Event Mesh</em> returns the success information.
+After <em>Event Mesh</em> persists safely the data, it returns a successful <em>HTTP</em> response with the <code>202 Accepted</code> return code.
 At this point, the operation could already be considered successful, from the end-user point of view.
 It will eventually settle correctly in all downstream systems.</p>
 </li>
@@ -307,7 +307,7 @@ <h3 id="_event_mesh_flow"><a class="anchor" href="#_event_mesh_flow"></a><a clas
 </li>
 <li>
 <p>The dispatch loop continues until the event queue is empty and all the events are processed successfully.
-The failures are being automatically retried by the <em>Event Mesh</em> using exponential backoff algorithm by default.</p>
+The failures are automatically retried by the <em>Event Mesh</em>, with an increasing pauses between retries to avoid overloading the system.</p>
 </li>
 </ol>
 </div>
@@ -362,9 +362,9 @@ <h3 id="_event_mesh_flow"><a class="anchor" href="#_event_mesh_flow"></a><a clas
 <h3 id="_work_ledger_analogy"><a class="anchor" href="#_work_ledger_analogy"></a><a class="link" href="#_work_ledger_analogy">2.4. <em>Work Ledger</em> analogy</a></h3>
 <div class="paragraph">
 <p>A good way of thinking about the <em>Event Mesh</em> and its persistent queue backend is the <em>Work Ledger</em> analogy.
-Like in olden days, the clerk was keeping his to-do work in the <em>Work Ledger</em> (e.g. a tray for paper forms).
+Like in the olden days, the clerk kept his to-do work in the <em>Work Ledger</em> (e.g. a tray for paper forms).
 Then he was picking the next form, and processing it, making changes within the physical file cabinets.
-In case of rare and unexpected issues (e.g. Invoicing dept being unavailable), the clerk would just put the data back onto the <em>Work Ledger</em> to be processed later.</p>
+In case of rare and unexpected issues (e.g. invoicing dept being unavailable), the clerk would just put the data back onto the <em>Work Ledger</em> to be processed later.</p>
 </div>
 <div class="paragraph">
 <p>The <em>Event Mesh</em> is processing the data in very similar fashion.

pull-1/solution-pattern-event-mesh-for-microservices/03-demo.html

@@ -519,7 +519,7 @@ <h4 id="_legacy_application_changes"><a class="anchor" href="#_legacy_applicatio
 We also need to accept new events coming from the <em>Event Mesh</em>, as the calculated fee will be transmitted as such.</p>
 </div>
 <div class="paragraph">
-<p>Here&#8217;s the refactored <code>completeTransit</code> method:</p>
+<p>Here&#8217;s the refactored code:</p>
 </div>
 <div class="listingblock">
 <div class="content">

pull-1/solution-pattern-event-mesh-for-microservices/developer-resources.html

@@ -155,7 +155,7 @@ <h2 id="_developer_resources"><a class="anchor" href="#_developer_resources"></a
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://github.com/cardil/cabs-usvc">cardil / cabs-usvc</a> <em>(The example code used in this solution)</em></p>
+<p><a href="https://github.com/cardil/cabs-usvc">Demo Source</a> <em>(The example code used in this solution)</em></p>
 </li>
 <li>
 <p><a href="https://youtu.be/Rc5IO6S6ZOk">youtu.be / Rc5IO6S6ZOk</a> <em>(The talk that served a base for this solution)</em></p>

pull-1/solution-pattern-event-mesh-for-microservices/index.html

@@ -160,7 +160,7 @@ <h1 class="page">Building Apps around the Event Mesh</h1>
 <p>This solution pattern is written to make it obvious and to show simple, yet
 elegant, correct, and comprehensive way of building software, either in
 greenfield or even in legacy projects. This solution leverages the
-<a href="https://www.redhat.com/en/technologies/cloud-computing/openshift/serverless">Red Hat Serverless</a>
+<a href="https://www.redhat.com/en/technologies/cloud-computing/openshift/serverless">Red Hat OpenShift Serverless</a>
 Eventing component, which implements the <a href="https://www.redhat.com/en/topics/integration/what-is-an-event-mesh">Event Mesh</a> pattern.</p>
 </div>
 <div class="paragraph">