first commit - draft clarification on M-A docs

Author: trujillo-adam

content/terraform/v1.14.x (beta)/docs/language/meta-arguments.mdx

@@ -185,17 +185,26 @@ Terraform performs the following operations when you apply a configuration:
 1. Creates resources defined in the configuration that are not associated with a real infrastructure object in the state.
 1. Destroys resources that exist in the state but not in the configuration.
 1. Updates in-place resources whose arguments have changed.
-1. Destroys and re-create resources whose arguments have changed but that Terraform cannot update in-place because of remote API limitations.
+1. Destroys and re-creates resources whose arguments have changed but that Terraform cannot update in-place because of remote API limitations.
 1. Invokes actions that are configured to run during an apply operation.
 
-The `lifecycle` block accepts a rule that customizes how Terraform performs the lifecycle stages for each resource. 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. The following table describes support for each `lifecycle` rule:
+The `lifecycle` block accepts a rule that customizes how Terraform performs the lifecycle stages for each resource. 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. 
 
+### State
+
+Except for `create_before_destroy`, Terraform does not explicitly record a resource's `lifecycle` rule to state. As a result, Terraform destroys the actual infrastructure during an apply operation if you remove the resource's configuration, even if `prevent_destroy` is enabled. Refer to [Remove a resource from state](/terraform/language/state/remove) for instructions on how to remove a resource from state without destroying the actual resource. 
+
+Terraform records the results of `precondition` and `postcondition` checks to state, but not the contents of the checks. Terraform may also record values in `lifecycle` rules as resource dependencies.
+
+### Rules 
+
+The following table describes support for each `lifecycle` rule:
 
 | Rule | Description | Terraform block |
 | --- | --- | --- |
 | `action_trigger` | Terraform runs the configured action when the specified conditions are met. Refer to [Invoke an action](/terraform/language/invoke-actions) for details. | `resource` |
 | `create_before_destroy` | Terraform creates a replacement resource before destroying the current resource. | `resource` |
-| `prevent_destroy` | Terraform rejects operations to destroy the resource and returns an error. | `resource` |
+| `prevent_destroy` | Terraform rejects operations to destroy the resource and returns an error. This rule doesn't prevent Terraform from destroying a resource if you remove its configuration. Refer to [Remove a resource from state](/terraform/language/state/remove) for instructions on how to remove a resource from state without destroying the actual resource. | `resource` |
 | `ignore_changes` | Specifies a list of resource attributes that Terraform ignores changes to. Otherwise, Terraform attempts to update the actual resource to match the configuration. | `resource` |
 | `replace_triggered_by` | Terraform replaces the resource when any of the referenced resources or specified attributes change. | `resource` |
 | `precondition` | Specifies a condition that Terraform evaluates before creating the resource. | `data`, `ephemeral`, `resource` |