docs: update framework intro

packages/docs/.vitepress/config.ts

@@ -13,7 +13,7 @@ export default defineConfig({
   },
   lang: 'en-US',
   title: 'BlockSuite',
-  description: 'Toolkit for Diverse Content Editing',
+  description: 'The Editor Framework',
   themeConfig: {
     // https://vitepress.dev/reference/default-theme-config
     nav: [

packages/docs/component-types.md

@@ -56,7 +56,15 @@ export class SimpleDocEditor extends LitElement {
 }
 ```
 
-As long as there is a corresponding `host` implementation, you can use the component model of frameworks like react or vue to implement your BlockSuite editors:
+In other words, you can think of the BlockSuite editor as being composed in this way:
+
+```ts
+type Editor = BlockSpec[];
+```
+
+With very little overhead.
+
+So, as long as there is a corresponding `host` implementation, you can use the component model of frameworks like react or vue to implement your BlockSuite editors:
 
 ![framework-agnostic](./images/framework-agnostic.png)
 

packages/docs/design-philosophy.md

@@ -6,7 +6,7 @@
 
 ## Motivation
 
-For years, web frameworks such as React and Vue have promoted a mental model of component based development. This approach allows us to break down complex front-end applications into components for better composition and maintenance.
+For years, web frameworks such as React and Vue have popularized the mental model of component based development. This approach allows us to break down complex front-end applications into components for better composition and maintenance.
 
 Hence, when discussing front-end collaborative editing (or rich text editing), the first thought is often to define an `<Editor/>` component, then design the corresponding data flow and APIs around this editor. This method seems intuitive and has been adopted by many open-source editors in the front-end community. Everything sounds natural, but are there limitations or room for improvement?
 

packages/docs/overview.md

@@ -2,7 +2,7 @@
 
 BlockSuite is a toolkit for building collaborative editors and applications. It embraces the [**_document-centric_**](./design-philosophy) approach to facilitate the development of more flexible, diverse, and scalable editable interfaces.
 
-We believe that for modern collaborative editing applications, the overall application data flow should be consistently modeled and reused on a larger scale, reducing the interoperability cost between editor and non-editor components. **Hence, BlockSuite completely separates the collaborative document model from the editor**. This separation allows any UI component, whether part of an editor or not, to function effectively by simply attaching it to the same document, offering a more flexible editing experience.
+We believe that for modern collaborative editing applications, the overall application data flow should be consistently modeled and reused on a larger scale, reducing the interoperability cost between editor and non-editor components. **This is why BlockSuite completely separates the collaborative document model from the editor**. This separation allows any UI component, whether part of an editor or not, to function effectively by simply attaching it to the same document, offering a more flexible editing experience.
 
 ![showcase-doc-edgeless-editors](./images/showcase-doc-edgeless-editors.jpg)