diff --git a/home.md b/home.md
index 4353a5b..820c578 100644
--- a/home.md
+++ b/home.md
@@ -12,6 +12,8 @@ For detailed information about flakes in general I will refer you to [here](http
 
 "A flake.nix file is an attribute set with two attributes called inputs and outputs. The inputs attribute describes the other flakes that you would like to use; things like nixpkgs or home-manager. You have to give it the url where the code for that other flake is, and usually people use GitHub. The outputs attribute is a function, which is where we really start getting into the nix programming language. Nix will go and fetch all the inputs, load up their flake.nix files, and it will call your outputs function with all of their outputs as arguments. The outputs of a flake are just whatever its outputs function returns, which can be basically anything the flake wants it to be. Finally, nix records exactly which revision was fetched from GitHub in flake.lock so that the versions of all your inputs are pinned to the same thing until you manually update the lock file."
 
+One of the incredible things Flakes do is create a flake.lock file when you run your first rebuild. This file contains the certain packages and their exact versions from whatever branch, stable or unstable, that your pulling from. Every time you rebuild the Flake uses this file to get its packages. This file is only updated when you run *nix flake update* - this means when you get my configuration and run it your running the exact same packages I am. This means no weird bugs due to getting a newer package with breaking changes.
+
 ### What About The ZaneyOS Flake?
 
 My Flake controls where we are getting things from. It also allows me to define variables for username and hostname. **For the options that you as a user may want you should look at options.nix.** When you run the rebuild switch command with the flake argument and give it the ZaneyOS folder it sources the flake.nix that sources system.nix and home.nix.