Update unreleased documentation (#659)

* Update versions.json

* Deployed aa9b9de to unreleased in versions with MkDocs 1.5.3 and mike 2.0.0

* Sort docs versions

---------

Co-authored-by: GitHub Actions Bot <[email protected]>

versions/unreleased/guides/prefect-deploy/index.html

@@ -9656,7 +9656,7 @@ <h3 id="store-your-code-in-cloud-provider-storage">Store your code in cloud prov
 </span><span class="hll">        <span class="n">entrypoint</span><span class="o">=</span><span class="s2">&quot;flows.py:my_flow&quot;</span><span class="p">,</span>
 </span>    <span class="p">)</span><span class="o">.</span><span class="n">deploy</span><span class="p">(</span>
         <span class="n">name</span><span class="o">=</span><span class="s2">&quot;deployment-from-aws-flow&quot;</span><span class="p">,</span>
-        <span class="n">work_pool</span><span class="o">=</span><span class="s2">&quot;my_pool&quot;</span><span class="p">,</span>
+        <span class="n">work_pool_name</span><span class="o">=</span><span class="s2">&quot;my_pool&quot;</span><span class="p">,</span>
     <span class="p">)</span>
 </code></pre></div>
 <p>In the example above your credentials will be auto-discovered from your deployment creation environment and credentials will need to be available in your runtime environment.</p>
@@ -9669,7 +9669,7 @@ <h3 id="store-your-code-in-cloud-provider-storage">Store your code in cloud prov
 <span class="k">if</span> <span class="vm">__name__</span> <span class="o">==</span> <span class="s2">&quot;__main__&quot;</span><span class="p">:</span>
 <span class="hll">    <span class="n">flow</span><span class="o">.</span><span class="n">from_source</span><span class="p">(</span>
 </span><span class="hll">        <span class="n">source</span><span class="o">=</span><span class="n">S3Bucket</span><span class="o">.</span><span class="n">load</span><span class="p">(</span><span class="s2">&quot;my-code-storage&quot;</span><span class="p">),</span> <span class="n">entrypoint</span><span class="o">=</span><span class="s2">&quot;my_file.py:my_flow&quot;</span>
-</span><span class="hll">    <span class="p">)</span><span class="o">.</span><span class="n">deploy</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s2">&quot;test-s3&quot;</span><span class="p">,</span> <span class="n">work_pool</span><span class="o">=</span><span class="s2">&quot;my_pool&quot;</span><span class="p">)</span>
+</span><span class="hll">    <span class="p">)</span><span class="o">.</span><span class="n">deploy</span><span class="p">(</span><span class="n">name</span><span class="o">=</span><span class="s2">&quot;test-s3&quot;</span><span class="p">,</span> <span class="n">work_pool_name</span><span class="o">=</span><span class="s2">&quot;my_pool&quot;</span><span class="p">)</span>
 </span></code></pre></div>
 <p>If you are familiar with the deployment creation mechanics with <code>.serve</code>, you will notice that <code>.deploy</code> is very similar. <code>.deploy</code> just requires a work pool name and has a number of parameters dealing with flow-code storage for Docker images.</p>
 <p>Unlike <code>.serve</code>, if you don't specify an image to use for your flow, you must to specify where to pull the flow code from at runtime with the <code>from_source</code> method, whereas <code>from_source</code> is optional with <code>.serve</code>.</p>