diff --git a/packer_test/common/plugin_tester/docs/README.md b/packer_test/common/plugin_tester/docs/README.md
index 558957445..103a74184 100644
--- a/packer_test/common/plugin_tester/docs/README.md
+++ b/packer_test/common/plugin_tester/docs/README.md
@@ -33,9 +33,11 @@ packer {
 }
 ```
 
-Note: With the new packer release the init command will try to install the official(Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [official](https://releases.hashicorp.com/) release site.
-Also going forward the official plugins mentioned above will be released through the official release site of hashicorp. so if one need to use new version of official plugins they need to use new packer release. There are no change in the packer init command.
+Note: With the new Packer release starting from version 1.14.0, the packer init command will automatically install official (Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [HashiCorp release site]([official](https://releases.hashicorp.com/)). 
+These official plugins will now be released through the official release site only.
 
+Going forward, to use newer versions of official Packer plugins, you'll need to upgrade to Packer version 1.14.0 or later. If you're using an older version, you can still install plugins, but as a workaround, you'll need to manually install them using the CLI.
+There is no change to the syntax or commands for installing plugins.
 
 #### Manual installation
 
@@ -45,10 +47,6 @@ uncompress it to retrieve the plugin binary file corresponding to your platform.
 To install the plugin, please follow the Packer documentation on
 [installing a plugin](https://www.packer.io/docs/extending/plugins/#installing-plugins).
 
-Note: With the new packer release the init command will try to install the official(Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [official](https://releases.hashicorp.com/) release site.
-Also going forward the official plugins mentioned above will be released through the official release site of hashicorp. so if one need to use new version of official plugins they need to use new packer release. There are no change in the packer plugins install command.
-
-
 #### From Source
 
 If you prefer to build the plugin from its source code, clone the GitHub
diff --git a/website/content/docs/plugins/install.mdx b/website/content/docs/plugins/install.mdx
index 724965d10..bce78f976 100644
--- a/website/content/docs/plugins/install.mdx
+++ b/website/content/docs/plugins/install.mdx
@@ -69,8 +69,11 @@ pinning plugin versions for build reproducibility. Refer to the [`packer` block
 
 1. Run the `packer init` command. Packer lists all installed plugins then installs the latest plugin version matching the version constraints specified in the `required_plugins` block. Refer to the [`init` command reference](/packer/docs/commands/init) for additional information.
 
-~> Note: With the new packer release the init command will try to install the official(Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [official](https://releases.hashicorp.com/) release site.
-Also going forward the official plugins mentioned above will be released through the official release site of hashicorp. so if one need to use new version of official plugins they need to use new packer release. There are no change in the packer init command.
+~> Note: With the new Packer release starting from version 1.14.0, the packer init command will automatically install official (Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [HashiCorp release site]([official](https://releases.hashicorp.com/)).
+These official plugins will now be released through the official release site only.
+
+Going forward, to use newer versions of official Packer plugins, you'll need to upgrade to Packer version 1.14.0 or later. If you're using an older version, you can still install plugins, but as a workaround, you'll need to manually install them using the CLI.
+There is no change to the syntax or commands for installing plugins.
 
 ## Manually install plugins using the CLI
 
@@ -92,10 +95,6 @@ $ packer plugins install --path happycloud github.com/hashicorp/happycloud
 
 Refer to the [`packer plugins install`](/packer/docs/commands/plugins/install) reference for additional information.
 
-~> Note: With the new packer release the init command will try to install the official(Amazon, Ansible, Azure, Docker, GoogleCloudPlatform, Qemu, Vagrant, VirtualBox) plugins from the [official](https://releases.hashicorp.com/) release site.
-Also going forward the official plugins mentioned above will be released through the official release site of hashicorp. so if one need to use new version of official plugins they need to use new packer release. There are no change in the packer plugins install command.
-
-
 ## Upgrade plugins
 
 To upgrade plugins that are already installed, run the `packer init` with the `--upgrade` flag. Packer retrieves the latest versions of installed plugins specified in the template configuration.