diff --git a/d9/d7c/md__2github_2workspace_2CHANGELOG.html b/d9/d7c/md__2github_2workspace_2CHANGELOG.html
index 3faacfff3..72c1d4bf0 100644
--- a/d9/d7c/md__2github_2workspace_2CHANGELOG.html
+++ b/d9/d7c/md__2github_2workspace_2CHANGELOG.html
@@ -103,7 +103,7 @@
 <div class="textblock"><p><a class="anchor" id="autotoc_md3"></a> </p>
 <h2><a class="anchor" id="autotoc_md4"></a>
 NexRes v1.8.0 (&lt;a href="https://github.com/resilientdb/resilientdb/releases/tag/nexres-v1.8.0" &gt;2023-08-21&lt;/a&gt;)</h2>
-<p><b>Implemented Enhancements:</b> View-Change algorithm in PBFT was added. Now PBFT-performance in NexRes is resilient to the following Byzantine behaviors and can replace primary and recover via the view-change algorithm. (<a href="https://github.com/DakaiKang">Dakai Kang</a>)</p>
+<p><b>Implemented Enhancements:</b> The view-change recovery protocol was extensively expanded to support the following Byzantine failures through primary/leader replacement and replica recovery. (<a href="https://github.com/DakaiKang">Dakai Kang</a>)</p>
 <ul>
 <li>Byzantine primary becomes non-responsive, stopping proposing any new Pre-Prepare messages.</li>
 <li>Byzantine primary equivocates, proposing two different client requests to two subsets of replicas.</li>