first draft

Author: siddomala

articles/firewall-manager/check-point-overview.md

@@ -1,6 +1,6 @@
 ---
-title: Secure Azure virtual hubs using Check Point Cloudguard Connect
-description: Learn about Check Point CloudGuard Connect to secure Azure virtual hubs
+title: Secure Azure virtual hubs using Check Point Harmony Connect
+description: Learn about Check Point Harmony Connect to secure Azure virtual hubs
 author: vhorne
 ms.service: firewall-manager
 services: firewall-manager
@@ -9,23 +9,24 @@ ms.date: 10/30/2020
 ms.author: victorh
 ---
 
-# Secure virtual hubs using Check Point Cloudguard Connect
+# Secure virtual hubs using Check Point Harmony Connect
 
-Check Point CloudGuard Connect is a Trusted Security Partner in Azure Firewall Manager. It protects globally distributed branch office to Internet (B2I) or virtual network to Internet (V2I) connections with advanced threat prevention. 
+>[!NOTE]
+> This offering provides limited features compared to the [Check Point NVA integration with Virtual WAN](../virtual-wan/about-nva-hub.md#partners). We strongly recommend using this NVA integration to secure your network traffic.
+
+Check Point Harmony Connect is a Trusted Security Partner in Azure Firewall Manager. It protects globally distributed branch office to Internet (B2I) or virtual network to Internet (V2I) connections with advanced threat prevention. 
 
-With a simple configuration in Azure Firewall Manager, you can route branch hub and virtual network connections to the Internet through the CloudGuard Connect security as a service (SECaaS). Traffic is protected in transit from your hub to the Check Point cloud service in IPsec VPN tunnels.
+With a simple configuration in Azure Firewall Manager, you can route branch hub and virtual network connections to the Internet through the Harmony Connect security as a service (SECaaS). Traffic is protected in transit from your hub to the Check Point cloud service in IPsec VPN tunnels.
 
 When you enable auto-sync in the Check Point portal, any resource marked as *secured* in the Azure portal is automatically secured. You don't have to manage your assets twice. You simply choose to secure them once in the Azure portal.
 
 Check Point unifies multiple security services under one umbrella. Integrated security traffic is decrypted once and inspected in a single pass. Application Control, URL Filtering, and Content Awareness (DLP) enforce safe web use and protect your data. IPS and Antivirus protect users from known network exploits. Anti-Bot blocks connections to Command and Control servers and alerts you if a host is infected.
 
 Threat Emulation (sandboxing) protects users from unknown and zero-day threats. Check Point SandBlast Zero-Day Protection is a cloud-hosted sand-boxing technology where files are quickly quarantined and inspected. It runs in a virtual sandbox to discover malicious behavior before it enters your network. It prevents threats before the damage is done to save staff valuable time responding to threats. 
 
->[!NOTE]
-> This offering provides limited features compared to the [Check Point NVA integration with Virtual WAN](../virtual-wan/about-nva-hub.md#partners). We strongly recommend using this NVA integration to secure your network traffic.
 ## Deployment example
 
-Watch the following video to see how to deploy Check Point CloudGuard Connect as a trusted Azure security partner.
+Watch the following video to see how to deploy Check Point Harmony Connect as a trusted Azure security partner.
 
 > [!VIDEO https://www.youtube.com/embed/C8AuN76DEmU]
 

articles/virtual-wan/virtual-wan-faq.md

@@ -332,9 +332,9 @@ The current behavior is to prefer the ExpressRoute circuit path over hub-to-hub
 
 * Contact the product team to take part in the gated public preview. In this preview, traffic between the 2 hubs traverses through the Azure Virtual WAN router in each hub and uses a hub-to-hub path instead of the ExpressRoute path (which traverses through the Microsoft Edge routers/MSEE). To use this feature during preview, email **[email protected]** with the Virtual WAN IDs, Subscription ID, and the Azure region. Expect a response within 48 business hours (Monday-Friday) with confirmation that the feature is enabled.
 
-### When there's an ExpressRoute circuit connected as a bow-tie to a vWAN hub and a non-vWAN (customer-managed) VNet, what is the path for the non-vWAN VNET to reach a VNet directly connected to the vWAN hub? 
+### When there's an ExpressRoute circuit connected as a bow-tie to a Virtual WAN hub and a non Virtual WAN (customer-managed) VNet, what is the path for the non Virtual WAN VNet to reach the Virtual WAN hub? 
 
-The current behavior is to prefer the ExpressRoute circuit path for non-vWAN VNet to vWAN VNet connectivity. However, this isn't encouraged in a Virtual WAN setup. To resolve this, you can [create a Virtual Network connection](howto-connect-vnet-hub.md) to directly connect the non-vWAN VNet to the vWAN hub. Afterwards, VNet to VNet traffic will traverse through the Virtual WAN router instead of the ExpressRoute path (which traverses through the Microsoft Enterprise Edge routers/MSEE).
+The current behavior is to prefer the ExpressRoute circuit path for non Virtual WAN VNet to Virtual WAN connectivity. It is recommended that the customer [create a Virtual Network connection](howto-connect-vnet-hub.md) to directly connect the non Virtual WAN VNet to the Virtual WAN hub. Afterwards, VNet to VNet traffic will traverse through the Virtual WAN router instead of the ExpressRoute path (which traverses through the Microsoft Enterprise Edge routers/MSEE).
 
 ### Can hubs be created in different resource group in Virtual WAN?