clarifications

Author: robswain

articles/private-5g-core/azure-stack-edge-virtual-machine-sizing.md

@@ -23,7 +23,7 @@ The following table lists the maximum supported limits for a range of parameters
 | RAN nodes (eNB/gNB)    | 200 per packet core |
 | Active UEs             | 10,000 per deployment (all sites) |
 | SIMs                   | 20,000 per ASE |
-| SIM provisioning       | 10,000 via Azure portal, 4MB via REST API |
+| SIM provisioning       | 10,000 per JSON file via Azure portal, 4MB per REST API call |
 
 Your chosen service package may define lower limits, with overage charges for exceeding them - see [Azure Private 5G Core pricing](https://azure.microsoft.com/pricing/details/private-5g-core/) for details. If you require higher throughput for your use case, please contact us to discuss your needs.
 

articles/private-5g-core/provision-sims-arm-template.md

@@ -67,7 +67,7 @@ Use the information you collected in [Collect the required information for your
 If you don't want to assign a SIM policy or static IP address now, you can delete the `simPolicy` and/or `staticIpConfiguration` parameters.
 
 > [!NOTE]
-> The maximum size of the API request body is 4MB. We recommend entering a maximum of 1000 SIMs per JSON array to remain below this limit. If you want to provision more than 1000 SIMs, create multiple arrays and repeat the provisioning process for each. Alternatively, you can use the [Azure portal](provision-sims-azure-portal.md) to provision up to 10,000 SIMs.
+> The maximum size of the API request body is 4MB. We recommend entering a maximum of 1000 SIMs per JSON array to remain below this limit. If you want to provision more than 1000 SIMs, create multiple arrays and repeat the provisioning process for each. Alternatively, you can use the [Azure portal](provision-sims-azure-portal.md) to provision up to 10,000 SIMs per JSON file.
 
 ```json
 [