diff --git a/content/other-tools/02_pixi_build.md b/content/other-tools/02_pixi_build.md
index 29d72ba..7357e3e 100644
--- a/content/other-tools/02_pixi_build.md
+++ b/content/other-tools/02_pixi_build.md
@@ -14,7 +14,7 @@ To learn the sections and functionalities by example rather than by inspection o
 When building conda packages, recipes have the concept of `build`, `host`, and `run` requirements.
 
 * `build`: Tools that are used to perform the actual build (e.g. `cmake`, `ninja`)
-* `host`: Packages that supply development requirements for the package you're building, like headers or shared libraries that are linked against (e.g. `boost-devel`)
+* `host`: Packages that supply development requirements for the package you're building, like headers or shared libraries that are linked against (e.g. `libboost-devel`)
 * `run`: The requirements of your package to actually run (e.g. your `pyproject.toml` `dependencies`)
 
 :::
diff --git a/slides/5_02_pixi_build.md b/slides/5_02_pixi_build.md
index 1df1a54..55e3a5e 100644
--- a/slides/5_02_pixi_build.md
+++ b/slides/5_02_pixi_build.md
@@ -34,7 +34,7 @@ When building conda packages, recipes have the concept of `build`,
   (e.g. `cmake`, `ninja`)
 - `host`: Packages that supply development requirements for the
   package you're building, like headers or shared libraries that are
-  linked against (e.g. `boost-devel`)
+  linked against (e.g. `libboost-devel`)
 - `run`: The requirements of your package to actually run
   (e.g. your `pyproject.toml` `dependencies`)