Deployed 9fb8e2a to dev with MkDocs 1.6.1 and mike 2.1.3

Author: HHDocs

dev/search/search_index.json

@@ -1719,7 +1719,7 @@ <h2 id="system-requirements">System Requirements</h2>
 <p>The following packages needs to be installed: <code>qemu-kvm socat</code>. Docker is also required, to login
 into the OCI registry.</p>
 <p>By default, the VLAB topology is Spine-Leaf with 2 spines, 2 MCLAG leaves, 2 ESLAG leaves, and 1 "orphan" leaf, i.e. with
-no redundancy scheme. Alternatively, users can run the experimental mesh topology, which directly connects as few as 2 leaves
+no redundancy scheme. Alternatively, users can run the mesh topology, which directly connects as few as 2 leaves
 to each other, without the need for a spine switch in between.</p>
 <p>You can calculate the system requirements based on the allocated resources to the VMs using the following table:</p>
 <table>

dev/vlab/demo/index.html

@@ -1987,7 +1987,7 @@ <h3 id="spine-leaf">Spine-Leaf</h3>
 style Spine_02_Group fill:none,stroke:none</code></pre>
 <p>You can jump <a href="#build-the-installer-and-start-vlab">to the instructions</a> to start VLAB, or see the next section for customizing the topology.</p>
 <h3 id="mesh">Mesh</h3>
-<p>To run the experimental mesh topology, which does away with spine switches and connects leaves directly to each other,
+<p>To run the mesh topology, which does away with spine switches and connects leaves directly to each other,
 use the <code>--mesh-links-count</code> flag.
 This flag allows you to specify how many mesh links should be created between each pair of leaves.
 For example, to create a mesh topology with 2 links between each pair of leaves, run:</p>

dev/vlab/overview/index.html

@@ -1719,7 +1719,7 @@ <h2 id="system-requirements">System Requirements</h2>
 <p>The following packages needs to be installed: <code>qemu-kvm socat</code>. Docker is also required, to login
 into the OCI registry.</p>
 <p>By default, the VLAB topology is Spine-Leaf with 2 spines, 2 MCLAG leaves, 2 ESLAG leaves, and 1 "orphan" leaf, i.e. with
-no redundancy scheme. Alternatively, users can run the experimental mesh topology, which directly connects as few as 2 leaves
+no redundancy scheme. Alternatively, users can run the mesh topology, which directly connects as few as 2 leaves
 to each other, without the need for a spine switch in between.</p>
 <p>You can calculate the system requirements based on the allocated resources to the VMs using the following table:</p>
 <table>

dev/vlab/running/index.html

@@ -1987,7 +1987,7 @@ <h3 id="spine-leaf">Spine-Leaf</h3>
 style Spine_02_Group fill:none,stroke:none</code></pre>
 <p>You can jump <a href="#build-the-installer-and-start-vlab">to the instructions</a> to start VLAB, or see the next section for customizing the topology.</p>
 <h3 id="mesh">Mesh</h3>
-<p>To run the experimental mesh topology, which does away with spine switches and connects leaves directly to each other,
+<p>To run the mesh topology, which does away with spine switches and connects leaves directly to each other,
 use the <code>--mesh-links-count</code> flag.
 This flag allows you to specify how many mesh links should be created between each pair of leaves.
 For example, to create a mesh topology with 2 links between each pair of leaves, run:</p>