chore: regenerate docs

docs/advanced-usage/registry-management/index.html

@@ -3647,7 +3647,7 @@ <h3 id="specifying-an-image-repository-name">Specifying an image repository name
 </code></pre></div>
 <p>Setting the property value to an empty string will reset the value to the system default. Resetting the value has to be done per-app.</p>
 <div class="highlight"><pre><span></span><code><a id="__codelineno-7-1" name="__codelineno-7-1" href="#__codelineno-7-1"></a><span class="c1"># per-app</span>
-<a id="__codelineno-7-2" name="__codelineno-7-2" href="#__codelineno-7-2"></a>dokku<span class="w"> </span>registry:set<span class="w"> </span>node-js-app<span class="w"> </span>push-on-release
+<a id="__codelineno-7-2" name="__codelineno-7-2" href="#__codelineno-7-2"></a>dokku<span class="w"> </span>registry:set<span class="w"> </span>node-js-app<span class="w"> </span>image-repo
 </code></pre></div>
 <h3 id="pushing-images-on-build">Pushing images on build<a class="headerlink" href="#pushing-images-on-build" title="Permanent link">&para;</a></h3>
 <p>To push the image on release, set the <code>push-on-release</code> property to <code>true</code> via the <code>registry:set</code> command. The default value for this property is <code>false</code>. Setting the property to <code>true</code> will result in the image being tagged with an ID that is incremented with every release. This tag will be what is used for running app code.</p>

docs/deployment/schedulers/docker-local/index.html

@@ -3773,7 +3773,7 @@ <h4 id="increasing-parallelism-within-a-process-deploy">Increasing parallelism w
 <a id="__codelineno-9-9" name="__codelineno-9-9" href="#__codelineno-9-9"></a><span class="w">  </span><span class="p">}</span>
 <a id="__codelineno-9-10" name="__codelineno-9-10" href="#__codelineno-9-10"></a><span class="p">}</span>
 </code></pre></div>
-<p>Omitting or removing the entry will result in parallelism for that process type to return to 1 entry at a time. This can be combined with the  <code>parallel-schedule-count</code> property to speed up deployments.</p>
+<p>Omitting or removing the entry will result in parallelism for that process type to return to 1 entry at a time. This can be combined with the <code>parallel-schedule-count</code> property to speed up deployments.</p>
 <p>Note that increasing the value of <code>max_parallel</code> may significantly impact CPU utilization on your host as your app containers - and their respective processes - start up. Setting a value higher than the number of available CPUs is discouraged. It is recommended that users carefully set this value so as not to overburden their server.</p>
 <p>See the <a href="../../../advanced-usage/deployment-tasks/#changing-the-appjson-location">app.json location documentation</a> for more information on where to place your <code>app.json</code> file.</p>
 <h2 id="scheduler-interface">Scheduler Interface<a class="headerlink" href="#scheduler-interface" title="Permanent link">&para;</a></h2>