validation

Author: cephalin

articles/app-service/containers/toc.yml

@@ -104,7 +104,7 @@
     - name: Deploy the app
       items:
       - name: Run from package
-        href: deploy-run-package.md
+        href: ../deploy-run-package.md?toc=%2fazure%2fapp-service%2fcontainers%2ftoc.json
       - name: Deploy via FTP
         href: ../deploy-ftp.md?toc=%2fazure%2fapp-service%2fcontainers%2ftoc.json
       - name: Deploy via cloud sync

articles/app-service/deploy-run-package.md

@@ -69,4 +69,4 @@ If you publish an updated package with the same name to Blob storage, you need t
 ## More resources
 
 - [Continuous deployment for Azure App Service](deploy-continuous-deployment.md)
-- [Deploy code with a ZIP or WAR file](deployment-zip-push.md)
+- [Deploy code with a ZIP or WAR file](deploy-zip.md)

includes/app-service-deploy-atomicity.md

@@ -14,6 +14,6 @@ ms.custom: "include file"
 
 All the officially supported deployment methods make changes to the files in the `/home/site/wwwroot` folder of your app. These files are used to run your app. Therefore, the deployment can fail because of locked files. The app may also behave unpredictably during deployment, because not all the files updated at the same time. This is undesirable for a customer-facing app. There are a few different ways to avoid these issues:
 
-- [Run your app from the ZIP package directly](../articles/app-service/deploy-run-zip-package.md), without unpacking it.
+- [Run your app from the ZIP package directly](../articles/app-service/deploy-run-package.md), without unpacking it.
 - Stop your app or enable offline mode for your app during deployment. For more information, see [Deal with locked files during deployment](https://github.com/projectkudu/kudu/wiki/Dealing-with-locked-files-during-deployment).
 - Deploy to a [staging slot](../articles/app-service/deploy-staging-slots.md) with [auto swap](../articles/app-service/deploy-staging-slots.md#configure-auto-swap) enabled.