Update docs

Author: github-actions[bot]

_sources/autoapi/tilelang/language/overrides/index.rst.txt

@@ -8,7 +8,7 @@ tilelang.language.overrides
    TileLang-specific runtime overrides.
 
    Importing this package registers custom handlers that extend or override
-   behaviour from upstream TVMScript for TileLang semantics.
+   behavior from upstream TVMScript for TileLang semantics.
 
 
 

_sources/compiler_internals/inject_fence_proxy.md.txt

@@ -4,7 +4,7 @@
 
 ## Why Fences Are Needed
 
-Hopper separates memory instructions into generic and asynchronous proxy paths. When an asynchronous instruction (for example, `cp.async` or `tma.load`) issues after generic traffic (like `ldmatrix` or plain buffer stores), the hardware requires a `fence.proxy.async` to guarantee ordering. Missing fences can lead to race conditions or undefined behaviour.
+Hopper separates memory instructions into generic and asynchronous proxy paths. When an asynchronous instruction (for example, `cp.async` or `tma.load`) issues after generic traffic (like `ldmatrix` or plain buffer stores), the hardware requires a `fence.proxy.async` to guarantee ordering. Missing fences can lead to race conditions or undefined behavior.
 
 ## What the Pass Does
 

autoapi/tilelang/language/overrides/index.html

@@ -480,7 +480,7 @@
 <span id="tilelang-language-overrides"></span><h1>tilelang.language.overrides<a class="headerlink" href="#module-tilelang.language.overrides" title="Link to this heading">¶</a></h1>
 <p>TileLang-specific runtime overrides.</p>
 <p>Importing this package registers custom handlers that extend or override
-behaviour from upstream TVMScript for TileLang semantics.</p>
+behavior from upstream TVMScript for TileLang semantics.</p>
 </section>
 
         </article>

compiler_internals/inject_fence_proxy.html

@@ -481,7 +481,7 @@ <h1>InjectFenceProxy Pass<a class="headerlink" href="#injectfenceproxy-pass" tit
 <p><code class="docutils literal notranslate"><span class="pre">tl.InjectFenceProxy</span></code> is a TIR-level transform that keeps the GPU proxy state consistent on NVIDIA Hopper (SM90+) by inserting <code class="docutils literal notranslate"><span class="pre">fence.proxy.async</span></code> instructions when control flow switches from generic memory operations to asynchronous proxy operations.</p>
 <section id="why-fences-are-needed">
 <h2>Why Fences Are Needed<a class="headerlink" href="#why-fences-are-needed" title="Link to this heading">¶</a></h2>
-<p>Hopper separates memory instructions into generic and asynchronous proxy paths. When an asynchronous instruction (for example, <code class="docutils literal notranslate"><span class="pre">cp.async</span></code> or <code class="docutils literal notranslate"><span class="pre">tma.load</span></code>) issues after generic traffic (like <code class="docutils literal notranslate"><span class="pre">ldmatrix</span></code> or plain buffer stores), the hardware requires a <code class="docutils literal notranslate"><span class="pre">fence.proxy.async</span></code> to guarantee ordering. Missing fences can lead to race conditions or undefined behaviour.</p>
+<p>Hopper separates memory instructions into generic and asynchronous proxy paths. When an asynchronous instruction (for example, <code class="docutils literal notranslate"><span class="pre">cp.async</span></code> or <code class="docutils literal notranslate"><span class="pre">tma.load</span></code>) issues after generic traffic (like <code class="docutils literal notranslate"><span class="pre">ldmatrix</span></code> or plain buffer stores), the hardware requires a <code class="docutils literal notranslate"><span class="pre">fence.proxy.async</span></code> to guarantee ordering. Missing fences can lead to race conditions or undefined behavior.</p>
 </section>
 <section id="what-the-pass-does">
 <h2>What the Pass Does<a class="headerlink" href="#what-the-pass-does" title="Link to this heading">¶</a></h2>