update links

src/pages/docs/how-to/examples.mdx

@@ -100,7 +100,7 @@ One of the simplest ways of running NetBird client application is to use a pre-b
 * **NetBird account.**
    Register one at [app.netbird.io](https://app.netbird.io/).
 
-You would need to obtain a [setup key](/docs/how-to/setup-keys) to associate NetBird client with your account.
+You would need to obtain a [setup key](/docs/how-to/register-peers-using-setup-keys) to associate NetBird client with your account.
 
 The setup key could be found in the NetBird Management dashboard under the Setup Keys tab - [https://app.netbird.io/setup-keys](https://app.netbird.io/setup-keys).
 

src/pages/docs/how-to/getting-started.mdx

@@ -278,10 +278,10 @@ Check connection status:
 ```
 
 ### Running NetBird with a Setup Key
-In case you are activating a server peer, you can use a [setup key](/docs/how-to/setup-keys) as described in the steps below.
+In case you are activating a server peer, you can use a [setup key](/docs/how-to/register-peers-using-setup-keys) as described in the steps below.
 > This is especially helpful when you are running multiple server instances with infrastructure-as-code tools like ansible and terraform.
 
-1. Login to the Management Service. You need to have a `setup key` in hand (see [setup keys](/docs/how-to/setup-keys)).
+1. Login to the Management Service. You need to have a `setup key` in hand (see [setup keys](/docs/how-to/register-peers-using-setup-keys)).
 
 For all systems:
 ```bash

src/pages/docs/how-to/register-peers-using-setup-keys.mdx

@@ -40,7 +40,7 @@ Setup keys are set to expire after 30 days. When expired, the setup key can't be
     <img src="/img/architecture/peer-auto-tagging-setupkey.gif" alt="high-level-dia" width="800" style={{boxShadow: '0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19)'}} />
 </p>
 
-NetBird offers a powerful [Access Control feature](/docs/how-to/access-control) that allows easy access management of your resources.
+NetBird offers a powerful [Access Control feature](/docs/how-to/restrict-access-to-peers) that allows easy access management of your resources.
 In a basic scenario, you would create multiple groups of peers and create access rules to define what groups can access each other.
 Adding peers to groups might become time-consuming in large networks with dozens of machines.