docs: cleanup

[krrish-berri-2]

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Apr 2, 2026 9:49pm

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[greptile-apps]

Greptile Summary

This is a small documentation-only cleanup PR. It updates the April Townhall blog post with a more descriptive title and a new "How to contribute" section, and renames the navigation bar item from "Release Notes" to "Changelog" while reordering it before the "Blog" link.

• Blog post title changed to "April Townhall: Security + Product Roadmap" to better describe the event's content.
• Blog post description expanded to mention security and product roadmap topics.
• New "How to contribute" section added, pointing readers to GitHub issue Focus: Stabilize core features and fix accumulated bugs/UX issues #24825 to shape the agenda.
• Navbar: "Release Notes" label renamed to "Changelog" and moved before "Blog" in the left navigation.

Confidence Score: 5/5

• Safe to merge — purely documentation changes with no logic, security, or test implications.
• Both changed files are documentation only (a Markdown blog post and a Docusaurus nav config). No code paths, tests, or APIs are affected. No custom rules are violated.
• No files require special attention.

Important Files Changed

Filename	Overview
docs/my-website/blog/april_townhall_announcement/index.md	Blog post updated: title made more descriptive, description expanded, and a new "How to contribute" section added with a link to GitHub issue #24825.
docs/my-website/docusaurus.config.js	Navbar entry renamed from "Release Notes" to "Changelog" and repositioned to appear before "Blog" in the left nav bar.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Docusaurus Navbar - Left Side] --> B[Enterprise]
    B --> C["Changelog (was: Release Notes)"]
    C --> D[Blog]
    D --> E[GitHub icon - right]

    style C fill:#d4edda,stroke:#28a745,color:#000

Loading

_{Reviews (1): Last reviewed commit: "docs: cleanup" | Re-trigger Greptile}

[codspeed]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing litellm_townhall_update (0eddc45) with main (cae8613)}