Deployed 47ef677 to dev with MkDocs 1.6.1 and mike 2.1.3

Author: Doc Deploy Bot

dev/guides/user-interactions/readme/index.html

@@ -1735,7 +1735,7 @@ <h4 id="examples_3">Examples</h4>
 </code></pre></div>
 <p>This directive causes the <code>shared-data</code> persistent storage allocation to be mounted onto the compute nodes for the job application to use. The copy-offload API is expected to be used by the application.</p>
 <h3 id="copy_incopy_out">copy_in/copy_out</h3>
-<p>The <code>copy_in</code> and <code>copy_out</code> directives are used to move data to and from the storage allocations on Rabbit nodes. The <code>copy_in</code> directive requests that data be moved into the Rabbit file system before application launch, and the <code>copy_out</code> directive requests data to be moved off of the Rabbit file system after application exit. This is different from data-movement that is requested through the copy-offload API, which occurs during application runtime. Multiple <code>copy_in</code> and <code>copy_out</code> directives can be included in the same job script. More information about data movement can be found in the <a href="../../data-movement/readme/">Data Movement</a> documentation.</p>
+<p>The <code>copy_in</code> and <code>copy_out</code> directives are used to move data to and from the storage allocations on Rabbit nodes. The <code>copy_in</code> directive requests that data be moved into the Rabbit file system before application launch, and the <code>copy_out</code> directive requests data to be moved off of the Rabbit file system after application exit. Multiple <code>copy_in</code> and <code>copy_out</code> directives can be included in the same job script. This is different from data-movement that is requested through the copy-offload API, which occurs during application runtime. More information about data movement can be found in the <a href="../../data-movement/readme/">Data Movement</a> documentation.</p>
 <h4 id="command-arguments_4">Command Arguments</h4>
 <table>
 <thead>