diff --git a/docs/deployment/heroku-deployment.md b/docs/deployment/heroku-deployment.md
index e65f9291c..afd9d2860 100644
--- a/docs/deployment/heroku-deployment.md
+++ b/docs/deployment/heroku-deployment.md
@@ -17,8 +17,3 @@ For more information, see [Using Multiple Buildpacks for an App](https://devcent
 ### rails/webpacker webpack configuration
 If you're using the standard rails/webpacker configuration of webpack, then rails/webpacker
 will automatically modify or create an assets:precompile task to build your assets.
-
-### custom webpack configuration
-If you're a custom webpack configuration, and you **do not have the default
-`config/webpack/production.js`** file, then the `config/initializers/react_on_rails.rb`
-configuration `config.build_production_command` will be used.
diff --git a/docs/guides/configuration.md b/docs/guides/configuration.md
index 04300c66f..7d083bac2 100644
--- a/docs/guides/configuration.md
+++ b/docs/guides/configuration.md
@@ -66,11 +66,8 @@ ReactOnRails.configure do |config|
   # defaults to "" (top level)
   config.node_modules_location = "client" # If using webpacker you should use "".
 
-  # This configures the script to run to build the production assets by webpack . Set this to nil
+  # This configures the script to run to build the production assets by webpack. Set this to nil
   # if you don't want react_on_rails building this file for you.
-  # Note, if you want to use this command then you should remove the file
-  # config/webpack/production.js
-  # If that file exists, React on Rails thinks that you'll use the rails/webpacker bin/webpack compiler.
   config.build_production_command = "RAILS_ENV=production bin/webpack"
 
   # Alternatively, you can also specify a module containing a class method `call`