cleaned up some grammar

Author: im-samz

articles/azure-functions/functions-networking-options.md

@@ -212,7 +212,7 @@ Currently, you can use non-HTTP trigger functions from within a virtual network
 
 ### Premium plan with virtual network triggers
 
-The Premium plan supports functions that are triggered by services inside a virtual network. These non-HTTP triggers are known as virtual network triggers. To enable dynamic scaling for function apps triggered by them, the **Runtime Sclae Monitoring** setting must be turned on. The setting can be found in the [Azure Portal](https://portal.azure.com) under **Configuration** > **Function runtime settings**.
+The Premium plan supports functions that are triggered by services inside a virtual network. These non-HTTP triggers are known as virtual network triggers. To enable dynamic scaling for function apps triggered by them, the **Runtime Scale Monitoring** setting must be turned on. The setting can be found in the [Azure Portal](https://portal.azure.com) under **Configuration** > **Function runtime settings**.
 
 :::image type="content" source="media/functions-networking-options/virtual-network-trigger-toggle.png" alt-text="VNETToggle":::
 
@@ -239,7 +239,7 @@ $Resource | Set-AzResource -Force
 > [!TIP]
 > Enabling virtual network triggers may have an impact on the performance of your application since your App Service plan instances monitor your triggers to determine when to scale. Though, this impact is likely to be very small.
 
-Virtual network triggers are supported in Functions runtime version 2.x and above. The table below contains the non-HTTP trigger types that are supported. We recommend upgrading to versions that also support [target-based scaling](functions-target-based-scaling.md#premium-plan-with-runtime-scale-monitoring-enabled) to get the best scaling performance.
+Virtual network triggers are supported in version 2.x and above of the Functions runtime. The table below contains the non-HTTP trigger types that are supported. We recommend upgrading to versions that also support [target-based scaling](functions-target-based-scaling.md#premium-plan-with-runtime-scale-monitoring-enabled) to get the best scaling performance.
 
 | Extension | Minimum version |
 |-----------|---------| 

articles/azure-functions/functions-target-based-scaling.md

@@ -1,7 +1,7 @@
 ---
 title: Target-based scaling in Azure Functions
 description: Explains target-based scaling behaviors of Consumption plan and Premium plan function apps.
-ms.date: 06/16/2023
+ms.date: 12/19/2023
 ms.topic: conceptual
 ms.service: azure-functions
 ---
@@ -72,7 +72,7 @@ To learn more, see the [example configurations for the supported extensions](#su
 
 ## Premium plan with runtime scale monitoring enabled
 
-When [runtime scale monitoring](functions-networking-options.md?tabs=azure-cli#premium-plan-with-virtual-network-triggers) is enabled, the extensions handle dyanmic scaling. This is because the scale controller does not have access to services secured by a virtual network. After you enable runtime scale monitoring, you'll need to upgrade your extension packages to the minimum versions below to unlock the additional target-based scaling logic. 
+When [runtime scale monitoring](functions-networking-options.md?tabs=azure-cli#premium-plan-with-virtual-network-triggers) is enabled, the extensions handle dynamic scaling. This is because the [scale controller](event-driven-scaling.md#runtime-scaling) does not have access to services secured by a virtual network. After you enable runtime scale monitoring, you'll need to upgrade your extension packages to the minimum versions below to unlock the additional target-based scaling functionality. 
 
 | Extension Name | Minimum Version Needed | 
 | -------------- | ---------------------- |