Apply suggestions from code review

Author: trujillo-adam

content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx

@@ -23,13 +23,21 @@ the processing happens too early for arbitrary expression evaluation.
 Support for each lifecycle rule varies across Terraform configuration blocks. Refer to the reference documentation for the Terraform block you are adding to your configuration for details. 
 
 Depending on the block you are configuring, you may be able to use one or more of the following rules.
+
 ### `create_before_destroy` 
 
 By default, when Terraform must change a resource argument that cannot be updated in-place due to remote API limitations, Terraform destroys the existing object and then create a new replacement object with the new configured arguments. Use the `create_before_destroy` rule to instruct Terraform to create a replacement resource before destroying the current resource. 
 
 This is an opt-in behavior because many remote object types have unique name requirements or other constraints that must be accommodated for both a new and an old object to exist concurrently. Some resource types offer special options to append a random suffix onto each object name to avoid collisions, for example. Terraform CLI cannot automatically activate such features, so you must understand the constraints for each resource type before using `create_before_destroy` with it.
 
-Note that Terraform propagates and applies the `create_before_destroy` meta-attribute behavior to all resource dependencies. For example, if `create_before_destroy` is enabled on resource `A` but not on resource `B`, but resource `A` is dependent on resource `B`, then Terraform enables `create_before_destroy` for resource `B` implicitly by default and stores it to the state file. You cannot override `create_before_destroy`
+#### `create_before_destroy` and resource dependencies
+
+Terraform propagates and applies `create_before_destroy` behavior to all resource dependencies. For example: 
+
+- `create_before_destroy` is enabled on resource `A` but not on resource `B`.
+- Because resource `A` is dependent on resource `B1, Terraform enables `create_before_destroy` for resource `B` implicitly by default and stores it to the state file. 
+
+As a result, you cannot override `create_before_destroy`
 to `false` on resource `B` because that would imply dependency cycles in the graph.
 
 When the resource contains a provisioner that runs during the `destroy` operation,  setting `create_before_destroy` to `true` also prevents the provisioner from running.