docs: add missing async_grpo.enabled flag to configuration

[youngeunkwon0405]

What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

Issues

List issues that this PR closes (syntax):

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you run the unit tests and functional tests locally? Visit our Testing Guide for how to run tests
• Did you add or update any necessary documentation? Visit our Document Development Guide for how to write, build and test the docs.

Additional Information

• ...

Summary by CodeRabbit

• Documentation
  • Updated the Async GRPO guide to include clear instructions for enabling the feature via configuration.
  • Added examples demonstrating how to turn on Async GRPO in both relevant configuration sections.
  • Clarified enablement behavior and expectations without changing functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds an enabled flag for Async GRPO in two YAML configuration sections within the Async GRPO guide: policy.async_grpo.enabled: true and grpo.async_grpo.enabled: true. No other modifications.

Changes

Cohort / File(s)	Summary
Docs: Async GRPO config flags docs/guides/async-grpo.md	Documents two YAML options to enable Async GRPO: adds policy.async_grpo.enabled: true and grpo.async_grpo.enabled: true; no other content changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• terrykong

Pre-merge checks and finishing touches

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Results For Major Changes	✅ Passed	The PR only updates documentation by adding two configuration flags in the async GRPO guide and does not change any code logic, introduce new features, or modify performance-critical behavior, so it is a minor change that does not require test results in the description.
Title Check	✅ Passed	The title clearly summarizes the change to documentation by adding the missing async_grpo.enabled configuration flag. It reflects the docs context and precisely matches the content of the update without unnecessary detail or ambiguity. It is concise, specific, and provides clear insight into the primary change.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[youngeunkwon0405]

Hi @parthchadha, I guess the enabled knob is missing from the doc.

[terrykong]

@CodeRabbit title

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@terrykong, the current PR title "fix: fix async grpo doc" could be more descriptive. Here are some suggestions for a clearer title:

Recommended:

• docs: add missing async_grpo.enabled flag to configuration
• docs: add enabled flag to async GRPO configuration examples

Alternative:

• fix(docs): add missing async_grpo.enabled configuration flag

These titles:

1. Use docs: prefix since this is a documentation change (more accurate than fix:)
2. Clearly indicate what was added/fixed
3. Mention the specific configuration flag that was missing
4. Follow conventional commit format

Would you like me to update the PR title to one of these suggestions?