chore: remove repetitive words

Signed-off-by: pavedroad <qcqs@outlook.com>

website/content/docs/templates/hcl_templates/functions/contextual/env.mdx

@@ -28,7 +28,7 @@ input variables, input variables remain as the single source of input to a
 template that a user can easily discover using `packer inspect`.
 
 When the environment variable is not set at all -- not even with the empty
-string -- the value returned by `env` will be an an empty string. It will still
+string -- the value returned by `env` will be an empty string. It will still
 be possible to set it using other means but you could use [custom validation
 rules](/packer/docs/templates/hcl_templates/variables#custom-validation-rules) to error in that case
 to make sure it is set, for example:

website/content/guides/1.7-template-upgrade.mdx

@@ -65,7 +65,7 @@ we suggest you reach out to the plugin maintainers and ask for an upgrade; the P
 maintainer-focused guide [here](/packer/guides/1.7-plugin-upgrade).
 
 Check the table below to better understand whether your plugin is compatible with `packer init`, with manual
-installation, or with both for the the Packer version you are using.
+installation, or with both for the Packer version you are using.
 
 | Packer Core Version | Single Component Plugin - API v4                  | Single Component Plugin - API v5.0                | Multi Component Plugin - API v5.0                         |
 | ------------------- | ------------------------------------------------- | ------------------------------------------------- | --------------------------------------------------------- |

website/content/partials/packer-plugin-sdk/communicator/SSH-not-required.mdx

@@ -76,7 +76,7 @@
   File Transfer Protocol.
   
   **NOTE**: Guests using Windows with Win32-OpenSSH v9.1.0.0p1-Beta, scp
-  (the default protocol for copying data) returns a a non-zero error code since the MOTW
+  (the default protocol for copying data) returns a non-zero error code since the MOTW
   cannot be set, which cause any file transfer to fail. As a workaround you can override the transfer protocol
   with SFTP instead `ssh_file_transfer_protocol = "sftp"`.