deploy: 8efc7a3

experimental/alt-da.html

@@ -259,7 +259,7 @@ <h2 id="da-server"><a class="header" href="#da-server">DA Server</a></h2>
 Content addressed systems like S3 should use the first <code>put/&lt;hex_encoded_commitment&gt;</code>
 because they can pre-commpute the commitment.
 Blockchain based DA layers should use <code>put</code> and then submit the returned commitment to L1.
-Because commitments can includ the block height or hash, the commitment cannot be computed prior to submitting
+Because commitments can include the block height or hash, the commitment cannot be computed prior to submitting
 it to the DA Layer.</p>
 <p>Any DA provider can implement the following endpoints to receive and serve input data:</p>
 <ul>
@@ -419,7 +419,7 @@ <h2 id="safety-and-finality"><a class="header" href="#safety-and-finality">Safet
 <p>Similarly to rollup mode, the engine queue labels any new blocks derived from input data with a commitment
 on the L1 chain as “safe”. Although labeled as “safe”, the chain might still reorg in case of a faulty DA provider
 and users must use the “finalized” label for a guarantee that their state cannot revert.</p>
-<p>With Alt-DA mode on, the engine queue does receives finality signals from the L1 RPC AND
+<p>With Alt-DA mode on, the engine queue does receive finality signals from the L1 RPC AND
 from the DA manager that keeps track of challenges.
 The DA manager maintains an internal state of all the input commitments in the current <code>challengeWindow</code>
 as they are validated by the derivation pipeline.</p>

print.html

@@ -8001,7 +8001,7 @@ <h2 id="da-server"><a class="header" href="#da-server">DA Server</a></h2>
 Content addressed systems like S3 should use the first <code>put/&lt;hex_encoded_commitment&gt;</code>
 because they can pre-commpute the commitment.
 Blockchain based DA layers should use <code>put</code> and then submit the returned commitment to L1.
-Because commitments can includ the block height or hash, the commitment cannot be computed prior to submitting
+Because commitments can include the block height or hash, the commitment cannot be computed prior to submitting
 it to the DA Layer.</p>
 <p>Any DA provider can implement the following endpoints to receive and serve input data:</p>
 <ul>
@@ -8161,7 +8161,7 @@ <h2 id="safety-and-finality"><a class="header" href="#safety-and-finality">Safet
 <p>Similarly to rollup mode, the engine queue labels any new blocks derived from input data with a commitment
 on the L1 chain as “safe”. Although labeled as “safe”, the chain might still reorg in case of a faulty DA provider
 and users must use the “finalized” label for a guarantee that their state cannot revert.</p>
-<p>With Alt-DA mode on, the engine queue does receives finality signals from the L1 RPC AND
+<p>With Alt-DA mode on, the engine queue does receive finality signals from the L1 RPC AND
 from the DA manager that keeps track of challenges.
 The DA manager maintains an internal state of all the input commitments in the current <code>challengeWindow</code>
 as they are validated by the derivation pipeline.</p>