fix blockers

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/TOC.yml

@@ -43,7 +43,7 @@
     href: ./durable-task-scheduler/quickstart-durable-task-scheduler.md
   - name: Configure a container app with Durable Task SDK and Durable Task Scheduler
     displayName: get started, durable task scheduler
-    href: ./durable-task-scheduler/quickstart-aca-azd-durable-task-sdk.md
+    href: ./durable-task-scheduler/quickstart-container-apps-durable-task-sdk.md
   - name: Configure Durable Functions app with MSSQL
     href: quickstart-mssql.md
   - name: Configure Durable Functions app with managed identity
@@ -133,7 +133,7 @@
     - name: How-to guides
       items:
       - name: Autoscaling with the Durable Task SDKs in Azure Container Apps
-        href: ./durable-task-scheduler/durable-task-scheduler-auto-scaling-aca.md
+        href: ./durable-task-scheduler/durable-task-scheduler-auto-scaling.md
   - name: Billing
     href: ./durable-task-scheduler/durable-task-scheduler-dedicated-sku.md
   - name: Troubleshoot

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-scaling-aca.md renamed to articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-auto-scaling.md

@@ -171,15 +171,15 @@ In the Azure portal, verify the orchestrations are running successfully.
 
 1. Confirm the client container is logging the function chaining tasks.
 
-   :::image type="content" source="media/quickstart-aca-azd-durable-task-sdk/client-app-log-stream.png" alt-text="Screenshot of the client container's log stream in the Azure portal.":::
+   :::image type="content" source="media/quickstart-container-apps-durable-task-sdk/client-app-log-stream.png" alt-text="Screenshot of the client container's log stream in the Azure portal.":::
 
 1. Navigate back to the resource group page to select the `worker` container. 
 
 1. Select **Monitoring** > **Log stream**.
 
 1. Confirm the worker container is logging the function chaining tasks.
 
-   :::image type="content" source="media/quickstart-aca-azd-durable-task-sdk/worker-app-log-stream.png" alt-text="Screenshot of the worker container's log stream in the Azure portal.":::
+   :::image type="content" source="media/quickstart-container-apps-durable-task-sdk/worker-app-log-stream.png" alt-text="Screenshot of the worker container's log stream in the Azure portal.":::
 
 ::: zone-end
 

articles/azure-functions/durable/durable-task-scheduler/media/quickstart-container-apps-durable-task-sdk/client-app-log-stream.png

@@ -65,7 +65,7 @@ Before you begin:
 
 ## Set up the Durable Task Scheduler emulator
 
-The application code looks for a deployed scheduler and task hub resource. If none are found, the code falls back to the emulator. The emulator simulates a scheduler and task hub in a Docker container, making it ideal for the local development required in this quickstart.
+The application code looks for a deployed scheduler and task hub resource. If none is found, the code falls back to the emulator. The emulator simulates a scheduler and task hub in a Docker container, making it ideal for the local development required in this quickstart.
 
 ::: zone-end
 
@@ -705,4 +705,4 @@ logger.info("Output: {}", completedInstance.readOutputAs(int.class));
 Now that you've run the sample locally using the Durable Task Scheduler emulator, try creating a scheduler and task hub resource and deploying to Azure Container Apps.
 
 > [!div class="nextstepaction"]
-> [Deploy Durable Task Scheduler hosted on Azure Container Apps to Azure](./quickstart-aca-azd-durable-task-sdk.md)
+> [Deploy Durable Task Scheduler hosted on Azure Container Apps to Azure](./quickstart-container-apps-durable-task-sdk.md)