Minor edits

Author: dksimpson

articles/azure-functions/run-functions-from-deployment-package.md

@@ -1,7 +1,7 @@
 ---
 title: Run your functions from a package file in Azure 
 description: Learn how to configure Azure Functions to run your function app from a deployment package file that contains your function app project.
-mw-service: azure-functions
+ms-service: azure-functions
 ms.topic: conceptual
 ms.date: 06/28/2024
 
@@ -96,7 +96,7 @@ This section provides information about how to run your function app from a pack
 + When you're running on a Dedicated plan, ensure you enable [Always On](dedicated-plan.md#always-on).
 + You can use [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) to upload package files to blob containers in your storage account.
 
-### Manually upload a package to Blob Storage
+### Manually uploading a package to Blob Storage
 
 To deploy a zipped package when using the URL option, you must create a .zip compressed deployment package and upload it to the destination. The following procedure deploys to a container in Blob Storage:
 

includes/app-service-run-from-package-via-identity.md

@@ -1,18 +1,18 @@
 ---
 author: mattchenderson
-ms.service: app-service
-ms.topic: include
-ms.date: 06/11/2021
 ms.author: mahender
+ms.service: app-service
 ms.subservice: web-apps
+ms.topic: include
+ms.date: 06/28/2024
 ---
 
-Azure Blob Storage can be configured to [authorize requests with Microsoft Entra ID](/azure/storage/blobs/authorize-access-azure-active-directory?toc=%2fazure%2fstorage%2fblobs%2ftoc.json). This means that instead of generating a SAS key with an expiration, you can instead rely on the application's [managed identity](/azure/app-service/overview-managed-identity). By default, the app's system-assigned identity will be used. If you wish to specify a user-assigned identity, you can set the `WEBSITE_RUN_FROM_PACKAGE_BLOB_MI_RESOURCE_ID` app setting to the resource ID of that identity. The setting can also accept "SystemAssigned" as a value, although this is the same as omitting the setting altogether.
+You can configure Azure Blob Storage to [authorize requests with Microsoft Entra ID](/azure/storage/blobs/authorize-access-azure-active-directory?toc=%2fazure%2fstorage%2fblobs%2ftoc.json). This configuration means that instead of generating a SAS key with an expiration, you can instead rely on the application's [managed identity](/azure/app-service/overview-managed-identity). By default, the app's system-assigned identity is used. If you wish to specify a user-assigned identity, you can set the `WEBSITE_RUN_FROM_PACKAGE_BLOB_MI_RESOURCE_ID` app setting to the resource ID of that identity. The setting can also accept `SystemAssigned` as a value, which is equivalent to omitting the setting.
 
 To enable the package to be fetched using the identity:
 
 1. Ensure that the blob is [configured for private access](/azure/storage/blobs/anonymous-read-access-configure#set-the-anonymous-access-level-for-a-container).
 
 1. Grant the identity the [Storage Blob Data Reader](/azure/role-based-access-control/built-in-roles#storage-blob-data-reader) role with scope over the package blob. See [Assign an Azure role for access to blob data](/azure/storage/blobs/assign-azure-role-data-access) for details on creating the role assignment.
 
-1. Set the `WEBSITE_RUN_FROM_PACKAGE` application setting to the blob URL of the package. This will likely be of the form "https://{storage-account-name}.blob.core.windows.net/{container-name}/{path-to-package}" or similar.
+1. Set the `WEBSITE_RUN_FROM_PACKAGE` application setting to the blob URL of the package. This URL is usually of the form `https://{storage-account-name}.blob.core.windows.net/{container-name}/{path-to-package}` or similar.