Merge pull request #292336 from ram-kakani/docs-editor/oracle-database-network-plan-1734975631

Update oracle-database-network-plan.md

Author: prmerger-automator[bot]

articles/oracle/oracle-db/oracle-database-network-plan.md

@@ -35,7 +35,7 @@ The following table describes the network topologies that are supported by each
 |Connectivity over active/active zone-redundant gateways| No |
 |Transit connectivity via a virtual WAN for an Oracle database cluster provisioned in a spoke virtual network| Yes |
 |On-premises connectivity to an Oracle database cluster via a virtual WAN and attached software-defined wide area network (SD-WAN)|No|
-|On-premises connectivity via a secured hub (a firewall network virtual appliance) | No|
+|On-premises connectivity via a secured hub (a firewall network virtual appliance) |Yes|
 |Connectivity from an Oracle database cluster on Oracle Database@Azure nodes to Azure resources|Yes|
 
 \* You can overcome this limitation by using a site-to-site VPN.
@@ -54,10 +54,10 @@ The following table describes required configurations of supported network featu
 |Load balancers for Oracle database cluster traffic|No|
 |Dual stack (IPv4 and IPv6) virtual network|Only IPv4 is supported|
 
->[!NOTE]
-> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective. 
->
-> For example, if your delegated subnet is `x.x.x.x/24`, you must configured your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
+> [!NOTE]
+> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't effective. 
+> 
+> For example, if your delegated subnet is `x.x.x.x/24`, you must configure your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
 
 ## Related content