diff --git a/website/content/docs/commands/init.mdx b/website/content/docs/commands/init.mdx
index dd353f82d..79d63593c 100644
--- a/website/content/docs/commands/init.mdx
+++ b/website/content/docs/commands/init.mdx
@@ -65,19 +65,20 @@ constraint
 string](/docs/templates/hcl_templates/blocks/packer#version-constraints). The
 plugins will be installed in the [Plugin
 Directory](/docs/configure#packer-s-plugin-directory).
+See [Installing Plugins](/docs/plugins#installing-plugins) for more information on how plugin installation works.
 
 ### Implicit required plugin
 
-Starting from Version `1.8` many plugins will move out from Packer core. This is
-part of a set of breaking changes made to decouple Packer releases from a Plugin
-release. To make the transition easier we will tag components of these plugins
-as "moved out". If one of the components of a moved out plugin is used in a
-config file, then it is implied that this plugin is required. Packer init will
-install that plugin then display a warning and a suggestion. We recommend on
-using a `required_plugin` block and setting a version to avoid surprises in the
-future.
+This is part of a set of breaking changes made to decouple Packer releases from
+plugin releases. To make the transition easier, we will tag components of these
+plugins as "moved out". If one of the components of a moved out plugin is used
+in a config file, but there is no mention of that plugin in the
+"required_plugin" block, then Packer init will automatically download and
+install that plugin. Packer will then display a warning and suggest that you
+add the plugin to your required_plugin block. We recommend you use the
+required_plugin block even if you are only using official plugins, because it
+allows you to set the plugin version to avoid surprises in the future.
 
-See [Installing Plugins](/docs/plugins#installing-plugins) for more information on how plugin installation works.
 ## Options
 
 - `-upgrade` - On top of installing missing plugins, update installed plugins to