# The request: move the word "in" to the second line. The word "in". Two letters.

> "apologies on how minor this is, but the client was very particular haha"

This is the Markdown copy of https://usesuperflow.ai/bug-book/very-particular, published for AI agents and scripts. The HTML page is canonical.

## Key facts

| Field | Value |
| --- | --- |
| Page type | Bug Book entry |
| URL | https://usesuperflow.ai/bug-book/very-particular |
| Issue type | Copy |
| Severity | Mild |
| Status | Resolved |
| Site | Client site (agency-built) |
| Platform | Webflow |
| Captured on | Chrome, macOS, Desktop |
| Date | 2025-12-01 |

## Why it matters

The pre-apology, the "haha" absorbing the client's energy, the surgical precision of a two-letter line-break request - this is the account manager's whole job in one sentence: translating "very particular" into something a developer can act on without anyone crying.

## Outcome

Resolved. "in" now lives on line two, exactly where the client needed it.

## The thread

- **Account manager:** apologies on how minor this is, but the client was very particular haha, can you have 'in' drop down to the second line with the city and state?

## About Superflow

Superflow is a website and creative-asset review tool. Its agents watch every page of a site, report what changed, and route findings to the people who approve them. Teams leave contextual feedback on live sites, staging environments, PDFs, images, videos, and Lottie animations, and comments sync two-way with Asana, ClickUp, Monday, Slack, Webflow, and Google Tag Manager.

Machine-readable entry points:

- Site index: https://usesuperflow.ai/llms.txt
- Full site content in one fetch: https://usesuperflow.ai/llms-full.txt
- Free tools, with a Markdown copy of each: https://usesuperflow.ai/tools.md
- MCP server (Streamable HTTP, no account and no API key): https://usesuperflow.ai/api/mcp
- Agent card: https://usesuperflow.ai/.well-known/agent-card.json