docs: Refine FAQ metaphors for SEO clarity (closes #8359)

Author: tobiu

apps/portal/index.html

@@ -171,7 +171,7 @@
                     "name": "Why is Neo.mjs called an 'Application Engine' instead of a framework?",
                     "acceptedAnswer": {
                         "@type": "Answer",
-                        "text": "Traditional frameworks (Toyota) are libraries that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs (F1) is a true runtime engine, similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks."
+                        "text": "Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks."
                     }
                 },
                 {