Not exactly Linux related but I think it is in the same spirit.
I self-host a git server at home which uses non-default SSH port. In my home network I did a local port-forward from port 22, so that I didn’t have to specify it every time I connect to it. I somehow messed up the port-forward rule, so it routed all outbound traffic to port 22 to my home server. I didn’t notice this for a while.
After a few months I tried to connect to another SSH server (public, work-related) and it failed. I tried the same with a VPN with an exit node in another country and this time it worked. I got scared that my ISP or some adversary was trying to do a MITM attack. I remembered my local network configuration about an hour later. Gave myself a big scare that day. 😅



In some atomic distributions like Vanilla OS and SteamOS you have two mostly (AFAIK) identical root partitions. Let’s say that you boot partition A. You install a system update, and now partition B contains the updated OS. Your bootloader also remembers which partition is up-to-date and boots off of that one next time. Now, you boot with partition B. There is a system update and the latest version of the OS is installed to partition A. It now repeats as you might expect.
The goal is to have both versions readily available so that if an update introduces problems you can always continue to use the old one. This is not something you are meant to think about or tinker with. If you need more customization, I think you might wanna consider a more traditional distro.