diff --git a/content/packaging/guide/en.md b/content/packaging/guide/en.md
index c61eb9e..31e361a 100644
--- a/content/packaging/guide/en.md
+++ b/content/packaging/guide/en.md
@@ -6,7 +6,7 @@ We assume you already have a working knowledge of Linux based systems, and are a
 
 ### Supported targets  
 
-You may either build natively on your Solus installation using the `ypkg` tool directly, or or on supported distributions in a chroot environment via the `evobuild` tool. Please note that in order to use `evobuild` from other distributions, your 
+You may either build natively on your Solus installation using the `ypkg` tool directly, or or on supported distributions in a chroot environment via the `solbuild` tool. Please note that in order to use `solbuild` from other distributions, your
 kernel must support `overlayfs`, which must be enabled and loaded.
 
 ### Overview  
diff --git a/content/packaging/packaging-practices/en.md b/content/packaging/packaging-practices/en.md
index 5ad6a63..1a7ac3b 100644
--- a/content/packaging/packaging-practices/en.md
+++ b/content/packaging/packaging-practices/en.md
@@ -69,7 +69,7 @@ When submitting a change `package.yml`, it must be accompanied by its correspond
 
 When providing a new version of a package, or a fix, always ensure you increment the `release` number by 1. This ensures that users of your package are correctly updated to the latest version.
 
-Never submit a package without having first tested it, and ensuring it builds within `evobuild`, a clean chroot environment.
+Never submit a package without having first tested it, and ensuring it builds within `solbuild`, a clean chroot environment.
 
 ### Generating a Package.yml