Update website/content/guides/1.7-plugin-upgrade/index.mdx

Co-authored-by: Sylvia Moss <moss@hashicorp.com>

website/content/guides/1.7-plugin-upgrade/index.mdx

@@ -21,7 +21,7 @@ github.com/hashicorp/packer with github.com/hashicorp/packer-plugin-sdk.
 
 But some of the import paths have changed more than that because we've refactored the SDK some to make it easier to discover and use helpful modules. Here are a few common paths below:
 
-github.com/hashicorp/packer-plugin-sdk/template/config => github.com/hashicorp/packer-plugin-sdk/template/config
+github.com/hashicorp/packer/template/config => github.com/hashicorp/packer-plugin-sdk/template/config
 github.com/hashicorp/packer/packer => github.com/hashicorp/packer-plugin-sdk/packer
 github.com/hashicorp/packer/template/interpolate => github.com/hashicorp/packer-plugin-sdk/template/interpolate
 
@@ -179,4 +179,4 @@ And then reference your plugin in the Packer template using "vsphere-iso" and "v
 
 You can still use the `DEFAULT_NAME` constant with a set implementation; in this example, whatever you register with the DEFAULT_NAME will be referenced in the Packer template as "vsphere". You can only register one plugin per plugin set using the DEFAULT_NAME
 
-We will soon write a follow-up guide explaining how to register you new plugin set with HashiCorp.
+We will soon write a follow-up guide explaining how to register you new plugin set with HashiCorp.