docs: polish FAQ wording

[chenjiahan]

Summary

• polish wording in the FAQ docs for clearer English explanations

Testing

• not run (docs only)

---

Codex Task

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	b95de4d
🔍 Latest deploy log	https://app.netlify.com/projects/rsbuild/deploys/69240ac18c09410008251fc1
😎 Deploy Preview	https://deploy-preview-6641--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 46 (🔴 down 21 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR polishes the wording in FAQ documentation files to provide clearer, more concise English explanations while maintaining technical accuracy.

• Improved sentence structure and clarity across multiple FAQ entries
• Made language more concise and direct throughout
• Enhanced consistency in documentation tone and style

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
website/docs/en/guide/faq/features.mdx	Improved wording for questions about imports, ESLint, CDN configuration, console removal, Rspack config inspection, and warning suppression
website/docs/en/guide/faq/exceptions.mdx	Enhanced clarity for error-related FAQs including ESNext compilation, PostCSS plugin errors, loader errors, and import/export errors

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.