docs/!sample/ui/internationalization.mdx (1)

132-141: Same Promise issue in Docs/Home layouts

Apply the same correction here to keep typings consistent.

-}: {
-  params: Promise<{ lang: string }>;
+}: {
+  params: { lang: string };
 ...
-  const { lang } = await params;
+  const { lang } = params;

docs/!sample/mdx/last-modified.mdx (1)

8-10: Tighten wording & add missing article

Minor style / grammar tweak to avoid the comma-splice and insert “the”.

-This feature is not enabled by default, you can enable this from the config file. Note that it only supports Git as version control.
+This feature is not enabled by default; you can enable it from the config file. Note that it only supports Git as the version-control system.

docs/!sample/ui/components/accordion.mdx (2)

30-31: Add missing “the” before “hash parameter”

-...with the specified `id` in hash parameter.
+...with the specified `id` in the hash parameter.

---

42-42: Clarify default value wording

-> The value of accordion is same as title by default. When an id presents, it will be used as the value instead.
+> The accordion’s value is the same as the title by default. When an `id` is present, that `id` is used as the value instead.

docs/!sample/headless/props.ts (2)

1-6: Consolidated import can be replaced by direct re-exports

Since these are purely type imports, you can remove the local alias indirection completely and rely on TypeScript’s export type { … } from "…".
This keeps the barrel in sync with upstream names automatically and avoids an ever-growing maintenance list.

-import type * as Breadcrumb from 'fumadocs-core/breadcrumb';
-…
-export type BreadcrumbItem = Breadcrumb.BreadcrumbItem;
+export type { BreadcrumbItem } from 'fumadocs-core/breadcrumb';

Same applies to the remaining modules.
Purely optional, but it keeps the file shorter and future-proof.

---

14-17: Verify generic default for SidebarContentProps / SidebarTriggerProps

Both generics accept an ElementType parameter that defaults to ElementType already in the upstream lib.
Passing the explicit ElementType here is harmless, but redundant. Confirm that the upstream declaration still uses that default; if so you can drop the parameter:

-export type SidebarContentProps = Sidebar.SidebarContentProps<ElementType>;
-export type SidebarTriggerProps = Sidebar.SidebarTriggerProps<ElementType>;
+export type SidebarContentProps = Sidebar.SidebarContentProps;
+export type SidebarTriggerProps = Sidebar.SidebarTriggerProps;

Tiny simplification, noop at runtime.

docs/!sample/headless/mdx/meta.json (1)

1-3: Nit: Ensure trailing newline to satisfy POSIX tools

A final newline is missing; some linters and diff tools flag this.

docs/!sample/headless/search/index.mdx (1)

1-6: Front-matter consistency

Elsewhere you use sentence-case descriptions (“Configure navigation in your Fumadocs app.”).
Consider lower-casing “Search” in the description for stylistic consistency:

-description: Configure Search in Fumadocs
+description: Configure search in Fumadocs

Pure content nit.

docs/!sample/ui/navigation/index.mdx (1)

2-4: Minor punctuation

The description already ends with a period; the title line doesn’t need one.
Consider removing the trailing period for symmetry with other pages.

-title: Navigation
-description: Configure navigation in your Fumadocs app.
+title: Navigation
+description: Configure navigation in your Fumadocs app

docs/!sample/ui/components/index.mdx (1)

3-4: Grammar tweak

“Additional components to improve documentation” reads more naturally:

-description: Additional components to improve your docs
+description: Additional components to improve your documentation

Very minor wording improvement.

docs/!sample/headless/utils/index.mdx (1)

6-6: Add a brief introduction so the page isn’t rendered completely empty

Right now the body is empty, so users who land here will just see a blank page below the heading. Consider adding a one-sentence overview or a bullet list linking to the individual utility docs.

 ---
 description: Utilities to provide extra functionality to your docs
 ---
+
+Utilities extend Fumadocs with helper functions such as navigation helpers, TOC generators, and GitHub metadata fetchers. Browse the list below to learn more.

docs/!sample/headless/components/index.mdx (1)

6-6: Populate the index page with at least a short summary

Similar to the utilities index, this page has no body content. A tiny blurb helps readers understand what they’ll find here and improves SEO.

 ---
 description: Blocks for your docs
 ---
+
+This section documents the headless UI building blocks—Breadcrumb, Link, Sidebar, ToC and more—that you can compose to craft a custom docs experience.

docs/!sample/headless/mdx/index.mdx (1)

6-6: Avoid empty body; add context or quick links

An empty MDX page can be confusing. Even a sentence explaining why MDX plugins matter (and maybe links to popular plugins) would be beneficial.

 ---
 description: Useful remark & rehype plugins for your docs.
 ---
+
+Below you’ll find guides for the core remark / rehype plugins we ship, plus tips on rolling your own.

docs/!sample/ui/search/meta.json (1)

1-3: Placeholder "..." and missing "title" may break navigation

fumadocs’ meta parser typically expects real page slugs and, for consistency, a title field like in other meta files. Verify that "..." is intentionally supported and add a title for uniformity.

 {
+  "title": "Search",
-  "pages": ["orama", "..."]
+  "pages": ["orama"]
 }

docs/!sample/headless/components/meta.json (1)

1-4: Replace placeholder "..." before merging to main docs

Leaving an ellipsis entry will surface a broken link in the sidebar. Either add the actual component docs slug or drop the placeholder until the page exists.

 {
   "title": "Components",
-  "pages": ["..."]
+  "pages": []
 }

docs/!sample/ui/components/inline-toc.mdx (2)

11-16: Minor MDX sample: remove the blank line inside fenced code for cleaner copy-paste

The extra blank line after the import statement becomes part of the pasted sample and can confuse readers.

 import { InlineTOC } from 'fumadocs-ui/components/inline-toc';

-<InlineTOC items={toc} />
+<InlineTOC items={toc} />

---

21-27: Example omits toc generation—add a hint to avoid “undefined” errors

Most readers will copy this block verbatim; without a toc variable the page will crash at runtime.

 <DocsPage>
   ...
+  {/* `toc` can be generated with \`getToc(content)\` or imported from
+      the page’s front-matter */} 
   <InlineTOC items={toc} />
   ...
 </DocsPage>

docs/!sample/ui/(integrations)/openapi/meta.json (1)

1-3: Metadata is incomplete – add a title to show up in navigation

Without a title, many nav generators fall back to the folder name (integrations)/openapi, which is not user-friendly.

 {
+  "title": "OpenAPI",
   "pages": ["configurations", "..."]
 }

docs/!sample/headless/utils/meta.json (1)

2-4: Placeholder "..." can break static-site generators

Some generators treat "..." as a literal path and will search for a non-existent file.
Either list concrete page IDs or remove the key until pages are added.

-  "pages": ["..."]
+  "pages": []

docs/!sample/headless/utils/find-neighbour.mdx (1)

11-11: Fix grammar: Add missing article.

The sentence should include the article "the" for proper grammar.

-It requires a page tree and the url of page.
+It requires a page tree and the url of the page.

docs/!sample/mdx/plugin.mdx (1)

26-26: Fix grammar: Add missing article.

The sentence should include the article "the" before ".source folder" for proper grammar.

-It automatically re-generates the index file in `.source` folder, ensuring Next.js hot reload is working properly.
+It automatically re-generates the index file in the `.source` folder, ensuring Next.js hot reload is working properly.

docs/!sample/ui/components/type-table.mdx (1)

17-19: Typo – “roll button” → “scroll button”

Small wording issue that could confuse readers.

-        'The percentage of scroll position to display the roll button',
+        'The percentage of scroll position to display the scroll button',

docs/!sample/ui/mdx/codeblock.mdx (2)

27-27: Grammar – use “an MDX”

Indefinite-article nitpick.

-This is a MDX component to be used with [Rehype Code](/docs/headless/mdx/rehype-code) to display highlighted codeblocks.
+This is an MDX component to be used with [Rehype Code](/docs/headless/mdx/rehype-code) to display highlighted codeblocks.

---

75-75: Missing determiner

Add “the” for smoother reading.

-Specify a custom icon by passing an `icon` prop to `CodeBlock` component.
+Specify a custom icon by passing an `icon` prop to the `CodeBlock` component.

docs/!sample/headless/utils/git-last-edit.mdx (2)

8-8: Grammar tweak

Insert the definite article.

-Pass your repository name, and the path to file.
+Pass your repository name and the path to the file.

---

21-24: Consistent “GitHub” casing

Maintain brand-correct capitalization throughout.

-### Github Token
-Notice that you may easily reach the rate limit in development mode. Hence, you
-should pass a Github token for a higher rate limit.
+### GitHub Token
+Notice that you may easily reach the rate limit in development mode. Hence, you
+should pass a GitHub token for a higher rate limit.

docs/!sample/ui/components/banner.mdx (1)

35-50: Optional: diversify sample rainbow colours

Several identical rgba(255,100,0,0.5) entries defeat the purpose of a rainbow example. Consider using seven distinct hues for clarity.

docs/!sample/ui/layouts/home-layout.mdx (1)

35-35: Fix grammatical issues for better readability.

The line contains grammatical and punctuation issues that should be corrected.

Apply this diff to fix the grammar and punctuation:

-We recommend to customise it from [`baseOptions`](/docs/ui/navigation/links).
+We recommend customising it from [`baseOptions`](/docs/ui/navigation/links).

docs/!sample/cli/index.mdx (1)

32-32: Fix missing article for better readability.

The sentence is missing the definite article "the" before "component".

Apply this diff to improve readability:

-The CLI fetches the latest version of component from the GitHub repository of Fumadocs.
+The CLI fetches the latest version of the component from the GitHub repository of Fumadocs.

docs/!sample/ui/search/index.mdx (2)

8-8: Minor grammar improvement needed.

Consider adding the article "the" before "root provider" for better readability.

-You can customise some configurations from root provider.
+You can customise some configurations from the root provider.

---

64-64: Minor grammar improvement for community section.

Consider adding the article "the" before "community" for better readability.

-A list of integrations maintained by community.
+A list of integrations maintained by the community.

docs/!sample/ui/(integrations)/openapi/media-adapters.mdx (1)

13-13: Minor grammar improvement needed.

Consider adding the article "the" before "use client" directive for better readability.

-Put your media adapters in a separate file with `use client` directive.
+Put your media adapters in a separate file with the `use client` directive.

docs/!sample/ui/components/github-info.mdx (1)

20-20: Fix minor grammar issue.

The sentence is missing the article "the" before "links option".

-It's recommended to add it to your docs layout with `links` option:
+It's recommended to add it to your docs layout with the `links` option:

docs/!sample/ui/components/dynamic-codeblock.mdx (2)

18-18: Fix verb agreement issue.

The verb "use" should be "uses" to agree with the singular subject "it".

-It highlights the code with Shiki and use the default component to render it.
+It highlights the code with Shiki and uses the default component to render it.

---

22-23: Fix sentence fragments and missing article.

The features list has grammatical issues that should be corrected for better readability.

-- Can be pre-rendered on server
-- load languages and themes on browser lazily
+- Can be pre-rendered on the server
+- Loads languages and themes on the browser lazily

docs/!sample/ui/layouts/root-provider.mdx (2)

27-27: Fix missing article in documentation.

The sentence lacks the definite article "the" before "search".

-Customize or disable the search dialog with `search` option.
+Customize or disable the search dialog with the `search` option.

---

43-44: Fix inconsistent word usage and missing article.

There are two issues: mixing "customise" and "customize" variants, and missing "the" before "theme".

-Fumadocs supports light/dark modes with [`next-themes`](https://github.com/pacocoursey/next-themes).
-Customise or disable it with `theme` option.
+Fumadocs supports light/dark modes with [`next-themes`](https://github.com/pacocoursey/next-themes).
+Customize or disable it with the `theme` option.

docs/!sample/headless/components/sidebar.mdx (1)

6-7: Fix missing article in description.

The sentence needs "the" before "scroll bar" for proper grammar.

-A sidebar component which handles device resizing and removes scroll bar
-automatically.
+A sidebar component which handles device resizing and removes the scroll bar
+automatically.

docs/!sample/ui/(integrations)/open-graph.mdx (1)

8-8: Fix grammar: Use "a" instead of "an" before "useful".

The static analysis tool correctly identified a grammar error.

-Next.js provides an useful set of utilities, allowing a flexible experience with Fumadocs.
+Next.js provides a useful set of utilities, allowing a flexible experience with Fumadocs.

docs/!sample/headless/internationalization.mdx (1)

40-40: Fix preposition: Use "to" instead of "on" with "attention".

The static analysis tool correctly identified an incorrect preposition usage.

-This may cause undesired cache problems, and need to pay extra attention on SEO to ensure search engines can index your pages correctly.
+This may cause undesired cache problems, and need to pay extra attention to SEO to ensure search engines can index your pages correctly.

docs/!sample/ui/components/tabs.client.tsx (1)

8-21: Consider using popstate events instead of polling for URL changes.

The current implementation polls every 100ms which is inefficient. URL changes can be detected more efficiently using browser events.

export function UrlBar() {
  const [url, setUrl] = useState('');
  useEffect(() => {
-    const timer = setInterval(() => {
+    const updateUrl = () => {
      setUrl(window.location.pathname + window.location.hash);
-    }, 100);
+    };
+    
+    updateUrl(); // Set initial value
+    window.addEventListener('popstate', updateUrl);
+    window.addEventListener('hashchange', updateUrl);

    return () => {
-      clearInterval(timer);
+      window.removeEventListener('popstate', updateUrl);
+      window.removeEventListener('hashchange', updateUrl);
    };
  }, []);

  return <pre className="bg-card rounded-lg border p-2 text-sm">{url}</pre>;
}

docs/!sample/headless/mdx/remark-ts2js.mdx (1)

88-88: Fix missing line number annotation.

The line number annotation (88~) is missing, which is inconsistent with the rest of the file's formatting.

Apply this diff to fix the formatting:

-```
+88~

docs/!sample/ui/(integrations)/feedback.mdx (2)

8-8: Fix subject-verb agreement.

Apply this diff to correct the grammar:

-Feedback is crucial for knowing what your reader thinks, and help you to further improve documentation content.
+Feedback is crucial for knowing what your reader thinks, and helps you to further improve documentation content.

---

50-51: Improve grammar and clarity.

Apply this diff to fix the grammar issues:

-On above example, it reports user feedback by capturing a `on_rate_docs` event on PostHog.
+In the above example, it reports user feedback by capturing an `on_rate_docs` event on PostHog.

docs/!sample/ui/markdown/math.mdx (2)

14-14: Fix verb form error.

Apply this diff to correct the grammar:

-Add the required remark/rehype plugins, the code might be vary depending on your content source.
+Add the required remark/rehype plugins, the code might vary depending on your content source.

---

32-32: Improve grammar and article usage.

Apply this diff to fix the grammar issues:

-Add the following to root layout to make it looks great:
+Add the following to the root layout to make it look great:

docs/!sample/ui/(integrations)/openapi/index.mdx (3)

28-28: Add missing article “the”.

Minor grammar tweak for smoother reading.

-Fumadocs OpenAPI renders the pages on server-side.
+Fumadocs OpenAPI renders the pages on the server side.

---

45-45: Remove superfluous comma after “Components”.

The comma breaks the flow of the sentence.

-Add `APIPage` to your MDX Components, so that you can use it in MDX files.
+Add `APIPage` to your MDX Components so that you can use it in MDX files.

---

73-80: Await generateFiles to surface failures.

Swallowing the returned Promise hides I/O and schema-validation errors.
Top-level await is fully supported in ESM .mjs scripts.

-void generateFiles({
+await generateFiles({

docs/!sample/ui/layouts/notebook.mdx (1)

6-6: Use more descriptive alternative text for images.

Current alt text repeats the filename and isn’t helpful for screen-reader users.
Consider something like “Screenshot of the Notebook layout” instead.

-![Notebook](/docs/notebook.png)
+![Screenshot of the Notebook layout](/docs/notebook.png)

Apply the same approach to the other screenshots.

Also applies to: 39-39, 64-64

docs/!sample/headless/mdx/headings.mdx (1)

8-9: Capitalise the acronym “IDs”.

-Applies ids to headings.
+Applies IDs to headings.

docs/!sample/ui/search/algolia.mdx (2)

10-11: Consider adding a comma for improved clarity.

Adding a comma after "generally" would improve readability and flow.

-While generally we recommend building your own search with their client-side
+While generally, we recommend building your own search with their client-side

---

30-30: Consider adding the missing article.

Adding "the" before "search server" would improve grammatical correctness.

-Configure [Tag Filter](/docs/headless/search/algolia#tag-filter) on search server and add the following:
+Configure [Tag Filter](/docs/headless/search/algolia#tag-filter) on the search server and add the following:

docs/!sample/ui/search/fetch.tsx (1)

38-38: Consider using a more robust check for empty results.

The hardcoded string comparison with 'empty' could be fragile if the API contract changes.

Consider using a more explicit check:

-<SearchDialogList items={query.data !== 'empty' ? query.data : null} />
+<SearchDialogList items={query.data && query.data !== 'empty' ? query.data : null} />

Or if possible, use a constant or enum for the empty state to make the contract more explicit.

docs/!sample/ui/navigation/links.mdx (1)

188-188: Add missing article for grammatical correctness.

Adding "a" before "navigation menu" would improve readability.

-In Home Layout, you can add navigation menu (fully animated) to the navbar.
+In Home Layout, you can add a navigation menu (fully animated) to the navbar.

docs/!sample/ui/components/tabs.mdx (1)

98-98: Add missing article for better readability.

Adding "the" before "HTML" would improve grammatical flow.

-Use HTML `id` attribute to link to a specific tab.
+Use the HTML `id` attribute to link to a specific tab.

docs/!sample/ui/(integrations)/python.mdx (1)

6-8: Fix typo in Callout title and wording for clarity

Experiemntal is miss-spelled and “use it in caution” is unidiomatic.

-<Callout type="warn" title="Experiemntal">
-  Support for Python docgen is still experimental, please use it in caution.
+<Callout type="warn" title="Experimental">
+  Support for Python doc-gen is still experimental—please use it with caution.
</Callout>

docs/!sample/ui/(integrations)/openapi/proxy.mdx (1)

19-21: Minor grammar – add missing article

“Create a route handler for proxy server.”

-Create a route handler for proxy server.
+Create a route handler for **the** proxy server.

Tiny tweak but reads more naturally.

docs/!sample/ui/search/.shared.mdx (1)

30-38: Optional: wrap <Provider> once per tree

If the root layout already provides other context providers, make sure the new Provider is only mounted once. Nesting multiple instances (e.g. in nested layouts) will override the search dialog recursively and can create extra renders.

No code change required—just something to double-check in larger apps.

docs/!sample/headless/mdx/rehype-code.mdx (2)

25-26: Typo – “codeblock” → “code block”

-A codeblock wrapped in `<pre />` element.
+A code block wrapped in a `<pre>` element.

---

53-56: Clarify React rendering caveat

The comment about dangerouslySetInnerHTML might alarm newcomers. A short hint that Fumadocs UI already handles this internally—or showing a minimal example—would prevent misuse.

Consider appending:

When using the default Fumadocs UI components the icon HTML is rendered safely for you; only customise this if you replace the default code component.

docs/!sample/headless/components/breadcrumb.mdx (1)

46-66: Minor accessibility touch-up

The breadcrumb separator <ChevronRight> is decorative; add aria-hidden="true" to prevent it from being announced by screen readers.

-<ChevronRight className="size-4 shrink-0 rtl:rotate-180" />
+<ChevronRight aria-hidden="true" className="size-4 shrink-0 rtl:rotate-180" />

docs/!sample/headless/mdx/structure.mdx (2)

21-23: Use “an MDX” instead of “a MDX”.

Small article mismatch.

- write your own plugin to convert it into a MDX export.
+ You can write your own plugin to convert it into an MDX export.

---

33-34: Preposition & missing article.

- Paragraphs will be extracted to the `contents` array, each item contains a `heading` prop indicating the heading of paragraph.
+ Paragraphs will be extracted into the `contents` array; each item contains a `heading` prop indicating the heading of the paragraph.

docs/!sample/headless/components/toc.mdx (1)

6-6: Missing hyphen in “auto-scroll”.

- A Table of Contents with active anchor observer and auto scroll.
+ A Table of Contents with active anchor observer and auto-scroll.

docs/!sample/headless/mdx/remark-image.mdx (2)

29-30: Subject-verb agreement.

- ...into Next.js Image usage, and add required props like `width` and `height`.
+ ...into a Next.js Image usage, and adds required props such as `width` and `height`.

---

64-64: Missing article.

- Where `./public/hello.png` points to the image in public directory.
+ Where `./public/hello.png` points to the image in the public directory.

docs/!sample/ui/markdown/mermaid.mdx (3)

6-6: Comma splice & clarity.

Consider splitting into two sentences for readability:

- Fumadocs doesn't have a built-in Mermaid wrapper provided, we recommend using `mermaid` directly.
+ Fumadocs does not ship with a built-in Mermaid wrapper. We recommend using the `mermaid` package directly.

---

10-11: Preposition tweak.

- Install the required dependencies, `next-themes` is used with Fumadocs to manage the light/dark mode.
+ Install the required dependencies; `next-themes` is used by Fumadocs to manage light/dark mode.

---

24-26: Article “an MDX”.

- Add the component as a MDX component:
+ Add the component as an MDX component:

docs/!sample/mdx/mdx.mdx (1)

10-11: Broken anchor in link.

The collection-config link uses #mdxoptions (missing hyphen) whereas the global link uses #mdx-options. Update for consistency:

- You can customise it on [Global Config](/docs/mdx/global#mdx-options) or [Collection Config](/docs/mdx/collections#mdxoptions).
+ You can customise it on [Global Config](/docs/mdx/global#mdx-options) or [Collection Config](/docs/mdx/collections#mdx-options).

docs/!sample/ui/markdown/twoslash.mdx (2)

52-56: Clarify heading and grammar for style-import section

The phrase “Add styles, Tailwind CSS v4 is required.” is a bit abrupt and misses a determiner, which may confuse readers skimming the guide.

-Add styles, Tailwind CSS v4 is required.
+Add the styles – Tailwind CSS v4 is required.

---

127-133: Minor wording tweak for cache section

Insert the definite article for smoother reading.

-You can enable filesystem cache with `typesCache` option:
+You can enable a filesystem cache with the `typesCache` option:

docs/!sample/ui/navigation/sidebar.mdx (1)

58-60: Article missing before “opened tab”

-Sidebar Tabs are folders with tab-like behaviours, only the content of opened tab will be visible.
+Sidebar Tabs are folders with tab-like behaviour; only the content of the opened tab will be visible.

docs/!sample/headless/index.mdx (1)

60-64: Fix plural-noun article mismatch

-It offers simple document searching as well as components for building a good docs.
+It offers simple document searching as well as components for building good docs.

docs/!sample/mdx/collections.mdx (1)

71-74: Replace “hence” conjunction misuse

“Hence” alone can read awkwardly mid-sentence; use “therefore” or break into two clauses.

-Note that the validation is done at build time, hence the output must be serializable.
+Note that validation is done at build time; therefore, the output must be serializable.

docs/!sample/mdx/async.mdx (1)

80-80: Grammar nit ‑ plural & article usage

“better capability to handle massive amount” sounds off.
Suggested tweak for smoother reading:

- which usually have better capability to handle massive amount of content to index.
+ which usually have better capabilities to handle a massive amount of content to index.

docs/!sample/headless/search/orama-cloud.mdx (2)

28-28: Missing definite article

“from dashboard” → should be “from the dashboard”.

- using the private API key and index ID from dashboard,
+ using the private API key and index ID from the dashboard,

---

68-69: Consistent article usage

Both occurrences read more naturally with “the”:

- 1. Create a Crawler index from dashboard,
+ 1. Create a Crawler index from the dashboard,

- 2. Copy the public API key and index ID from dashboard
+ 2. Copy the public API key and index ID from the dashboard

docs/!sample/ui/comparisons.mdx (2)

12-13: Capitalisation after comma

The pronoun “It” mid-sentence shouldn’t be capitalised:

- As a result, It provides many server-side functions,
+ As a result, it provides many server-side functions,

---

66-66: Article + plural noun mismatch

“For a simple docs” → either “For simple docs” or “For a simple doc site”.

- For a simple docs, Docusaurus might be a better choice
+ For simple docs, Docusaurus might be a better choice

docs/!sample/ui/layouts/docs.mdx (4)

6-6: Run-on sentence

Consider splitting for clarity:

- The layout of documentation pages, it includes a sidebar and mobile-only navbar.
+ The Docs Layout includes a sidebar and a mobile-only navbar for documentation pages.

---

53-55: Verb form after “recommend”

Use gerund/infinitive:

- we recommend to customise it from `baseOptions`.
+ we recommend customising it via `baseOptions`.

---

120-120: Missing article

- into appropriate position.
+ into the appropriate position.

---

135-136: Preposition choice

appears in the browser viewport reads better than “into”.

- appears into the browser viewport,
+ appears in the browser viewport,

docs/!sample/mdx/performance.mdx (1)

40-41: Minor style – “files” already implies plural

You could drop the second “+”:

- handle nearly 500+ files
+ handle nearly 500 files

docs/!sample/headless/page-tree.mdx (4)

6-10: Grammar & clarity tweaks improve readability

Several minor issues make the intro harder to parse (article “the”, verb form, plural).

-Page tree is a tree structure that describes all navigation links, with other items like separator and folders.
-It will be sent to the client and being referenced in navigation elements including the sidebar and breadcrumb.
-Hence, you shouldn't store any sensitive or large data in page tree.
+The page-tree is a hierarchical structure that describes all navigation links, along with items such as separators and folders.
+It is sent to the client and referenced by navigation elements, including the sidebar and breadcrumb.
+Therefore, you shouldn't store any sensitive or large data in the page-tree.

---

13-17: Fix missing article & preposition

-By design, page tree only contains necessary information of all pages and folders.
-Unserializable data such as functions can't be passed to page tree.
+By design, the page-tree only contains the necessary information about all pages and folders.
+Unserializable data such as functions can't be passed to the page-tree.

---

50-51: Capitalise acronym

“urls” → “URLs”.

-> External urls are also supported
+> External URLs are also supported

---

90-91: Article missing before “ReactElement”

-Icon is a `ReactElement`, supported by pages and folders.
+An icon is a `ReactElement`, supported by pages and folders.

docs/!sample/ui/index.mdx (4)

54-56: Add missing verb & clarify version notice

-A minimum version of Node.js 18 required, note that Node.js 23.1 might have problems with Next.js production build.
+A minimum Node.js version of 18 **is** required. Note that Node.js 23.1 (preview) might have problems with the Next.js production build.

---

76-80: Subject/verb agreement

-- the React.js framework to use (the docs is only written for Next.js).
-- the content source to use.
+- the React.js framework to use (the docs **are** only written for Next.js).
+- the content source to use.

---

166-167: Missing article

-...remove the original MDX file from content directory (`/content/docs`).
+...remove the original MDX file from the content directory (`/content/docs`).

---

201-203: Polish welcome sentence

-New to here? Don't worry, we are welcome for your questions.
+New here? Don't worry, we welcome your questions.

docs/!sample/ui/(integrations)/openapi/configurations.mdx (3)

42-44: Clarify sentence & add article

-> Operation in OpenAPI schema refers to an API endpoint with specific method like `/api/weather:GET`.
+> An *operation* in an OpenAPI schema refers to an API endpoint with a specific method, such as `/api/weather:GET`.

---

225-226: Preposition

-Customise components in the page.
+Customise components on the page.

---

260-260: Use “a URL”

-...if given an URL.
+...if given a URL.

docs/!sample/headless/search/orama.mdx (5)

6-7: Comma splice & capitalisation

-Fumadocs supports document search with Orama, It is the default but also the recommended option since it can be self-hosted and totally free.
+Fumadocs supports document search with Orama. It is the default—and recommended—option because it can be self-hosted and is totally free.

---

42-43: Word choice

-Index with the raw content of document (unrecommended).
+Index with the raw content of the document (not recommended).

---

86-87: Comma splice

-Support filtering results by tag, it's useful for implementing multi-docs similar to this documentation.
+You can filter results by tag—useful for implementing multi-docs similar to this documentation.

---

203-205: Missing article

-To work with Next.js static export, use `staticGET` from search server.
+To work with Next.js static export, use `staticGET` from the search server.

---

245-245: Plural noun

-You can host the search server on other backend such as Express and Elysia.
+You can host the search server on other backends, such as Express or Elysia.

docs/!sample/headless/mdx/install.mdx (1)

51-55: Table description could be clearer

Consider expanding the second column header so readers know what to supply:

-| Component |                                    |
-| --------- | ---------------------------------- |
-| Tabs      | Accepts an array of item (`items`) |
-| Tab       | Accepts the name of item (`value`) |
+| Component | Required props / description                     |
+| --------- | ----------------------------------------------- |
+| Tabs      | `items`: string[] – list of tab labels          |
+| Tab       | `value`: string – label matching one `items` entry |

docs/!sample/headless/custom-source.mdx (3)

14-14: Improve phrasing for clarity

“examples to use Fumadocs” reads awkwardly. Prefer “examples of using Fumadocs” (or similar) to keep the sentence idiomatic.

-You can see examples to use Fumadocs with a CMS, which allows a nice experience on publishing content, and real-time update without re-building the app.
+You can see examples of using Fumadocs with a CMS, which provides a pleasant publishing experience and real-time updates without rebuilding the app.

---

61-63: Add missing determiners

Both occurrences lack the required article.

-In the main body of page, find the corresponding page according to the slug and render its content inside the `DocsPage` component.
-You also need table of contents, which can be generated with your own implementation, or using the [`getTableOfContents`](/docs/headless/utils/get-toc) utility (Markdown/MDX only).
+In the main body of the page, find the corresponding page by its slug and render its content inside the `DocsPage` component.
+You also need a table of contents, which can be generated with your own implementation or by using the [`getTableOfContents`](/docs/headless/utils/get-toc) utility (Markdown/MDX only).

---

84-84: Minor grammar fixes

1. “similar as” → “similar to”
2. “think it as” → “think of it as”
3. “there’s some limitations” → “there are some limitations”

-generateMetadata` (similar as the code above).
+generateMetadata` (similar to the code above).

-You can think it as a `next-mdx-remote` with built-in plugins for Fumadocs.
+You can think of it as a `next-mdx-remote` with built-in plugins for Fumadocs.

-Since it doesn't use a bundler, there's some limitations:
+Since it doesn't use a bundler, there are some limitations:

Also applies to: 98-98, 107-107

docs/!sample/headless/content-collections/index.mdx (1)

89-90: Insert missing comma after an introductory phrase

A short pause improves readability.

-To use components from other packages like Fumadocs UI, pass them to your `<MDXContent />` component.
+To use components from other packages, like Fumadocs UI, pass them to your `<MDXContent />` component.

docs/!sample/headless/search/trieve.mdx (1)

60-63: Missing preposition breaks sentence flow

Add “to” after “script” for grammatical correctness.

-Create a script, the `sync` function will sync search indexes.
+Create a script to run the `sync` function that will synchronise the search indexes.

docs/!sample/headless/source-api.mdx (1)

80-83: Minor grammar & clarity

“it fallbacks” → “it falls back”.

-When looking for a page, it fallbacks to default locale
+When looking for a page, it falls back to the default locale

docs/!sample/mdx/index.mdx (4)

9-10: Polish the intro sentences for concision & grammar

Minor wording fixes improve readability and remove a comma-splice.

-It provides the tool for Next.js to transform content into type-safe data, similar to Content Collections.
-This library is made for Next.js, you can use it to handle blog and other contents.
+It provides a tool for Next.js to transform content into type-safe data, similar to Content Collections.
+This library is designed for Next.js; you can use it to handle blogs and other content.

---

43-45: Plural-agreement typo

“type of files” → “types of files”.

-**Collection** refers to a collection containing a certain type of files.
+**Collection** refers to a collection containing certain types of files.

---

47-48: Quote-style consistency in Tabs list

Mixed single and double quotes may trip some ESLint configs.

-<Tabs items={["doc", "meta", 'docs']}>
+<Tabs items={['doc', 'meta', 'docs']}>

---

117-133: Tighten wording & add missing determiners

Run-on sentence and missing “the” before .source folder.

-A `.source` folder is generated in the root directory when you run `next dev` or `next build`. It contains all output data and types, you should add it to `.gitignore`.
+A `.source` folder is generated in the project root when you run `next dev` or `next build`. It contains all output data and types, and you should add it to the `.gitignore` file.

-The `fumadocs-mdx` command also generates types for `.source` folder.
+The `fumadocs-mdx` command also generates types for the `.source` folder.

-You can access the collection output from `.source` folder with its original name:
+You can access the collection output from the `.source` folder with its original name:

docs/!sample/ui/internationalization.mdx (1)

10-12: Minor comma insertion for readability

-Fumadocs is not a full-powered i18n library, it's up to you when implementing i18n for Next.js part.
+Fumadocs is not a full-powered i18n library, so it's up to you to implement i18n for the Next.js part.

docs/!sample/headless/page-conventions.mdx (7)

6-10: Tighten grammar in Callout copy

Minor grammatical nits that make the sentence flow better:

-    This guide only applies for content sources that uses `loader()` API, such as Fumadocs MDX.
+    This guide only applies to content sources that use the `loader()` API, such as Fumadocs MDX.

---

14-16: Missing comma → readability

Add a comma after the parenthetical phrase to prevent the clause from running on:

-While Next.js handles routing, Fumadocs generates **page slugs** and **sidebar items** (page tree) from your content directory using [`loader()`](/docs/headless/source-api).
+While Next.js handles routing, Fumadocs generates **page slugs** and **sidebar items** (page tree) from your content directory, using [`loader()`](/docs/headless/source-api).

---

25-29: “An MDX file”, not “A MDX file”

-A [MDX](https://mdxjs.com) or Markdown file, you can customise its frontmatter.
+An [MDX](https://mdxjs.com) or Markdown file—you can customise its front-matter.

---

63-66: Split run-on sentence in “Folder” section

-Organize multiple pages, you can create a [Meta file](#meta) to customise folders.
+Organize multiple pages into folders.  
+You can create a [Meta file](#meta) (`meta.json`) to customise a folder.

---

68-70: Add missing determiner

-By default, putting a file into folder will change its slugs.
+By default, putting a file into a folder will change its slugs.

---

145-152: Article before “icon”

-Use the syntax `[Text](url)` to insert links, or `[Icon][Text](url)` to add icon.
+Use the syntax `[Text](url)` to insert links, or `[Icon][Text](url)` to add an icon.

---

156-161: “At runtime”, not “in runtime”

-Since Fumadocs doesn't include an icon library, you have to convert the icon names to JSX elements in runtime, and render it as a component.
+Since Fumadocs doesn't include an icon library, you have to convert icon names to JSX elements at runtime and render them as components.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Learnt from: juliusmarminge
PR: trpc/trpc#6262
File: examples/minimal-react/client/package.json:16-17
Timestamp: 2025-02-12T16:56:46.960Z
Learning: In examples and codemods targeting future versions, dependencies may intentionally use upcoming versions (e.g., React v19) or `next` tags, even if those versions haven't been officially released yet.

Learnt from: juliusmarminge
PR: trpc/trpc#6262
File: examples/minimal-react/client/package.json:16-17
Timestamp: 2025-02-12T16:56:46.960Z
Learning: In examples and codemods targeting future versions, dependencies may intentionally use upcoming versions (e.g., React v19) or `next` tags, even if those versions haven't been officially released yet.

Learnt from: juliusmarminge
PR: trpc/trpc#6262
File: examples/minimal-react/client/package.json:16-17
Timestamp: 2025-02-12T16:56:46.960Z
Learning: In examples and codemods targeting future versions, dependencies may intentionally use upcoming versions (e.g., React v19) or `next` tags, even if those versions haven't been officially released yet.

Learnt from: juliusmarminge
PR: trpc/trpc#6262
File: examples/minimal-react/client/package.json:16-17
Timestamp: 2025-02-12T16:56:46.960Z
Learning: In examples and codemods targeting future versions, dependencies may intentionally use upcoming versions (e.g., React v19) or `next` tags, even if those versions haven't been officially released yet.

docs/content/docs/framework/videos-and-community-resources.mdx (2)

49-74: Minor copy-editing: compound adjectives need hyphens

Examples:

• “Full Stack TypeScript” → “Full-stack TypeScript”
• “Beginner Friendly” → “Beginner-friendly”

Applying the hyphen improves grammatical correctness and aligns with the LanguageTool lint hints.
Consider a quick pass over all section titles and bullet points to add these hyphens where appropriate.

Also applies to: 75-99, 100-124

---

418-431: Accessibility: icons alone aren’t descriptive

Cards such as “tRPC Analytics” rely solely on icons to convey meaning. Assistive technologies may ignore SVGs rendered via components.
Add brief descriptive text via aria-label/title on the icon component or supplement with additional visible text.

Example:

-<Card href="#" title="tRPC Analytics" icon={<IconChartLine />} >
+<Card
+  href="#"
+  title="tRPC Analytics"
+  icon={<IconChartLine aria-label="Analytics icon" />}
+>

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro