diff --git a/docs/modules/ROOT/pages/guides/weights_fees.adoc b/docs/modules/ROOT/pages/guides/weights_fees.adoc
index 8a8e2ac..a0a6e55 100644
--- a/docs/modules/ROOT/pages/guides/weights_fees.adoc
+++ b/docs/modules/ROOT/pages/guides/weights_fees.adoc
@@ -45,7 +45,7 @@ for pallet_name in $pallets; do
 done
 ```
 
-The final step is to automate the steps above. the first step may be automated by enforcing the command in the CI. The second step is automated by integrating a Benchmarking Bot. For an example, see https://github.com/paritytech/command-bot[Parity's Command Bot].
+The final step is to automate the steps above. The first step may be automated by enforcing the command in the CI. The second step is automated by integrating a Benchmarking Bot. For an example, see https://github.com/paritytech/command-bot[Parity's Command Bot].
 
 == More Reading
 
@@ -55,9 +55,7 @@ Technically, *Weight* represents the time it takes to execute code on *productio
 1 unit of weight = 1 picosecond of execution time on target reference hardware
 ```
 
-https://wiki.polkadot.network/docs/maintain-guides-how-to-validate-polkadot#:~:text=Reference%20Hardware%E2%80%8B,instance%20on%20GCP%20and%20c6i.[Polkadot Reference Hardware Docs] provides more information on Polkadot validator hardware requirements.
-
-It is important to ONLY generate weights by running `cargo build --features runtime-benchmarks --release` on *production hardware*.
+It is important to ONLY generate weights on *production hardware*. https://wiki.polkadot.network/docs/maintain-guides-how-to-validate-polkadot#:~:text=Reference%20Hardware%E2%80%8B,instance%20on%20GCP%20and%20c6i.[Polkadot Reference Hardware Docs] provides more information on Polkadot validator hardware requirements.
 
 References:
 ** https://www.shawntabrizi.com/blog/substrate/substrate-weight-and-fees/[Substrate Weight & Fees] by https://github.com/shawntabrizi/[Shawn Tabrizi]