From 6fbd0dbde10087adade7aef5219f4db1bc70d965 Mon Sep 17 00:00:00 2001
From: maurojasmsft <67924377+maurojasmsft@users.noreply.github.com>
Date: Fri, 19 Jul 2024 10:41:30 -0500
Subject: [PATCH] Chaged titles and removed back slash

---
 .../Network/expressRouteGateways/recommendations.yaml       | 2 +-
 azure-resources/Network/p2sVpnGateways/recommendations.yaml | 2 +-
 azure-resources/Network/virtualHubs/recommendations.yaml    | 6 +++---
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/azure-resources/Network/expressRouteGateways/recommendations.yaml b/azure-resources/Network/expressRouteGateways/recommendations.yaml
index 00a88e5de..0534663c4 100644
--- a/azure-resources/Network/expressRouteGateways/recommendations.yaml
+++ b/azure-resources/Network/expressRouteGateways/recommendations.yaml
@@ -3,7 +3,7 @@
   recommendationTypeId: null
   recommendationControl: High Availability
   recommendationImpact: High
-  recommendationResourceType: Microsoft.Network/expressRouteGateways/
+  recommendationResourceType: Microsoft.Network/expressRouteGateways
   recommendationMetadataState: Active
   longDescription: To increase reliability, it's advised that each v-Hub's ExpressRoute gateway connects to at least two circuits, with each circuit originating from a different peering location than the other, ensuring diverse connectivity paths for enhanced resilience.|
   potentialBenefits: Enhance resiliency for Azure Service
diff --git a/azure-resources/Network/p2sVpnGateways/recommendations.yaml b/azure-resources/Network/p2sVpnGateways/recommendations.yaml
index fa3cadfd8..4a06a9c24 100644
--- a/azure-resources/Network/p2sVpnGateways/recommendations.yaml
+++ b/azure-resources/Network/p2sVpnGateways/recommendations.yaml
@@ -3,7 +3,7 @@
   recommendationTypeId: null
   recommendationControl: Monitoring and Alerting
   recommendationImpact: High
-  recommendationResourceType: Microsoft.Network/p2sVpnGateways/
+  recommendationResourceType: Microsoft.Network/p2sVpnGateways
   recommendationMetadataState: Active
   longDescription: Set up monitoring and alerts for Point-to-Site VPN gateways. Create alert rule for ensuring promptly response to critical events such as Gateway overutilization, connection count limits and User VPN route limits.
   potentialBenefits: Detection and mitigation to avoid disruptions.
diff --git a/azure-resources/Network/virtualHubs/recommendations.yaml b/azure-resources/Network/virtualHubs/recommendations.yaml
index c39f71b20..dd7ba3ea9 100644
--- a/azure-resources/Network/virtualHubs/recommendations.yaml
+++ b/azure-resources/Network/virtualHubs/recommendations.yaml
@@ -3,7 +3,7 @@
   recommendationTypeId: null
   recommendationControl: High Availability
   recommendationImpact: High
-  recommendationResourceType: Microsoft.Network/virtualHubs/
+  recommendationResourceType: Microsoft.Network/virtualHubs
   recommendationMetadataState: Active
   longDescription: |
     Routing Intent will enable Inter Hub connectivity. This is recommended if you have Secured Hubs and no Custom Route Tables to establish Interconnectivity between the Vnets across v-Hubs.
@@ -17,12 +17,12 @@
     - name: How to configure v-Hub routing intent and routing policies
       url: "https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies"
 
-- description: Enable routing intent to send private and internet traffic via Azure Firewall or Security Solution deployed in the v-Hub.
+- description: Route private and internet traffic through v-Hub's Azure Firewall
   aprlGuid: 0390bf34-8be5-44ee-b454-d6b8d5dd3790
   recommendationTypeId: null
   recommendationControl: High Availability
   recommendationImpact: High
-  recommendationResourceType: Microsoft.Network/virtualHubs/
+  recommendationResourceType: Microsoft.Network/virtualHubs
   recommendationMetadataState: Active
   longDescription: Routing Intent will allow private and internet traffic inspection via Azure Firewall or Security Solution deployed on the v-Hub.
   potentialBenefits: Enhanced traffic inspection