Archive max-container-starts and migrating, update cf-release-eol [ai-assisted]

Made-with: Cursor

Author: anita-flegg

max-container-starts.html.md.erb archive/max-container-starts.html.md.erbmax-container-starts.html.md.erb renamed to archive/max-container-starts.html.md.erb

@@ -25,6 +25,6 @@ To configure the maximum number of started instances:
 
 1. Save the changes and re-deploy BOSH.
 
-<p class="terminal">diego.auctioneer.starting_container_count_maximum:<br/>
-    description: "Maximum number of inflight container starts allowed globally. Value of 0 or less indicates no limit."<br/>
-    default: Your-numerical-value-here</p>
+<pre class="terminal">diego.auctioneer.starting_container_count_maximum:
+    description: "Maximum number of inflight container starts allowed globally. Value of 0 or less indicates no limit."
+    default: Your-numerical-value-here</pre>

migrating.html.md.erb archive/migrating.html.md.erbmigrating.html.md.erb renamed to archive/migrating.html.md.erb

@@ -215,7 +215,7 @@ Perform the following steps:
     - name: z1
       cloud_properties:
         availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z1-RESOURCE-POOL
-    - name: z1
+    - name: z2
       cloud_properties:
         availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z2-RESOURCE-POOL
     - name: z3

cf-release-eol.html.md.erb

@@ -7,7 +7,7 @@ owner: Release Integration
 
 ## Next Steps
 
-* If you have an existing Cloud Foundry deployment that uses <code>cf-release</code>, see the <a href="./migrating.html">Migrating from cf-release to cf-deployment</a> topic.
+* If you have an existing Cloud Foundry deployment that uses <code>cf-release</code>, see the [cf-deployment documentation](https://github.com/cloudfoundry/cf-deployment) for migration guidance.
 
 * If you are deploying Cloud Foundry for the first time, see the <a href="./cf-deployment/index.html">Deploying Cloud Foundry with cf-deployment</a> topic.