```
-## Types of setup keys
+## Types of Setup Keys
-There are 2 types of setup keys:
-* **One-off key**. This type of key can be used only once to authenticate a machine.
-* **Reusable key**. This type of key can be used multiple times to authenticate machines.
+There are two types of setup keys:
+* **One-off key** — can be used only once to authenticate a single machine.
+* **Reusable key** — can be used multiple times to authenticate a configurable number of machines.
-## Ephemeral peers
+## Ephemeral Peers
You can create a setup key with the ephemeral peers option enabled.
-Peers added with this key that later become offline for over 10 minutes will be removed automatically from the NetBird system.
+Peers registered with this key are automatically removed from NetBird after staying offline for more than 10 minutes.
-This is useful when you want to add containers or auto scaling instances to your network.
+This is useful for short-lived workloads such as containers or autoscaling instances.
-## Using setup keys
+## Managing Setup Keys
-Setup keys are available in the NetBird Management Dashboard under `Peers` → `Setup Keys` [https://app.netbird.io/setup-keys](https://app.netbird.io/setup-keys).
- You can easily add new or revoke keys.
+Setup keys are available in the NetBird Management Dashboard under `Settings` → `Setup Keys`.
+Use [this page](https://app.netbird.io/settings?tab=setup-keys) to view and manage your setup keys.
+From there, you can add new keys or revoke existing ones.
- When revoking a key, all machines authenticated with this key will remain connected to the network. The same logic applies when the key expires.
+ When you revoke a key, all machines already authenticated with it remain connected to the network. The same applies when the key expires.
## Expiration
-You can set expiration when creating a key. When expired, the setup key can't be used anymore.
+You can set an expiration date when creating a key. Once expired, the key can no longer be used.
-## Usage limit
+## Usage Limit
By default, every reusable key has unlimited usage.
-We recommend limiting the number of times the key can be used, e.g., set it to 30 if you need to enroll only 30 machines.
+We recommend limiting the number of times a key can be used — for example, set it to 30 if you only need to enroll 30 machines.
## Allow Extra DNS Labels
You can create a setup key with the **Allow Extra DNS Labels** option enabled.
-When enabled, peers registered with this key can set additional DNS names using the `--extra-dns-labels` flag. Other peers in the network can then reach them by these names.
+When enabled, peers registered with this key can set additional DNS names using the `--extra-dns-labels` flag, so other peers in the network can reach them by those names.
-If multiple peers share the same label, they form a DNS round-robin group for that label, distributing queries across all of them.
+If multiple peers share the same label, they form a DNS round-robin group for that label, with queries distributed across all of them.
See [Extra DNS Labels](/manage/dns/extra-dns-labels) for full details, including wildcard labels and usage examples.
-## Peer Auto-grouping
+## Peer Auto-Grouping
-NetBird offers a powerful [access control feature](/manage/access-control/manage-network-access) 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.
+NetBird offers a powerful [access control feature](/manage/access-control/manage-network-access) for managing access to your resources.
+In a typical setup, you create multiple groups of peers and define access rules that determine which groups can reach each other.
+Adding peers to groups manually can become time-consuming in large networks with dozens of machines.
-Starting NetBird [v0.9.2](https://github.com/netbirdio/netbird/releases), when creating or updating a setup key,
-it is possible to specify a list of auto-assign groups. Every peer registered with this key will be automatically added
-to these groups. All the access control rules enabled for these groups will apply automatically.
+Starting with NetBird [v0.9.2](https://github.com/netbirdio/netbird/releases), you can specify a list of auto-assign groups when creating or updating a setup key.
+Every peer registered with this key is automatically added to those groups, and all access control rules for those groups apply automatically.
-To add `Auto-assign groups`, open `Peers` → `Setup Keys` and create or update any existing setup key.
-Then use this key to enroll new machine.
+To configure `Auto-assign groups`, open `Settings` → `Setup Keys` and create or update a setup key.
+Then use this key to enroll new machines.
@@ -81,17 +78,17 @@ Then use this key to enroll new machine.
Auto-assign groups will apply only to newly registered machines.
-## Create setup key
+## Create Setup Key
-Go to `Peers` → `Setup Keys` and click the `Create Setup Key` button
-In the opened popup, give your new key an easily identifiable name, choose type, set usage limit, and assign auto groups.
-The defaults should be suitable for most of the cases. We recommend using one-off keys for security reasons.
+Go to `Settings` → `Setup Keys` and click the `Create Setup Key` button.
+In the dialog that opens, give your new key a recognizable name, choose its type, set a usage limit, and assign auto-groups.
+The defaults are suitable for most cases. For security reasons, we recommend using one-off keys.
-After your key has been successfully created, copy and store it in a secure location.
+Once the key has been created, copy it and store it in a secure location.
diff --git a/src/pages/use-cases/cloud/aws-ecs-terraform.mdx b/src/pages/use-cases/cloud/aws-ecs-terraform.mdx
index 793665fb..828a0246 100644
--- a/src/pages/use-cases/cloud/aws-ecs-terraform.mdx
+++ b/src/pages/use-cases/cloud/aws-ecs-terraform.mdx
@@ -102,7 +102,7 @@ One of the simplest ways of running NetBird client application is to use a pre-b
You would need to obtain a [setup key](/manage/peers/register-machines-using-setup-keys) to associate NetBird client with your account.
-The setup key could be found in the NetBird Management dashboard under `Peers` → `Setup Keys` - [https://app.netbird.io/setup-keys](https://app.netbird.io/setup-keys).
+The setup key could be found in the NetBird Management dashboard under `Settings` → `Setup Keys` - [https://app.netbird.io/setup-keys](https://app.netbird.io/setup-keys).
Set the ```NB_SETUP_KEY``` environment variable and run the command.
diff --git a/src/pages/use-cases/cloud/routing-peers-and-kubernetes.mdx b/src/pages/use-cases/cloud/routing-peers-and-kubernetes.mdx
index e5342e07..c68a378f 100644
--- a/src/pages/use-cases/cloud/routing-peers-and-kubernetes.mdx
+++ b/src/pages/use-cases/cloud/routing-peers-and-kubernetes.mdx
@@ -20,7 +20,7 @@ from hosts running on a Hetzner without exposing them to the public internet.
## Step-by-Step guide
### Step 1: Create a setup key
-Navigate to `Peers` → `Setup Keys` in the NetBird management dashboard and click on "Create setup key".
+Navigate to `Settings` → `Setup Keys` in the NetBird management dashboard and click on "Create setup key".
Choose a name, e.g. `Kubernetes routing peers`, mark the key as `reusable` and enable `Ephemeral peers`. This option is
ideal for stateless workloads like containers, where peers that are offline for over 10 minutes are automatically removed.