Super tiny fix typo: warmup ratio reported in numina

[fzyzcjy]

Hi thanks for the blog! When looking at source code, it seems that:

• https://github.com/project-numina/aimo-progress-prize/blob/main/training/configs/stage-1-cot.yaml: stage 1 has "0." (i.e. 0.0)
• https://github.com/project-numina/aimo-progress-prize/blob/main/training/configs/stage-2-tir.yaml: stage 2 has "0.1"

But the blog mentions both as 0.1. Thus I guess it may potentially be a very little typo and make this PR.

Please correct me if I am wrong! For example, maybe my understanding of the config is incorrect.

---

Congratulations! You've made it this far! Once merged, the article will appear at https://huggingface.co/blog. Official articles
require additional reviews. Alternatively, you can write a community article following the process here.

Preparing the Article

You're not quite done yet, though. Please make sure to follow this process (as documented here):

• Add an entry to _blog.yml.
• Add a thumbnail. There are no requirements here, but there is a template if it's helpful.
• Check you use a short title and blog path.
• Upload any additional assets (such as images) to the Documentation Images repo. This is to reduce bloat in the GitHub base repo when cloning and pulling. Try to have small images to avoid a slow or expensive user experience.
• Add metadata (such as authors) to your md file. You can also specify guest or org for the authors.
• Ensure the publication date is correct.
• Preview the content. A quick way is to paste the markdown content in https://huggingface.co/new-blog. Do not click publish, this is just a way to do an early check.

Here is an example of a complete PR: #2382

Getting a Review

Please make sure to get a review from someone on your team or a co-author.
Once this is done and once all the steps above are completed, you should be able to merge.
There is no need for additional reviews if you and your co-authors are happy and meet all of the above.

Feel free to add @pcuenca as a reviewer if you want a final check. Keep in mind he'll be biased toward light reviews
(e.g., check for proper metadata) rather than content reviews unless explicitly asked.