Deployed 607d144 to nightly with MkDocs 1.4.3 and mike 1.1.2

nightly/configure-templates/index.html

@@ -1467,8 +1467,8 @@ <h2 id="object-templates">Object Templates<a class="headerlink" href="#object-te
 </code></pre></div>
 <p>After restarting your pollers, <code>aggr.yaml</code> and <code>custom_aggr.yaml</code> will be merged.</p>
 <h3 id="create-a-new-object-template">Create a new object template<a class="headerlink" href="#create-a-new-object-template" title="Permanent link">&para;</a></h3>
-<p>In this example, imagine that Harvest doesn't already collect environment sensor data and you wanted to collect it.
-Sensor does comes from the <code>environment-sensors-get-iter</code> ZAPI. Here are the steps to add a new object template.</p>
+<p>In this example, imagine that Harvest doesn't already collect environment sensor data, and you wanted to collect it.
+Sensor does come from the <code>environment-sensors-get-iter</code> ZAPI. Here are the steps to add a new object template.</p>
 <p>Create the file <code>conf/zapi/cdot/9.8.0/sensor.yaml</code> (optionally replace <code>9.8.0</code> with the earliest version of ONTAP that
 supports sensor data. Refer to <a href="./#harvest-versioned-templates">Harvest Versioned Templates</a> for
 more information. Add the following content to your new <code>sensor.yaml</code> file.</p>

nightly/install/containerd/index.html

@@ -1154,7 +1154,7 @@ <h1 id="setup">Setup<a class="headerlink" href="#setup" title="Permanent link">&
 <p>We're going to:
 - Install and Start <a href="https://rancherdesktop.io/">Rancher Desktop</a>
 - (Optional) Create Harvest Docker image by following Harvest's existing documentation
-- Generate a Compose file following Harvest' existing documentation
+- Generate a Compose file following Harvest existing documentation
 - Concatenate the Prometheus/Grafana compose file with the harvest compose file since Rancher doesn't support multiple compose files yet
   - Fixup the concatenated file
 - Start containers</p>
@@ -1170,7 +1170,7 @@ <h2 id="create-harvest-docker-image">Create Harvest Docker image<a class="header
 <div class="highlight"><pre><span></span><code>nerdctl<span class="w"> </span>build<span class="w"> </span>-f<span class="w"> </span>container/onePollerPerContainer/Dockerfile<span class="w"> </span>-t<span class="w"> </span>harvest:latest<span class="w"> </span>.<span class="w"> </span>--no-cache<span class="w"> </span>
 </code></pre></div>
 <h2 id="generate-a-harvest-compose-file">Generate a Harvest compose file<a class="headerlink" href="#generate-a-harvest-compose-file" title="Permanent link">&para;</a></h2>
-<p>Follow the existing documentation to setup your <code>harvest.yml</code> <a href="../containers/#setup-harvestyml">file</a></p>
+<p>Follow the existing documentation to set up your <code>harvest.yml</code> <a href="../containers/#setup-harvestyml">file</a></p>
 <p>Create your <code>harvest-compose.yml</code> file like this:</p>
 <div class="highlight"><pre><span></span><code>docker<span class="w"> </span>run<span class="w"> </span>--rm<span class="w"> </span><span class="se">\</span>
 <span class="w">  </span>--entrypoint<span class="w"> </span><span class="s2">&quot;bin/harvest&quot;</span><span class="w"> </span><span class="se">\</span>

nightly/install/podman/index.html

@@ -1345,7 +1345,7 @@ <h2 id="containerized-harvest-on-linux-using-rootless-podman_1">Containerized Ha
 <div class="highlight"><pre><span></span><code><span class="c1"># as root or sudo</span>
 usermod<span class="w"> </span>--append<span class="w"> </span>--groups<span class="w"> </span>wheel<span class="w"> </span>harvest
 </code></pre></div>
-<p>Login with the harvest user, setup the podman.socket, and make sure the curl below works. <code>su</code> or <code>sudo</code> aren't sufficient, you need to <code>ssh</code> into the machine as the harvest user or use <code>machinectl login</code>. See <a href="https://www.redhat.com/sysadmin/sudo-rootless-podman">sudo-rootless-podman</a> for details.</p>
+<p>Login with the harvest user, set up the podman.socket, and make sure the curl below works. <code>su</code> or <code>sudo</code> aren't sufficient, you need to <code>ssh</code> into the machine as the harvest user or use <code>machinectl login</code>. See <a href="https://www.redhat.com/sysadmin/sudo-rootless-podman">sudo-rootless-podman</a> for details.</p>
 <div class="highlight"><pre><span></span><code><span class="c1"># these must be run as the harvest user</span>
 systemctl<span class="w"> </span>--user<span class="w"> </span><span class="nb">enable</span><span class="w"> </span>podman.socket
 systemctl<span class="w"> </span>--user<span class="w"> </span>start<span class="w"> </span>podman.socket
@@ -1360,7 +1360,7 @@ <h2 id="containerized-harvest-on-linux-using-rootless-podman_1">Containerized Ha
 <span class="w">  </span>runRoot:<span class="w"> </span>/run/user/1001/containers
 </code></pre></div>
 <h2 id="running-harvest">Running Harvest<a class="headerlink" href="#running-harvest" title="Permanent link">&para;</a></h2>
-<p>By default, Cockpit runs on port 9090, same as Prometheus. We'll change Prometheus's host port to 9091 so we can run both Cockpit and Prometheus. Line <code>2</code> below does that.</p>
+<p>By default, Cockpit runs on port 9090, same as Prometheus. We'll change Prometheus's host port to 9091, so we can run both Cockpit and Prometheus. Line <code>2</code> below does that.</p>
 <p>With these changes, the <a href="../containers/#docker-compose">standard Harvest compose instructions</a> can be followed as normal now. In summary,</p>
 <ol>
 <li>Add the clusters, exporters, etc. to your <code>harvest.yml</code> file</li>
@@ -1406,7 +1406,7 @@ <h3 id="errors-after-rebooting">Errors after rebooting<a class="headerlink" href
 <div class="highlight"><pre><span></span><code>podman ps -a
 ERRO[0000] error joining network namespace for container 424df6c: error retrieving network namespace at /run/user/1001/netns/cni-5fb97adc-b6ef-17e8-565b-0481b311ba09: failed to Statfs &quot;/run/user/1001/netns/cni-5fb97adc-b6ef-17e8-565b-0481b311ba09&quot;: no such file or directory
 </code></pre></div>
-<p>Run <code>podman info</code> and make sure <code>runRoot</code> points to <code>/run/user/$UID/containers</code> (see below). If it instead points to <code>/tmp/podman-run-$UID</code> you will likely have problems when restarting the machine. Typically this happens because you used su to become the harvest user or ran podman as root. You can fix this by logging in as the <code>harvest</code> user and running <code>podman system reset</code>.</p>
+<p>Run <code>podman info</code> and make sure <code>runRoot</code> points to <code>/run/user/$UID/containers</code> (see below). If it instead points to <code>/tmp/podman-run-$UID</code> you will likely have problems when restarting the machine. Typically, this happens because you used su to become the harvest user or ran podman as root. You can fix this by logging in as the <code>harvest</code> user and running <code>podman system reset</code>.</p>
 <div class="highlight"><pre><span></span><code>podman<span class="w"> </span>info<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>runRoot
 <span class="w">  </span>runRoot:<span class="w"> </span>/run/user/1001/containers
 </code></pre></div>

nightly/prepare-cdot-clusters/index.html

@@ -1814,7 +1814,7 @@ <h2 id="create-client-certificates-for-password-less-login">Create Client Certif
 required to name the key/cert pair after the hostname, but if you do, Harvest will load them automatically when you
 specify <code>auth_style: certificate_auth</code> otherwise you can point to them directly.
 See <a href="https://github.com/NetApp/harvest#pollers">Pollers</a> for details.</p>
-<p>Change the common name to the ONTAP user you setup with the harvest role above. e.g <code>harvest2</code></p>
+<p>Change the common name to the ONTAP user you set up with the harvest role above. e.g <code>harvest2</code></p>
 <div class="highlight"><pre><span></span><code>cd /opt/harvest
 mkdir cert
 openssl req -x509 -nodes -days 1095 -newkey rsa:2048 -keyout cert/$(hostname).key -out cert/$(hostname).pem -subj &quot;/CN=harvest2&quot;