minor edits and updates

Author: reyjordi

articles/application-gateway/application-gateway-create-probe-portal.md

@@ -18,7 +18,10 @@ ms.author: mbender
 > * [Azure Resource Manager PowerShell](application-gateway-create-probe-ps.md)
 > * [Azure Classic PowerShell](application-gateway-create-probe-classic-ps.md)
 
-In this article, you add a custom health probe to an existing application gateway through the Azure portal. Azure Application Gateway uses these health probes to monitor the health of the resources in the backend pool.
+> [!IMPORTANT]
+> Application Gateway v2 SKU is the current and recommended version. Application Gateway v1 SKU was deprecated on April 28, 2023, and will be retired on April 28, 2026. If you're using Application Gateway v1, plan your migration to v2 now. For more information, see [Migrate your Application Gateways from V1 SKU to V2 SKU](v1-retirement.md).
+
+In this article, you add a custom health probe to an existing application gateway through the Azure portal. Azure Application Gateway uses health probes to monitor the health of the resources in the backend pool.
 
 ## Before you begin
 
@@ -45,24 +48,24 @@ Probes are configured in a two-step process through the portal. The first step i
    |**Name**|customProbe|This value is a friendly name given to the probe that is accessible in the portal.|
    |**Protocol**|HTTP or HTTPS | The protocol that the health probe uses. |
    |**Host**|i.e contoso.com|This value is the name of the virtual host (different from the VM host name) running on the application server. The probe is sent to \<protocol\>://\<host name\>:\<port\>/\<urlPath\>  This can also be the private IP address of the server, or the public IP address, or the DNS entry of the public IP address.  The probe will attempt to access the server when used with a file based path entry, and validate a specific file exists on the server as a health check.|
-   |**Pick host name from backend HTTP settings**|Yes or No|Sets the *host* header in the probe to the host name from the HTTP settings to which this probe is associated. Specially required for multi-tenant backends such as Azure app service. [Learn more](./configuration-http-settings.md#pick-host-name-from-backend-address)|
-   |**Pick port from backend HTTP settings**| Yes or No|Sets the *port* of the health probe to the port from HTTP settings to which this probe is associated. If you choose no, you can enter a custom destination port to use |
+   |**Pick host name from backend settings**|Yes or No|Sets the *host* header in the probe to the host name from the backend settings to which this probe is associated. Specially required for multi-tenant backends such as Azure app service. [Learn more](./configuration-http-settings.md#pick-host-name-from-backend-address)|
+   |**Pick port from backend settings**| Yes or No|Sets the *port* of the health probe to the port from backend settings to which this probe is associated. If you choose no, you can enter a custom destination port to use |
    |**Port**| 1-65535 | Custom port to be used for the health probes | 
    |**Path**|/ or any valid path|The remainder of the full url for the custom probe. A valid path starts with '/'. For the default path of http:\//contoso.com, just use '/'.  You can also input a server path to a file for a static health check instead of web based.  File paths should be used while using public / private ip, or public ip dns entry as the hostname entry.|
    |**Interval (secs)**|30|How often the probe is run to check for health. It isn't recommended to set the lower than 30 seconds.|
-   |**Timeout (secs)**|30|The amount of time the probe waits before timing out. If a valid response isn't received within this time-out period, the probe is marked as failed. The timeout interval needs to be high enough that an http call can be made to ensure the backend health page is available. The time-out value shouldn't be more than the ‘Interval’ value used in this probe setting or the ‘Request timeout’ value in the HTTP setting, which will be associated with this probe.|
+   |**Timeout (secs)**|30|The amount of time the probe waits before timing out. If a valid response isn't received within this time-out period, the probe is marked as failed. The timeout interval needs to be high enough that an http call can be made to ensure the backend health page is available. The time-out value shouldn't be more than the ‘Interval’ value used in this probe setting or the ‘Request timeout’ value in the backend setting, which will be associated with this probe.|
    |**Unhealthy threshold**|3|Number of consecutive failed attempts to be considered unhealthy. The threshold can be set to 0 or more.|
    |**Use probe matching conditions**|Yes or No|By default, an HTTP(S) response with status code between 200 and 399 is considered healthy. You can change the acceptable range of backend response code or backend response body. [Learn more](./application-gateway-probe-overview.md#probe-matching)|
-   |**HTTP Settings**|selection from dropdown|Probe will get associated with the HTTP settings selected here and therefore, will monitor the health of that backend pool, which is associated with the selected HTTP setting. It will use the same port for the probe request as the one being used in the selected HTTP setting. You can only choose those HTTP settings, which aren't associated with any other custom probe. <br>The only HTTP settings that are available for association are those that have the same protocol as the protocol chosen in this probe configuration, and have the same state for the *Pick Host Name From Backend HTTP setting* switch.|
+   |**Backend Settings**|selection from dropdown|Probe will get associated with the backend settings selected here and therefore, will monitor the health of that backend pool, which is associated with the selected backend setting. It will use the same port for the probe request as the one being used in the selected backend setting. You can only choose those backend settings, which aren't associated with any other custom probe. <br>The only backend settings that are available for association are those that have the same protocol as the protocol chosen in this probe configuration, and have the same state for the *Pick Host Name From Backend setting* switch.|
 
    > [!IMPORTANT]
-   > The probe will monitor health of the backend only when it's associated with one or more HTTP settings. It will monitor backend resources of those backend pools which are associated to the HTTP settings to which this probe is associated with. The probe request will be sent as \<protocol\>://\<hostName\>:\<port\>/\<urlPath\>.
+   > The probe will monitor health of the backend only when it's associated with one or more backend settings. It will monitor backend resources of those backend pools which are associated to the backend settings to which this probe is associated with. The probe request will be sent as \<protocol\>://\<hostName\>:\<port\>/\<urlPath\>.
 
 ### Test backend health with the probe
 
 After entering the probe properties, you can test the health of the backend resources to verify that the probe configuration is correct and that the backend resources are working as expected.
 
-1. Select **Test** and note the result of the probe. The Application gateway tests the health of all the backend resources in the backend pools associated with the HTTP settings used for this probe. 
+1. Select **Test** and note the result of the probe. The Application gateway tests the health of all the backend resources in the backend pools associated with the backend settings used for this probe. 
 
    ![Test backend health][5]