Fix double introduction of import syntax

[OJFord]

Related Issue

Fixes #552

Description

Prevents an odd-reading double introduction of how to import a resource:

Import is supported using the following syntax:

The terraform import command can be used, for example:

terraform import wireguard_asymmetric_key.example "EFr5/97eoK32SeMingmUqJpE4TL21nckcl2jQ9ZT82g="

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

No

[Copilot]

Pull request overview

This PR fixes redundant text in the Terraform resource documentation template by removing a duplicate introduction to the Import section.

Changes:

• Removed the redundant "Import is supported using the following syntax:" line from the resource documentation template

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[OJFord]

I don't understand the check failures, they don't seem relevant but I've rebased and they're passing on master, so if this is something you'd otherwise accept I'd appreciate a pointer! Cheers.

[OJFord]

@ansgarm @austinvalle @rainkwan sorry for the ping - could someone review please?

[OJFord]

@gbaker-ibm @SBGoods am I missing something here, is this not an issue for all providers using imports currently?

This is presently stopping me upgrading the docs plugin in wireguard provider from v0.21.0, since the unexpected diff doesn't seem to make sense.