Skip to content

Commit be0f724

Browse files
authored
add missing word to routing-traffic-to-multiple-resources.mdx (#312)
1 parent eb6589c commit be0f724

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/pages/how-to/routing-traffic-to-multiple-resources.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Adding routes to resources within on-premises or cloud is a common scenario for
44
## Example
55
In the following scenario, we will cover the case where all users have restricted access to internal DNS servers in the internal network, and the DevOps team has full access to the entire network.
66
The network address is `172.16.0.0/15` and DNS servers has the IPs `172.16.30.2` and `172.17.100.2`.
7-
These IP ranges will routed using [Routing peers](/how-to/networks-concept#routing-peers) running in the network.
7+
These IP ranges will be routed using [Routing peers](/how-to/networks-concept#routing-peers) running in the network.
88

99
### Create a Network
1010
To create a Network, navigate to the `Networks` > `Networks` section in the NetBird dashboard:
@@ -108,4 +108,4 @@ With the steps above, we created resources that allow different levels of access
108108
- Make sure to [star us on GitHub](https://github.com/netbirdio/netbird)
109109
- Follow us [on Twitter](https://twitter.com/netbird)
110110
- Join our [Slack Channel](https://join.slack.com/t/netbirdio/shared_invite/zt-31rofwmxc-27akKd0Le0vyRpBcwXkP0g)
111-
- NetBird [latest release](https://github.com/netbirdio/netbird/releases) on GitHub
111+
- NetBird [latest release](https://github.com/netbirdio/netbird/releases) on GitHub

0 commit comments

Comments
 (0)