ddymko · Aug 3, 2026 · Aug 3, 2026
diff --git a/temp_backup/images/freight.jpg b/temp_backup/images/freight.jpg
diff --git a/temp_backup/images/freight.png b/temp_backup/images/freight.png
diff --git a/temp_backup/readme.md b/temp_backup/readme.md
diff --git a/website/docs/advanced.md b/website/docs/advanced.md
@@ -1,4 +1,4 @@
-# Advanced Configuration
+npm # Advanced Configuration
 
 Take full control of your Git hooks with advanced configuration options and deep dives into Freight's execution model.
 

diff --git a/website/docs/best-practices.md b/website/docs/best-practices.md
@@ -3,10 +3,9 @@
 Follow these guidelines to ensure a smooth and consistent experience for your entire team using Freight.
 
 ### Version Control
-It is crucial to commit both the `railcar.json` configuration file AND the `conductor` binary to your repository.
+It is crucial to commit the `railcar.json` configuration file.
 
 *   **railcar.json**: Defines what hooks run and what they do.
-*   **conductor**: Ensures everyone is using the exact same orchestrator version without needing to install external dependencies like Node.js or Python.
 
 :::info
 By committing the binary, you guarantee that Git hooks will work immediately upon cloning the repository, regardless of the developer's local environment.

diff --git a/website/docs/installation.md b/website/docs/installation.md
@@ -65,9 +65,6 @@ freight init --allow pre-commit,commit-msg
 
 This is particularly useful for **incremental adoption**. If you already have a complex set of hooks and only want to move `pre-commit` to Freight for now, you can do so without affecting your other hooks.
 
-:::tip Pro-Tip
-For total team portability, **commit the `conductor` binary** directly to your repository. This ensures that every team member (and your CI/CD pipeline) can execute hooks immediately without needing to install the `freight` CLI tool themselves.
-:::
 
 ### 3. Verify
 Add a simple command to your `railcar.json` and trigger a hook: