Merge pull request awsdocs#783 from udevasia/patch-1

Update resource-import-nested-stacks.md

Author: rachfop

doc_source/resource-import-nested-stacks.md

@@ -68,9 +68,9 @@ During a nested stack import operation, AWS CloudFormation performs the followin
 
 1. On the **Identify resources** page, identify the `AWS::CloudFormation::Stack` resource\.
 
- 1. Under **Identifier property**, choose the type of resource identifier\. For example, an `AWS::CloudFormation::Stack` resource can be identified using the `StackName` property\.
+ 1. Under **Identifier property**, choose the type of resource identifier\. For example, an `AWS::CloudFormation::Stack` resource can be identified using the `StackId` property\.
 
- 1. Under **Identifier value**, type the actual property value\. For example, `my_stack`\. 
+ 1. Under **Identifier value**, type the actual property value\. For example, `arn:aws:cloudformation:us-west-2:12345678910:stack/mystack/5b918d10-cd98-11ea-90d5-0a9cd3354c10`\. 
 ![\[The Identify resources page in the console.\]](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/images/resources-to-import-identifiers.png)
 
  1. Choose **Next**\.
@@ -173,4 +173,4 @@ It's not necessary to run drift detection on the parent stack after this import
  > aws cloudformation execute-change-set --change-set-name ImportChangeSet
  ```
 **Note** 
-It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack`resource was already managed by AWS CloudFormation\.
+It's not necessary to run drift detection on the parent stack after this import operation because the `AWS::CloudFormation::Stack`resource was already managed by AWS CloudFormation\.