diff --git a/docs/archival/run-archival-node.md b/docs/archival/run-archival-node.md
index fe1a379..3c2ce8e 100644
--- a/docs/archival/run-archival-node.md
+++ b/docs/archival/run-archival-node.md
@@ -84,12 +84,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`.
 
-By the way, if you’re familiar with Cargo, you could wonder why not
-run `cargo build -p neard --release` instead.  While this will produce
-a binary, the result will be a less optimized version.  On technical
-level, this is because building via `make neard` enables link-time
-optimisation which is disabled by default.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#3-initialize-working-directory}
@@ -178,12 +172,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`.
 
-By the way, if you’re familiar with Cargo, you could wonder why not
-run `cargo build -p neard --release` instead.  While this will produce
-a binary, the result will be a less optimized version.  On technical
-level, this is because building via `make neard` enables link-time
-optimisation which is disabled by default.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#3-initialize-working-directory-1}
diff --git a/docs/rpc/run-rpc-node.md b/docs/rpc/run-rpc-node.md
index eb34f5f..18092e5 100644
--- a/docs/rpc/run-rpc-node.md
+++ b/docs/rpc/run-rpc-node.md
@@ -83,11 +83,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`.
 
-If you’re familiar with Cargo, you could also run `cargo build -p neard
---release` instead, which might or might not be equivalent to `make release`. It
-is equivalent at the time of writing, but we don't guarantee this. If in doubt,
-consult the `Makefile`, or just stick with `make release`.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#3-initialize-working-directory}
@@ -171,11 +166,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make release`.
 
-If you’re familiar with Cargo, you could also run `cargo build -p neard
---release` instead, which might or might not be equivalent to `make release`. It
-is equivalent at the time of writing, but we don't guarantee this. If in doubt,
-consult the `Makefile`, or just stick with `make release`.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#3-initialize-working-directory-1}
diff --git a/docs/validator/compile-and-run-a-node.md b/docs/validator/compile-and-run-a-node.md
index c723cfd..d8f9008 100644
--- a/docs/validator/compile-and-run-a-node.md
+++ b/docs/validator/compile-and-run-a-node.md
@@ -106,12 +106,7 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`.
 
-By the way, if you’re familiar with Cargo, you could wonder why not
-run `cargo build -p neard --release` instead.  While this will produce
-a binary, the result will be a less optimized version.  On technical
-level, this is because building via `make neard` enables link-time
-optimisation which is disabled by default. The binary path is `target/release/neard`.
-
+The binary path is `target/release/neard`
 
 For `localnet`, you also have the option to build in nightly mode (which is experimental and is used for cutting-edge testing). When you compile, use the following command:
 ```bash
@@ -180,12 +175,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`.
 
-By the way, if you’re familiar with Cargo, you could wonder why not
-run `cargo build -p neard --release` instead.  While this will produce
-a binary, the result will be a less optimized version.  On technical
-level, this is because building via `make neard` enables link-time
-optimisation which is disabled by default.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#initialize-working-directory-1}
@@ -415,12 +404,6 @@ takes approximately 25 minutes). Note that compilation will need over
 with processes being killed, you might want to try reducing number of
 parallel jobs, for example: `CARGO_BUILD_JOBS=8 make neard`.
 
-By the way, if you’re familiar with Cargo, you could wonder why not
-run `cargo build -p neard --release` instead.  While this will produce
-a binary, the result will be a less optimized version.  On technical
-level, this is because building via `make neard` enables link-time
-optimisation which is disabled by default.
-
 The binary path is `target/release/neard`
 
 ### 3. Initialize working directory {#initialize-working-directory-2}