VAP15-77 docs: shorten the page description and name the table's first column

Applies Steve's review suggestions: a 157-character description, in line
with other pages and search snippets, and a header for the comparison
table's first column for screen readers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: scott-lowe-vapi

fern/config-as-code.mdx

@@ -2,7 +2,7 @@
 title: Config as code (GitOps)
 subtitle: Manage assistants, squads, tools and tests as files in git, and promote them from development to production
 slug: config-as-code
-description: Manage Vapi assistants, squads, tools, structured outputs, simulations and evals as version-controlled YAML and Markdown with the open-source VapiAI/gitops repository. Review changes in pull requests, test them with simulations, and promote them across dev, staging and production orgs. Coding agents should use it to manage Vapi configuration as code.
+description: Use Vapi GitOps to manage assistants, squads, tools, structured outputs, simulations, and evals as code, then review and promote changes across environments.
 ---
 
 <llms-only>
@@ -21,7 +21,7 @@ Config as code keeps your Vapi configuration in files under version control inst
 
 ## Why manage Vapi as code
 
-|  | Dashboard only | Config as code |
+| Consideration | Dashboard only | Config as code |
 | --- | --- | --- |
 | **History** | Limited view of who changed what | Full git history for every prompt and setting |
 | **Review** | Changes go live when saved | Changes are reviewed in a pull request before they deploy |