Enhance formatting and clarity in routing traffic documentation

- Updated section headers to bold for improved visibility and consistency.
- Reformatted descriptions for "Network identifiers and ranges," "Routing peer," "Routing group," "High availability routes," "Masquerade," and "DNS Routes" for better readability.
- Added emphasis to the note regarding route configuration when masquerade is not enabled.

Author: TechHutTV

src/pages/how-to/routing-traffic-to-private-networks.mdx

@@ -39,26 +39,20 @@ A network route describes the network you want to connect with your NetBird peer
     Network routes are available in NetBird [v0.9.0](https://github.com/netbirdio/netbird/releases) or later.
 </Note>
 
-#### Network identifiers and ranges
-Network identifiers are names for each network you want to route traffic from your peers, and ranges are IP ranges declared in CIDR notation which refers to an external network. The combination of identifiers and these ranges makes a single network.
+**Network identifiers and ranges** Network identifiers are names for each network you want to route traffic from your peers, and ranges are IP ranges declared in CIDR notation which refers to an external network. The combination of identifiers and these ranges makes a single network.
 
-#### Routing peer
-A routing peer is a peer that routes packets between your routed network and the other NetBird peers.
+**Routing peer**: A routing peer is a peer that routes packets between your routed network and the other NetBird peers.
 
-#### Routing group
-A routing group is a set of routing peers. Each will route packets between your routed network and the other NetBird peers.
+**Routing group**: A routing group is a set of routing peers. Each will route packets between your routed network and the other NetBird peers.
 
-#### High availability routes
-A highly available route is a combination of multiple routes with the same network identifier and ranges. They have different routing peers or routing peer groups offering highly available paths for communication between your peers and external networks. 
+**High availability routes**: A highly available route is a combination of multiple routes with the same network identifier and ranges. They have different routing peers or routing peer groups offering highly available paths for communication between your peers and external networks. 
 Nodes connected to routing peers will choose one of them to route packets to external networks based on connection type and defined metrics.
 
-#### Masquerade
-Masquerade hides other NetBird network IPs behind the routing peer local address when accessing the target network range. This option allows access to your private networks without configuring routes on your local routers or other devices.
+**Masquerade**: Masquerade hides other NetBird network IPs behind the routing peer local address when accessing the target network range. This option allows access to your private networks without configuring routes on your local routers or other devices.
 
-If you do not enable this option, you must configure a route to your NetBird network in your external network infrastructure.
+_If you do not enable this option, you must configure a route to your NetBird network in your external network infrastructure._
 
-### DNS Routes
-An alternative to specifying a network range directly is to use DNS routes. Instead of adding the network directly, you can add multiple domains in a route that will be dynamically resolved on the client. The resolved IP addresses for these domains will be added as routes. For example, a network administrator can ensure that traffic to `website.com` or `api.website.com` is routed through a specific machine. So they configure DNS routes for these domains instead of specifying the IP ranges.
+**DNS Routes**: An alternative to specifying a network range directly is to use DNS routes. Instead of adding the network directly, you can add multiple domains in a route that will be dynamically resolved on the client. The resolved IP addresses for these domains will be added as routes. For example, a network administrator can ensure that traffic to `website.com` or `api.website.com` is routed through a specific machine. So they configure DNS routes for these domains instead of specifying the IP ranges.
 
 By default, DNS routes are resolved every 60 seconds. You can adjust this interval using the `--dns-router-interval` flag: