build: updated documentation reflecting cloud backend override functionality

website/docs/language/files/override.mdx

@@ -150,3 +150,8 @@ In both the `required_version` and `required_providers` settings, each override
 constraint entirely replaces the constraints for the same component in the
 original block. If both the base block and the override block both set
 `required_version` then the constraints in the base block are entirely ignored.
+
+If a `cloud` block is set within the original configuration's `terraform` block and a `backend` block
+is set in the override file, then the backend specified by the `backend` block is used upon merging.
+Similarly, if a `backend` block is set within the original configuration's `terraform` block
+and a `cloud` block is set in the override file, then the backend specified by the `backend` block is used upon merging.

website/docs/language/settings/terraform-cloud.mdx

@@ -28,6 +28,8 @@ terraform {
 }
 ```
 
-You cannot use the CLI integration and a [state backend](/language/settings/backends) in the same configuration; they are mutually exclusive. A configuration can only provide one `cloud` block and the `cloud` block cannot refer to named values like input variables, locals, or data source attributes.
+You cannot use the CLI integration and a [state backend](/language/settings/backends) in the same configuration; they are mutually exclusive.
+A configuration can only provide one `cloud` block and the `cloud` block cannot refer to named values like input variables, locals, or data source attributes.
+Note that a `cloud` block can be overridden by a state backend in an [override file](/language/files/override#merging-terraform-blocks).
 
 Refer to [Using Terraform Cloud](/cli/cloud) in the Terraform CLI docs for more information.