[Jah-yee]

Description

Corrects the page title from Pyhon API to Python API in docs/04-api-reference/01-python-api/index.md (line 3).

Fixes

Fixes issue #290.

Type of change

• Documentation fix (typo correction)

Testing

This is a single-word typo fix in a documentation file. No functional code change.

[greptile-apps]

Greptile Summary

Corrects the Python API documentation page title by changing Pyhon API to Python API.

• Fixes a single typo in the page’s front matter.
• Does not alter runtime code or documentation structure.

Confidence Score: 5/5

The PR appears safe to merge with no actionable issues identified.

The change is limited to correcting a documentation title typo and introduces no behavioral, structural, or security impact.

Important Files Changed

Filename	Overview
docs/04-api-reference/01-python-api/index.md	Correctly fixes the misspelled Python API page title without affecting other content.

_{Reviews (1): Last reviewed commit: "fix: correct 'Pyhon' to 'Python' in API ..." | Re-trigger Greptile}

[Jah-yee]

Hi @xyy9411! Gentle follow-up on this typo fix — correcting 'Pyhon' → 'Python' in the API docs title (docs/04-api-reference/01-python-api/index.md line 3). This PR addresses good first issue #290. Happy to make any adjustments if needed! 🙏

[Jah-yee]

Hi @xyy9411 — one last check on this typo fix, since issue #290 is still open upstream.

This PR is a single-line change and nothing else:

• File: docs/04-api-reference/01-python-api/index.md, line 3
• Change: title: Pyhon API → title: Python API
• Fixes: issue #290 ("Typo" — https://tvm.hyper.ai/docs/api-reference/python-api/ renders "Pyhon API")
• Commits: 1, files changed: 1

I re-checked the upstream file just now on main — the title there still reads Pyhon API, so the typo is still live on the published docs page. The diff is a one-token change to a YAML frontmatter title; there is no behavior, API, or build impact, and docs/04-api-reference/01-python-api/index.md is not generated by any script I could find in the repo, so no regeneration step is needed.

If you would prefer this to land a different way — for example squashing it into a docs-wide typo sweep, or retitling the PR to reference the docs site rather than the source file — say so and I will rebase or rework accordingly. Otherwise it is ready to merge as-is.

Happy to close it if the issue is being handled elsewhere, so it does not sit open in your queue. 🐎