docs: update terminology in landing page and documentation

Update text to clarify "vibe coding" vs "AI Assisted Engineering" terminology
Make language more approachable for non-technical audiences

Author: devakone

apps/web/src/app/page.tsx

@@ -779,6 +779,12 @@ function MarketingLanding() {
               better. We surface signals from your commit history to shine a light on how you build
               with AI. What feels like you, what feels new, and how your workflow is evolving.
             </p>
+            <p className="max-w-2xl text-sm text-zinc-600">
+              The term “vibe coding” can be polarizing, but it captures the cultural moment around
+              AI-shaped development. We personally prefer “AI Assisted Engineering” because it’s
+              more explicit about the role of AI. This is a playful side project, so we keep it
+              light and approachable for non-technical folks.
+            </p>
           </div>
 
           <div className="flex flex-wrap gap-3">

docs/how-vibed-works.md

@@ -3,7 +3,9 @@
 > **Last Updated:** January 2026  
 > **Maintainer:** Update this document when analysis logic, personas, or metrics change.
 
-Vibed Coding analyzes your git history to reveal your coding style and patterns. Think of it as "Spotify Wrapped for vibe coders." We look at *how* you build, not *what* you build.
+Vibed Coding analyzes your git history to reveal your vibe coding/ AI Assited Engineering style and patterns. Think of it as "Spotify Wrapped for vibe coders." We look at *how* you build, not *what* you build.
+
+Note: The term "vibe coding" can be polarizing, but it captures the cultural moment around AI-shaped development. We personally prefer "AI Assisted Engineering" because it’s more explicit about the role of AI. This is a playful side project, so we lean into the pop framing and keep it approachable for non-technical folks.
 
 ---