Skip to content

Commit 36d81c5

Browse files
authored
Incorporated review pass comments
1 parent 2da8b93 commit 36d81c5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/batch/accounts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Batch accounts and Azure Storage accounts
33
description: Learn about Azure Batch accounts and how they're used from a development standpoint.
44
ms.topic: conceptual
5-
ms.date: 04/03/2024
5+
ms.date: 04/04/2024
66

77
---
88
# Batch accounts and Azure Storage accounts
@@ -40,7 +40,7 @@ You can associate a storage account with your Batch account when you create the
4040
When a storage account is linked to a Batch account, it's considered to be the *autostorage account*. An autostorage account is required if you plan to use the [application packages](batch-application-packages.md) capability, as it's used to store the application package .zip files. It can also be used for [task resource files](resource-files.md#storage-container-name-autostorage). Linking Batch accounts to autostorage can avoid the need for shared access signature (SAS) URLs to access the resource files.
4141

4242
> [!NOTE]
43-
> Batch nodes automatically unzip application package .zip files when they are pulled down from a linked storage account. This can cause the node autostorage to fill up prematurely. For more information, see [Manage Batch application package](/cli/azure/batch/application/package).
43+
> Batch nodes automatically unzip application package .zip files when they are pulled down from a linked storage account. This can cause the compute node local storage to fill up. For more information, see [Manage Batch application package](/cli/azure/batch/application/package).
4444
4545
## Next steps
4646

0 commit comments

Comments
 (0)