moved resource identity concept to overview page

Author: trujillo-adam

content/terraform/v1.14.x (alpha)/docs/language/import/bulk.mdx

@@ -14,20 +14,10 @@ For organizations with large sets of infrastructure resources, manually identify
 Complete the following steps to find and import resources in bulk:
 
 - Search for resources: Create `list` blocks to search for existing resources.
-- Generate configuration: Use the Terraform command to generate `resource` and `import` blocks for importing the resources. The configuration also includes the [resource identity](#resource-identity). 
-
+- Generate configuration: Use the Terraform command to generate `resource` and `import` blocks for importing the resources. The configuration also includes the [resource identity](/terraform/language/import#resource-identity). 
 - Import resources: Copy the generated configuration into your main.tf file and run a `terraform apply` command to import the resources.
 - After importing resources, you can remove the generated `import` block or keep it as an historical record.
 
-### Resource identity
-
-Terraform uniquely identifies resources according to either the ID assigned by the cloud provider or a collection of specific attributes defined by the provider. For example, the `s3_bucket` resource available in the AWS provider uniquely identifies buckets according to the following attributes:
-
-- `account_id`
-- `bucket`
-- `region`  
-
-Refer to your provider documentation for information about resource identities. 
 
 ## Requirements
 

content/terraform/v1.14.x (alpha)/docs/language/import/index.mdx

@@ -22,3 +22,17 @@ When you need to identify and import large sets of infrastructure resources, you
 The workflow for importing single resources or small batches of resources works best when you can easily access unique infrastructure resource IDs and other attributes from your cloud provider. In this workflow, manually write `import` and `resource` blocks and run the `terraform apply` command to import the resources. 
 
 Alternatively, you can write only the `import` block and run the `terraform plan` command with the `generate-config-out` flag to generate the `resource` blocks. Refer to [Import a single resource](/terraform/language/import/single-resource) for more information.  
+
+## Resource identity
+
+Terraform uniquely identifies resources according to either the ID assigned by the cloud provider or a collection of specific attributes defined by the provider. To reference a resource identity in Terraform configuration, you can use either `id` or `identity` attribute. 
+
+The `identity` attribute for `s3_bucket` resources available in the AWS provider, for example, uniquely identifies buckets according to the following attributes:
+
+- `account_id`
+- `bucket`
+- `region`  
+
+To reference the unique identity of an `aws_instance` resource, you can use the `id` attribute.  
+
+Refer to your provider documentation for information about how to reference resource identities. For information about referencing resource identities in Terraform configuration, refer to the [`import` block reference](/terraform/language/block/import).

content/terraform/v1.14.x (alpha)/docs/language/import/single-resource.mdx

@@ -48,7 +48,7 @@ You can include [meta-arguments](/terraform/language/meta-arguments) to modify h
 
 ## Define an `import` block
 
-Add an `import` block and specify the ID of an existing resource and [destination resource address](#define-a-destination-resource) to import to. Cloud providers use different methods of identifying resources. As a result, the ID depends on your cloud vendor and the kind of resource you are importing. Refer to the provider documentation for the resource you want to import for details.
+Add an `import` block and specify the [resource identity](/terraform/language/import#resource-identity) of an existing resource and [destination resource address](#define-a-destination-resource) to import to. Cloud providers use different methods of identifying resources. As a result, the identity depends on your cloud vendor and the kind of resource you are importing. Refer to the provider documentation for the resource you want to import for details.
 
 Use the following syntax to configure the `import` block: