diff --git a/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md b/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md
index 481ffd476..08707e336 100644
--- a/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md
+++ b/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md
@@ -2,7 +2,7 @@
 
 # Towards reproducibility: pinning Nixpkgs
 
-In various Nix examples, you'll often see references to [\<nixpkgs>](https://github.com/NixOS/nixpkgs), as follows.
+In various Nix examples, you'll often see the following:
 
 ```nix
 { pkgs ? import <nixpkgs> {} }:
@@ -10,6 +10,11 @@ In various Nix examples, you'll often see references to [\<nixpkgs>](https://git
 ...
 ```
 
+:::{note}
+`<nixpkgs>` points to the file system path of some revision of {term}`Nixpkgs`.
+Find more information on [lookup paths](lookup-path-tutorial) in [](reading-nix-language).
+:::
+
 This is a **convenient** way to quickly demonstrate a Nix expression and get it working by importing Nix packages.
 
 However, <ref-search-path>**the resulting Nix expression is not fully reproducible**.