diff --git a/src/bonsai/docs/guides/development/installation.rst b/src/bonsai/docs/guides/development/installation.rst
index 98db8fa41e..3992c50701 100644
--- a/src/bonsai/docs/guides/development/installation.rst
+++ b/src/bonsai/docs/guides/development/installation.rst
@@ -174,10 +174,16 @@ in the `rem` tags.
 After you modify your code in the Git repository, you will need to restart
 Blender for the changes to take effect.
 
+If there are changes to the IfcOpenShell binaries, you may replace the two
+``*ifcopenshell_wrapper*`` files with new ones downloaded from the automated
+`IfcOpenShell builds directory <https://builds.ifcopenshell.org/>`__.
+
 The downside with this approach is that if a new dependency is added, or a
-compiled dependency version requirement has changed, or the build system
-changes, you'll need to fix your setup manually. But this is relatively rare.
-Reviewing the Makefile history, `here <https://github.com/IfcOpenShell/IfcOpenShell/commits/v0.8.0/src/bonsai/Makefile>`__, is one quick way to see if a dependency has changed.  
+compiled dependency has changed (that is not available via the build
+directory), or the build system changes, you'll need to fix your setup
+manually. But this is relatively rare. Reviewing the Makefile history, `here
+<https://github.com/IfcOpenShell/IfcOpenShell/commits/v0.8.0/src/bonsai/Makefile>`__,
+is one quick way to see if a dependency has changed.
 
 .. seealso::