docs: update FAQ

README.md

@@ -20,13 +20,13 @@
 
 - [Table of contents](#table-of-contents)
 - [Introduction](#introduction)
-  - [Key Features](#key-features)
-  - [Development Experience Preview](#development-experience-preview)
-  - [Architecture](#architecture)
+    - [Key Features](#key-features)
+    - [Development Experience Preview](#development-experience-preview)
+    - [Architecture](#architecture)
 - [Quick Start](#quick-start)
 - [Documentation](#documentation)
-  - [Tutorials](#tutorials)
-  - [References](#references)
+    - [Tutorials](#tutorials)
+    - [References](#references)
 - [Roadmap](#roadmap)
 - [Contribution](#contribution)
 - [FAQ](#faq)
@@ -178,11 +178,13 @@ No, you can think of it as a traditional GUI development library that incorporat
 
 It's recommended to prioritize other GUI libraries/frameworks, as LCUI currently lacks:
 
-- **A rich set of built-in components:** You will need to build almost all the components in your UI from scratch, leading to higher development costs.
-- **Efficient graphics rendering performance:** Interfaces with extensive and complex content may experience lag.
-- **An animation system:** The lack of visual feedback affects the user interaction experience.
+- **Rich Built-in Components:** You will need to build almost all the components in your UI from scratch, leading to higher development costs.
+- **Efficient Graphics Rendering Performance:** Interfaces with extensive and complex content may experience lag.
+- **Animation System:** The lack of visual feedback affects the user interaction experience.
+- **Detailed and User-friendly Documentation**: The existing documentation and examples are only for a simple understanding. If you want to study in depth, you need to read the source code, so the learning cost is relatively high.
+- **Active Updates**: Limited by the maintainer's personal interests and time, the update frequency of this project is very low. Therefore, the functional requirements or bugs you submit may not necessarily be resolved, especially those in the old versions.
 
-Given its current state, LCUI is best suited for fulfilling the author's personal needs or developing simple tools with minimal UI content and interactions.
+Given its current state, LCUI is best suited for fulfilling the maintainer's personal needs or developing simple tools with minimal UI content and interactions.
 
 **Support development with TypeScript? If I know how to use it, why wouldn’t I just go with Electron?**
 

README.zh-cn.md

@@ -170,10 +170,12 @@ LCUI 及相关项目的部分功能设计参考了其它开源项目，你可以
 建议优先考虑其它 GUI 库/框架，因为 LCUI 目前缺少：
 
 - **丰富的预置组件：** 你需要从零开始实现界面中几乎所有的组件，开发成本较高。
-- **高效的图形渲染性能：** 界面内容较多且较大时，可能会出现卡顿。
+- **高效的图形渲染性能：** 没有 GPU 加速，界面内容较多且较大时，可能会出现卡顿。
 - **动画系统：** 界面没有动效反馈，影响交互体验。
+- **详尽且友好的文档：** 现有的文档和示例仅供简单了解，想要深入学习则需要阅读源码，因此学习成本较高。
+- **积极的更新：** 受限于维护者的个人兴趣和时间，此项目的更新频率非常低。因此你提交的功能需求或 BUG 并不一定会被解决，尤其是旧版本中的。
 
-以 LCUI 现有的条件，除了满足作者的个人需求外，也就只适用于开发一些界面内容和交互都很简单的小工具。
+以 LCUI 现有的条件，除了满足维护者的个人需求外，也就只适用于开发一些界面内容和交互都很简单的小工具。
 
 **都用上 TypeScript 语言了，那我为什么不直接用 Electron？**