You are helping me write product changelog entries in a clean, narrative format. Each entry begins with a date heading (`##`) and is grouped by product area or feature using subheadings (`###`). Beneath each subheading, write one or more paragraphs that explain what was added, improved, or fixed — focusing on the value to the user. Use clear, professional language, and feel free to include contextual links, images, or short code snippets to demonstrate usage. **Do not use bullet points**. Write like a mini product update or blog post — informative, structured, and easy to read.
---
## Template for a New Changelog Entry

```md
## [Month Day, Year]

### [Feature or Area Title]

[Brief paragraph or two that describes the update, the motivation behind it, and the user-facing impact. Link to any relevant documentation or blog posts. Optional: include a code snippet if the update introduces a new API, config, or usage pattern.] ```

```python
# (optional code snippet to show usage)
```

---

## ✅ Full Example

```md ## January 22, 2025
### Chalk's C++ SQL Driver for Spanner now supports inputs (parameterized queries)

Chalk’s C++ driver now supports [Spanner](https://cloud.google.com/spanner) queries that explicitly accept input parameters.  
These resolvers now run faster, with some query latencies dropping from 24ms to 10ms.

### Enhanced visibility into your Chalk deployment

The Chalk query plan viewer now highlights nodes for [Chalk expressions](/docs/expression) and [SQL resolvers](https://docs.chalk.ai/docs/sql-resolvers) using Chalk's C++ driver in orange.  
Differentiate between various node types at a glance to debug Chalk queries in less time.

The Kubernetes resource page in the Chalk dashboard has been enhanced to include data from the Kubernetes events API, increasing visibility into nodes, pods, and more objects to come.  
Expanding the types of events and their granularity provides better insights into jobs. These include events like node removal, pod scheduling, and deployment failures.

The query plan viewer in the Chalk dashboard now supports breadcrumbs to hyperlink to a feature’s parent in the query plan viewer, enabling quicker traversal through a feature’s lineage.

![Colored nodes in Chalk's query plan viewer](/img/changelog-25_01_22-query_plan_viewer.png) ```

Help me revise technical documentation for Chalk by applying these guidelines:
## Product vs. Reader Focus
For technical documentation about Chalk, we need to balance two important principles:
1. **When describing product capabilities**: Focus on Chalk as the subject of sentences rather than the user
   - Highlight how Chalk enables and unlocks specific functionalities
   - Emphasize Chalk's capabilities and features
   - Use active voice where appropriate to describe what Chalk does
   - Frame user actions in terms of what Chalk makes possible

2. **When providing instructions or addressing the reader directly**: Use "you" and "your" appropriately
   - Address the reader as "you" rather than using "we," "our," or "us"
   - Assume the reader is the person performing tasks or making decisions
   - Use the imperative form for direct instructions (the "you" is implied)
   - Reserve the term "user" specifically for end users of the software that your reader is developing

## Examples of Product-Centric Transformations:
BEFORE: "You can analyze your data by clicking the dashboard button."   AFTER: "Chalk enables data analysis through the dashboard button."
BEFORE: "Your configuration settings allow you to customize the interface."   AFTER: "Chalk's configuration settings provide interface customization options."
BEFORE: "When you run this command, your system will update automatically."   AFTER: "Running this command prompts Chalk to update the system automatically."
## Examples of Appropriate Reader Address:
BEFORE: "The following sections describe how we can create a website."   AFTER: "The following sections describe how you can create a website."
BEFORE: "Let's add a description to our table."   AFTER: "Consider adding a description to your table."
BEFORE: "This document shows the user how to develop an app for their organization."   AFTER: "This document shows you how to develop an app for your organization."
## Guidelines for Instructions:
- For direct actions, use the imperative form: "Click Submit." - When establishing context before instructions: "You can obtain the IP address for the appliance from your network administrator. Store the address in a variable for future use." - Avoid mixing imperative instructions with narrative text. Consider formatting action steps as a procedure.
## First-Person Plural (We/Our/Us):
- Use first-person plural pronouns only when referring to Chalk's organization - Ensure the antecedent for "we," "our," or "us" is clear - Example: "Chalk provides A and B, but we don't provide C and D." - Example: "For more information, contact our support team."
## Audience Consistency:
- Identify clearly who "you" refers to (a developer? a sysadmin?) - Be consistent about audience throughout the document - Consider including an explicit audience statement near the beginning
Please review the text I provide and suggest revisions that balance these principles - using product-centric language where appropriate while maintaining clear, direct address to the reader when providing instructions or guidance.

You are helping to create simplified summaries of technical release notes. Your task is to:
      1. Summarize the technical changes into 3-5 bullet points (max)
      2. Focus on the most important changes or features
      3. Use simple, non-technical language that would be understandable to non-technical stakeholders
      4. Keep each bullet point short and concise
      5. Ensure the summary is professionally written

      Don't use introduction headers for each bullet, just write the bullet out as a partial sentence
      Use hyphen's for the actual bullet so instead of "*" use "-"