[skip ci] deploy gh-pages

RFC-0330_Cerberus.html

@@ -295,7 +295,7 @@ <h2 id="cerberus-consensus---a-diagram"><a class="header" href="#cerberus-consen
 other shards that need to mark new substates as <code>Up</code> as a result of the transaction output.</li>
 </ol>
 <p>A mermaid flow diagram of the above process is shown below:</p>
-<pre><code class="language-mermaid">
+<pre class="mermaid">
 flowchart TD
     A[Client] --&gt; B([Broadcast transaction])
     B --&gt; C{Any tx inputs in my shard?}
@@ -344,7 +344,7 @@ <h2 id="cerberus-consensus---a-diagram"><a class="header" href="#cerberus-consen
     globalConsensus --&gt; GCD{Consensus on ACCEPT_*?}
     GCD --&gt; |No.| Stall[Abandon block!]
     GCD--&gt; |Yes| ssCommit{Decision == ACCEPT_COMMIT?}
-</code></pre>
+</pre>
 <p>The process above describes PCerberus in general, with some modifications from <a href="https://arxiv.org/pdf/1708.03778.pdf" title="Chainspace whitepaper">Chainspace</a>. There are a few details
 that need some additional explanation. In particular, this includes substate address derivation and state
 synchronisation.</p>

print.html

@@ -6863,7 +6863,7 @@ <h2 id="cerberus-consensus---a-diagram"><a class="header" href="#cerberus-consen
 other shards that need to mark new substates as <code>Up</code> as a result of the transaction output.</li>
 </ol>
 <p>A mermaid flow diagram of the above process is shown below:</p>
-<pre><code class="language-mermaid">
+<pre class="mermaid">
 flowchart TD
     A[Client] --&gt; B([Broadcast transaction])
     B --&gt; C{Any tx inputs in my shard?}
@@ -6912,7 +6912,7 @@ <h2 id="cerberus-consensus---a-diagram"><a class="header" href="#cerberus-consen
     globalConsensus --&gt; GCD{Consensus on ACCEPT_*?}
     GCD --&gt; |No.| Stall[Abandon block!]
     GCD--&gt; |Yes| ssCommit{Decision == ACCEPT_COMMIT?}
-</code></pre>
+</pre>
 <p>The process above describes PCerberus in general, with some modifications from <a href="https://arxiv.org/pdf/1708.03778.pdf" title="Chainspace whitepaper">Chainspace</a>. There are a few details
 that need some additional explanation. In particular, this includes substate address derivation and state
 synchronisation.</p>