Update access-on-premises-resources.md

'Dyname' looks like a typo and should be 'Dynamic'. I could not find any references to 'Dyname' elsewhere.

Author: QueryCoordinator

articles/ai-studio/how-to/access-on-premises-resources.md

@@ -83,7 +83,7 @@ Follow the [Quickstart: Direct web traffic using the portal](/azure/application-
     > - If you are using HTTPS listener with certificate uploaded, make sure the FQDN alias matches with the certificate's CN (Common Name) or SAN (Subject Alternative Name) otherwise HTTPS call will fail with SNI (Server Name Indication).
     > - The provided FQDNs must have at least three labels in the name to properly create the private DNS zone of thee private endpoint for Application Gateway.
     > - The FQDNs field is editable after the private endpoint creation through SDK or CLI. The field is not editable in the Azure portal.
-    > - Dyname sub-resource naming is not supported for the private Frontend IP configuration. The Frontend IP name must be `appGwPrivateFrontendIpIPv4`.
+    > - Dynamic sub-resource naming is not supported for the private Frontend IP configuration. The Frontend IP name must be `appGwPrivateFrontendIpIPv4`.
 
 ### Configure using Python SDK and Azure CLI
 
@@ -109,4 +109,4 @@ For errors related to the Application Gateway connection to your backend resourc
 
 ## Related content
 
-- [Managed virtual network isolation](configure-managed-network.md)
+- [Managed virtual network isolation](configure-managed-network.md)