Skip to content

docs: clarify Chain-of-Thought vs ReAct in Unit 1 thoughts section #563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nrnavaneet
Copy link

This PR addresses issue #525, which noted that the “Thought” section in Unit 1 previously conflated Chain-of-Thought (CoT) with ReAct.

What’s Fixed:
• Clearly defined Chain-of-Thought (CoT) as a separate prompting strategy.
• Clarified ReAct as an extension of CoT that includes external actions and observations.
• Moved the image and explanation of ReAct to the appropriate context.
• Added a comparison table showing CoT vs ReAct in terms of behavior and use cases.
• Updated explanatory on how modern LLMs like DeepSeek R1 and OpenAI’s o1 handle structured internal reasoning.

Outcome:

The revised section now:
• Accurately reflects the original academic papers (Kojima et al. for CoT, Yao et al. for ReAct),
• Eliminates confusion between the two methods, and
• Supports students with a more pedagogically sound and technically correct explanation.

…arly define Chain-of-Thought (CoT), distinguish it from ReAct, and correct prior conflation. Added comparison table and revised example placement for accuracy.
@HuggingFaceDocBuilderDev
Copy link
Collaborator

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Copy link
Member

@sergiopaniego sergiopaniego left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!
I appreciate the concerns you've raised and agree that adding more context is valuable. However, I noticed that the new addition appears at the bottom of the previous content, resulting in a lot of duplicated text.

Could we clean that up to avoid repetition?

Copy link
Author

@nrnavaneet nrnavaneet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the review.

Copy link
Member

@sergiopaniego sergiopaniego left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the improvement!

One final touch. In the last , it renders as follows:

Screenshot 2025-07-07 at 11 27 11

To actually show it correctly, you can do one of the following:

  • Add new lines after <Tip> and before </Tip>
  • Use HTML.

Copy link
Author

@nrnavaneet nrnavaneet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes

@nrnavaneet
Copy link
Author

Hi @sergiopaniego,
Thanks again for the feedback!

I’ve applied the newline formatting to both blocks to ensure proper MDX rendering, as you suggested. The updated version should now display correctly in the docs.

Let me know if there’s anything else you’d like me to adjust.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants