## Summary The example directory name in our scaffolding instructions was inconsistent across docs: | Source | Name used | |--------|-----------| | `create-twenty-app` README | `my-twenty-app` | | Getting Started (developer docs) | `my-twenty-app` | | Core Concepts → Apps (intro doc) | `my-app` ⚠️ | | `twenty-sdk` README | `my-app` ⚠️ | This means a user reading the high-level Apps intro sees `my-app`, then the official Getting Started guide and the scaffold use `my-twenty-app`. Small but eroding for confidence on the very first command. This PR aligns the two outliers to `my-twenty-app`. The `twenty-my-app` example in `publishing.mdx` is left alone — that's an npm package name example, not a directory name (different concept). ## Test plan - [x] `grep -rn "my-app\b"` over source docs returns no other directory-name occurrences - [ ] Verify rendered docs after merge Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>