Unsupported Config as Code Scenarios page has typo and outdated info about runbook support #3026
Description
Page: Unsupported Configuration as Code Scenarios
Source file: /docs/blob/main/src/pages/docs/projects/version-control/unsupported-config-as-code-scenarios.md
There are a few issues on this warning box on the page:
Configuration as Code currently supports storing the deployment process and non-sensitive variables for a project in the Git repo. It does not store or runbook processes or sensitive variables.
1. Grammar error in "Syncing multiple instances" section
The warning box reads:
It does not store or runbook processes or sensitive variables.
There is a stray "or". It should read: "It does not store runbook processes or sensitive variables."
2. Outdated information — runbook processes are now supported
The warning box states that Config as Code does not store runbook processes. However, the Configuration as Code reference page now lists Runbook Process and Runbook Settings as version-controlled resources saved to Git.