[CI] Refresh EverParse doc

everparse/3d-lang.html

@@ -512,8 +512,10 @@ <h3>Singleton arrays of variable size<a class="headerlink" href="#singleton-arra
 <ul class="simple">
 <li><code class="docutils literal notranslate"><span class="pre">T</span> <span class="pre">f[:byte-size-single-element-array-at-most</span> <span class="pre">n]</span></code></li>
 </ul>
-<p>similar to the previous form, but where <code class="docutils literal notranslate"><span class="pre">n</span></code> is an upper bound on the
-size in bytes.</p>
+<p>which describes a field <code class="docutils literal notranslate"><span class="pre">f</span></code> that contains a single element of type
+<code class="docutils literal notranslate"><span class="pre">T</span></code> occupying at most <code class="docutils literal notranslate"><span class="pre">n</span></code> bytes, followed by padding bytes to make
+up to <code class="docutils literal notranslate"><span class="pre">n</span></code> bytes. This construct thus always consumes exactly <code class="docutils literal notranslate"><span class="pre">n</span></code>
+bytes.</p>
 <p>We expect to add several other kinds of variable-length array-like
 types in the uture.</p>
 </div>

everparse/_sources/3d-lang.rst.txt

@@ -374,8 +374,10 @@ A variation is:
 
 * ``T f[:byte-size-single-element-array-at-most n]``
 
-similar to the previous form, but where ``n`` is an upper bound on the
-size in bytes.
+which describes a field ``f`` that contains a single element of type
+``T`` occupying at most ``n`` bytes, followed by padding bytes to make
+up to ``n`` bytes. This construct thus always consumes exactly ``n``
+bytes.
 
 We expect to add several other kinds of variable-length array-like
 types in the uture.