Merge pull request #111385 from NathanDunning/patch-2

Update container-instances-virtual-network-concepts.md

Author: Court72

articles/container-instances/container-instances-virtual-network-concepts.md

@@ -43,7 +43,7 @@ Container groups deployed into an Azure virtual network enable scenarios like:
 * To deploy container groups to a subnet, the subnet and the container group must be on the same Azure subscription.
 * You can't enable a [liveness probe](container-instances-liveness-probe.md) or [readiness probe](container-instances-readiness-probe.md) in a container group deployed to a virtual network.
 * Due to the additional networking resources involved, deployments to a virtual network are typically slower than deploying a standard container instance.
-* Outbound connections to port 25 and 19390 are not supported at this time. Port 19390 needs to be opened in your Firewall for connecting to ACI from Azure ortal when container groups are deployed in virtual networks.
+* Outbound connections to port 25 and 19390 are not supported at this time. Port 19390 needs to be opened in your Firewall for connecting to ACI from Azure portal when container groups are deployed in virtual networks.
 * For inbound connections, the firewall should also allow all ip addresses within the virtual network.
 * If you are connecting your container group to an Azure Storage Account, you must add a [service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) to that resource.
 * [IPv6 addresses](../virtual-network/ip-services/ipv6-overview.md) are not supported at this time.