diff --git a/docs/compilation.md b/docs/compilation.md
index 8021e5bd..e47cc46f 100644
--- a/docs/compilation.md
+++ b/docs/compilation.md
@@ -34,9 +34,10 @@ If you're creating a package that relies on a custom build of `better-sqlite3`,
 2. Unzip the compressed archive
 3. Move the `sqlite3.c` and `sqlite3.h` files to your project folder
 4. Add a `preinstall` script to your `package.json`, like the one shown above
-5. Make sure the `--sqlite3` flag points to the location of your `sqlite3.c` and `sqlite3.h` files
-6. Define your preferred [compile time options](https://www.sqlite.org/compile.html) at the top of `sqlite3.c`
-7. Run `npm install` in your project folder
+6. Make sure the `--sqlite3` flag points to the location of your `sqlite3.c` and `sqlite3.h` files
+7. Define your preferred [compile time options](https://www.sqlite.org/compile.html) at the top of `sqlite3.c`
+8. Make sure to remove `better-sqlite3` from your `dependencies`
+9. Run `npm install` in your project folder
 
 If you're using a SQLite3 encryption extension that is a drop-in replacement for SQLite3 (such as [SEE](https://www.sqlite.org/see/doc/release/www/readme.wiki) or [sqleet](https://github.com/resilar/sqleet)), then simply replace `sqlite3.c` and `sqlite3.h` with the source files of your encryption extension.