Deployed a448d5d to 0.1.0 with MkDocs 1.6.1 and mike 2.1.3

Author: github-actions[bot]

0.1.0/40-operations/operations-overview/index.html

@@ -4141,7 +4141,7 @@ <h3 id="live-runtime">Live Runtime</h3>
 </ul>
 <p>This Runtime is operated by the Execution Stack.</p>
 <hr />
-<h2 id="trading-runtime-model">Trading Runtime Model</h2>
+<h2 id="core-runtime-model">Core Runtime Model</h2>
 <p>Both Runtimes execute the same event-driven trading core.</p>
 <p>The infrastructure processes Events sequentially and updates internal States based on those Events.</p>
 <p>The Runtime model follows a deterministic Event processing pipeline:</p>
@@ -4183,7 +4183,7 @@ <h2 id="event-processing-loop">Event Processing Loop</h2>
 <p>This event-driven feedback loop ensures consistent infrastructure behavior across both Backtesting and Live Runtimes.</p>
 <hr />
 <h2 id="runtime-components">Runtime Components</h2>
-<p>The Trading Runtime consists of several cooperating components.</p>
+<p>The Core Runtime consists of several cooperating components.</p>
 <h3 id="state-management">State Management</h3>
 <p>Maintains the internal State derived from processed Events.</p>
 <h3 id="strategy-layer">Strategy Layer</h3>

0.1.0/50-evolution/milestones/index.html

@@ -4338,7 +4338,7 @@ <h3 id="formal-documentation-and-project-structuring">Formal Documentation and P
 <p>Once the Core Runtime and supporting tooling existed, the focus moved to formalizing the architecture and making the project legible.</p>
 <p><strong>Main outcomes</strong></p>
 <ul>
-<li>Created the MkDocs-based architecture documentation</li>
+<li>Created this MkDocs-based architecture documentation</li>
 <li>Documented the semantic and conceptual model of the infrastructure rather than repository-level implementation details</li>
 <li>Structured documentation around architecture, concepts, Stacks, operations, and evolution</li>
 <li>Cleaned up project structure at the GitHub organization and repository level</li>