docs: Address CodeRabbit nitpick suggestions

- Clarify that !terraform.state returns null when state file doesn't exist
- Enhance YQ expression comments in store.get.mdx to be more specific

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: aknysh

website/docs/functions/yaml/store.get.mdx

@@ -128,13 +128,13 @@ from complex data structures:
 
 <File title="stack.yaml">
 ```yaml
-# Extract a field from a JSON object
+# Extract database host from app-config in Redis
 database_host: !store.get redis app-config | query .database.host
 
-# Get the first item from an array
+# Get the first availability zone from Azure Key Vault array
 primary_zone: !store.get azure-keyvault availability-zones | query .[0]
 
-# Extract nested values with a default
+# Extract API key from SSM config with empty object fallback
 api_key: !store.get ssm /external/config | default "{}" | query .api.key
 ```
 </File>

website/docs/functions/yaml/terraform.state.mdx

@@ -559,5 +559,5 @@ vars:
 
  - Be mindful of disaster recovery (DR) implications when using it across regions.
 
- - Consider cold-start scenarios: if the dependent component has not yet been provisioned, the `!terraform.state` function will return `null`.
+ - Consider cold-start scenarios: if the referenced component's state file doesn't exist (e.g., not yet provisioned), `!terraform.state` returns `null`.
    Use the YQ `//` operator to provide default values for components that may not be provisioned yet (see [Using YQ Expressions to provide a default value](#using-yq-expressions-to-provide-a-default-value)).