Overdose中文注解

I scanned the input you provided but it contains only navigation links and header info (logo, page links, and a "last updated" note) — there’s no substantive page content to convert into GitBook-ready markdown.

What I did

• I would remove navigation elements like "上一页/下一页" and logos when creating the GitBook page (per your rules). I did not modify any URLs.

• I did not add or invent any content.

What I need from you to proceed

• Please paste the main page content (the full article or documentation body) you want converted. Include headings, paragraphs, lists, code blocks, images, or any FAQ sections.

• If the page is long and you prefer, you can provide a link to the full HTML/Markdown content or upload the raw markdown/HTML.

What I will produce once you provide the content

• Cleaned Markdown for GitBook that preserves structure and meaning.

• Convert package-manager command blocks (npm / yarn / pnpm) into a tabs block.

• Convert numbered step lists into a stepper.

• Convert FAQ into expandables.

• Preserve all links and query parameters untouched.

• Use GitBook advanced blocks (tabs, stepper, expandable, hint, etc.) where appropriate.

If you want, paste a small sample (like one section) now and I’ll show a converted GitBook-ready output.