diff --git a/public/docs-static/img/architecture/netbird-peer-auto-tagging-newkey.png b/public/docs-static/img/architecture/netbird-peer-auto-tagging-newkey.png
index 52ac13b0..8ea33b88 100644
Binary files a/public/docs-static/img/architecture/netbird-peer-auto-tagging-newkey.png and b/public/docs-static/img/architecture/netbird-peer-auto-tagging-newkey.png differ
diff --git a/public/docs-static/img/how-to-guides/add-setup-key.png b/public/docs-static/img/how-to-guides/add-setup-key.png
index 8f70a6ab..2e35be03 100644
Binary files a/public/docs-static/img/how-to-guides/add-setup-key.png and b/public/docs-static/img/how-to-guides/add-setup-key.png differ
diff --git a/public/docs-static/img/how-to-guides/setup-key-create2d.png b/public/docs-static/img/how-to-guides/setup-key-create2d.png
new file mode 100644
index 00000000..2fb16665
Binary files /dev/null and b/public/docs-static/img/how-to-guides/setup-key-create2d.png differ
diff --git a/public/docs-static/img/how-to-guides/setup-key-created.png b/public/docs-static/img/how-to-guides/setup-key-created.png
index 2fb16665..1eaf9820 100644
Binary files a/public/docs-static/img/how-to-guides/setup-key-created.png and b/public/docs-static/img/how-to-guides/setup-key-created.png differ
diff --git a/public/docs-static/img/how-to-guides/setup-keys.png b/public/docs-static/img/how-to-guides/setup-keys.png
index 5fc4eebf..39475b4b 100644
Binary files a/public/docs-static/img/how-to-guides/setup-keys.png and b/public/docs-static/img/how-to-guides/setup-keys.png differ
diff --git a/src/pages/how-to/manage-network-access.mdx b/src/pages/how-to/manage-network-access.mdx
index a6151940..c5d04f3f 100644
--- a/src/pages/how-to/manage-network-access.mdx
+++ b/src/pages/how-to/manage-network-access.mdx
@@ -34,7 +34,7 @@ Policies act as rules governing how different resources (peers) can communicate
 
 Policies are processed when the Management service shares a network map with all peers of your account. Because you can only create ALLOW policies, there is no processing order or priority. So, the decision to distribute peer information is based on its association with a group belonging to an existing policy.
 
-Currently, communication between lists of groups in the source and destination fields of a policy is bidirectional for ALL and ICMP protocols. Additionally, for TCP and UDP protocols without port limitations defined, it is bidirectional, meaning that destinations can also initiate connections to a group of peers listed in the source field of the policy.
+For ICMP and ALL protocols, as well as for TCP and UDP protocols **without** specific port restrictions, communication between groups listed in the source and destination fields is bidirectional. This means that both source and destination groups can initiate connections with each other. To establish one-way connections, you must specify a protocol (UDP or TCP), along with a port.
 
 <Note>
 If you need to allow peers from the same group to communicate with each other, you can do so by adding the same group to the `Source` and `Destination` lists.
diff --git a/src/pages/how-to/register-machines-using-setup-keys.mdx b/src/pages/how-to/register-machines-using-setup-keys.mdx
index 77389066..c8c5c52f 100644
--- a/src/pages/how-to/register-machines-using-setup-keys.mdx
+++ b/src/pages/how-to/register-machines-using-setup-keys.mdx
@@ -11,7 +11,7 @@ This makes it possible to run automated deployments with infrastructure-as-code
 sudo netbird up --setup-key <SETUP KEY>
 ```
 
-## Types of setup seys
+## 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.
@@ -46,9 +46,6 @@ We recommend limiting the number of times the key can be used, e.g., set it to 3
 
 ## Peer Auto-grouping
 
-<p>
-    <img src="/docs-static/img/architecture/peer-auto-tagging-setupkey.gif" alt="high-level-dia" className="imagewrapper"/>
-</p>
 
 NetBird offers a powerful [access control feature](/how-to/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.
@@ -71,7 +68,7 @@ Then use this key to enroll new machine.
 
 ## Create setup key
 
-Click the `Add Key` button in the `Setup Keys'.
+Go to the `Setup Keys` tab 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.