acrolinx

Author: cephalin

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

@@ -10,7 +10,7 @@ ms.date: 01/14/2020
 
 In [Azure App Service](overview.md), you can run your apps directly from a deployment ZIP package file. This article shows how to enable this functionality in your app.
 
-All other deployment methods in App Service have something in common: your files are deployed to *D:\home\site\wwwroot* in your app (or */home/site/wwwroot* for Linux apps). Since the same directory is used by your app at runtime, it's possible for deployment to fail due to file lock conflicts, and for the app to behave unpredictably because some of the files are not yet updated.
+All other deployment methods in App Service have something in common: your files are deployed to *D:\home\site\wwwroot* in your app (or */home/site/wwwroot* for Linux apps). Since the same directory is used by your app at runtime, it's possible for deployment to fail because of file lock conflicts, and for the app to behave unpredictably because some of the files are not yet updated.
 
 In contrast, when you run directly from a package, the files in the package are not copied to the *wwwroot* directory. Instead, the ZIP package itself gets mounted directly as the read-only *wwwroot* directory. There are several benefits to running directly from a package:
 

articles/app-service/deploy-zip.md

@@ -26,7 +26,7 @@ The WAR file deployment deploys your [WAR](https://wikipedia.org/wiki/WAR_(file_
 
 ## Prerequisites
 
-To complete the steps in this article,[create an App Service app](/azure/app-service/), or use an app that you created for another tutorial.
+To complete the steps in this article, [create an App Service app](/azure/app-service/), or use an app that you created for another tutorial.
 
 [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.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-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. 

includes/app-service-web-deploy-zip-prepare.md

@@ -20,7 +20,7 @@ In a local terminal window, navigate to the root directory of your app project.
 
 This directory should contain the entry file to your web app, such as _index.html_, _index.php_, and _app.js_. It can also contain package management files like _project.json_, _composer.json_, _package.json_, _bower.json_, and _requirements.txt_.
 
-Unless you want App Service to run deployment automation for you, run all the build tasks (e.g. `npm`, `bower`, `gulp`, `composer`, `pip`, etc.) and make sure that you have all the files you need to run the app. This step is required if you want to [run your package directly](../articles/app-service/deploy-run-package.md).
+Unless you want App Service to run deployment automation for you, run all the build tasks (for example, `npm`, `bower`, `gulp`, `composer`, and `pip`) and make sure that you have all the files you need to run the app. This step is required if you want to [run your package directly](../articles/app-service/deploy-run-package.md).
 
 Create a ZIP archive of everything in your project. The following command uses the default tool in your terminal: