From b3ab5ee834a9fe8d77430c5f44dec34da0c1a457 Mon Sep 17 00:00:00 2001
From: Henrik Karlsson <i97henka@gmail.com>
Date: Fri, 9 Feb 2024 10:45:52 +0000
Subject: [PATCH] adding example to make clear what is meant by a nix
 repository.

---
 pills/12-inputs-design-pattern.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pills/12-inputs-design-pattern.xml b/pills/12-inputs-design-pattern.xml
index 97b9f08..498e354 100644
--- a/pills/12-inputs-design-pattern.xml
+++ b/pills/12-inputs-design-pattern.xml
@@ -14,7 +14,7 @@
   <section>
     <title>Repositories in Nix</title>
     <para>
-      Nix is a tool for build and deployment, it does not enforce any particular repository format. A repository of packages is the main usage for Nix, but not the only possibility. It's more like a consequence due to the need of organizing packages.
+      Nix is a tool for build and deployment, it does not enforce any particular repository format. A repository of packages, like for example <link xlink:href="https://github.com/NixOS/nixpkgs">nixpkgs</link>, is the main usage for Nix, but not the only possibility. It's more like a consequence due to the need of organizing packages.
     </para>
     <para>
       Nix is a language, and it is powerful enough to let you choose the format of your own repository. In this sense, it is not declarative, but functional.