diff --git a/README.md b/README.md
index b4f38ea..f16dfb8 100644
--- a/README.md
+++ b/README.md
@@ -109,17 +109,28 @@ vlan pvid 1 99
 ip ssh
 username admin password YourPassword
 end
-copy running-config nvram:config.cfg
+save config
 ```
 
 Replace `1` with the port number your management computer will plug into. Replace `YourPassword` with a strong password (8–32 characters; allowed special characters: `! @ # $ % ^ & * - _ = + [ ] ; : , . /` — no spaces, no quotes).
 
-**ERS 59100 note:** Port numbering on the 59100 is `1/1` through `1/96` for copper and `1/97` through `1/100` for SFP+ uplinks. Substitute accordingly:
+**Port numbering:** On both the ERS 5952 and ERS 59100, use bare port numbers (`1`, `2`, `48`…). There is no slot prefix.
 
-```
-vlan members add 99 1/1
-vlan pvid 1/1 99
-```
+> **What about the switch's existing IP?**
+> Out of the box the switch has `192.168.1.1` on VLAN 1. If your router is also `192.168.1.1`, they will conflict — two devices with the same IP on the same network causes ARP fights and makes both unreliable.
+>
+> This setup deliberately avoids that by putting management traffic on a **separate VLAN (99) with its own subnet (192.168.99.x)**. Your management computer gets a static IP on that subnet and talks to the switch there. The switch's original VLAN 1 address is irrelevant once VLAN 99 is up.
+>
+> If you ever need to change the switch's VLAN 1 IP (e.g. to remove the conflict before VLAN 99 is configured):
+> ```
+> config terminal
+> interface vlan 1
+> ip address 192.168.1.2 255.255.255.0
+> exit
+> ip default-gateway 192.168.1.1
+> exit
+> save config
+> ```
 
 After the last command the switch confirms with `CP1 [07/04/15 12:00:00.000:INFO]: Operation Success` or similar.