docs/provider: Update Resource Tagging Code Implementation section to…

… show tagging on creation versus not, fix typo

Reference: #10313

.github/CONTRIBUTING.md

@@ -216,7 +216,7 @@ In addition to the below checklist and the items noted in the Extending Terrafor
 
 #### Adding Resource Tagging Support
 
-AWS provides key-value metadata across many services and resources, which can be used for a variety of use cases including billing, ownership, and more. See the [AWS Tagging Stategy page](https://aws.amazon.com/answers/account-management/aws-tagging-strategies/) for more information about tagging at a high level.
+AWS provides key-value metadata across many services and resources, which can be used for a variety of use cases including billing, ownership, and more. See the [AWS Tagging Strategy page](https://aws.amazon.com/answers/account-management/aws-tagging-strategies/) for more information about tagging at a high level.
 
 Implementing tagging support for Terraform AWS Provider resources requires the following, each with its own section below:
 
@@ -255,7 +255,7 @@ More details about this code generation, including fixes for potential error mes
 
 - In the resource Go file (e.g. `aws/resource_aws_eks_cluster.go`), add the following Go import: `"github.com/terraform-providers/terraform-provider-aws/aws/internal/keyvaluetags"`
 - In the resource schema, add `"tags": tagsSchema(),`
-- In the resource `Create` function, implement the logic to convert the configuration tags into the service tags, e.g. with EKS Clusters:
+- If the API supports tagging on creation (the `Input` struct accepts a `Tags` field), in the resource `Create` function, implement the logic to convert the configuration tags into the service tags, e.g. with EKS Clusters:
 
   ```go
   input := &eks.CreateClusterInput{
@@ -276,6 +276,16 @@ More details about this code generation, including fixes for potential error mes
   }
   ```
 
+- Otherwise if the API does not support tagging on creation (the `Input` struct does not accept a `Tags` field), in the resource `Create` function, implement the logic to convert the configuration tags into the service API call to tag a resource, e.g. with CloudHSM v2 Clusters:
+
+  ```go
+  if v := d.Get("tags").(map[string]interface{}); len(v) > 0 {
+    if err := keyvaluetags.Cloudhsmv2UpdateTags(conn, d.Id(), nil, v); err != nil {
+      return fmt.Errorf("error adding CloudHSM v2 Cluster (%s) tags: %s", d.Id(), err)
+    }
+  }
+  ```
+
 - In the resource `Read` function, implement the logic to convert the service tags to save them into the Terraform state for drift detection, e.g. with EKS Clusters (which had the tags available in the DescribeCluster API call):
 
   ```go