docs(readme): update convergence table, latest news, and outdated links

[sbhavani]

Description

Updates README add missing format support documentation, update news section, and fix broken/outdated links.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

• Add MXFP8 and NVFP4 format support to highlights and description
• Update FP8 convergence table with MXFP8 results from arxiv paper
• Remove outdated JAX Toolbox links and "available on request" entries
• Update Docker container versions to 26.01
• Fix DeepSpeed and Lightning integration links
• Add Nemotron 3 paper to Latest News
• Add quickstart notebook link after PyTorch example

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the repository README (README.rst) to reflect newer TE capabilities and references: adds Blackwell MXFP8/NVFP4 support messaging, refreshes the FP8 convergence table, updates the Latest News section, bumps example NGC container tags to 26.01, and revises several integration links while removing some outdated/"coming soon" entries.

Overall, the changes are localized to documentation and align with the README’s purpose as a landing page for capabilities, links, and quickstart guidance.

Confidence Score: 4/5

• This PR is safe to merge after fixing a small reStructuredText link markup issue.
• Changes are documentation-only and limited to README content/links; the only definite issue found is a malformed/anonymous reST hyperlink (__) that can render incorrectly.
• README.rst (Videos section hyperlink markup)

Important Files Changed

Filename	Overview
README.rst	Updates news, format support text, FP8 convergence table entries, container versions, and integration links; found a reST link markup issue (anonymous hyperlink __ likely unintended).

Sequence Diagram

sequenceDiagram
  participant A as PR Author
  participant R as README.rst
  participant G as GitHub Renderer
  participant U as Users

  A->>R: Update docs content/links/tables
  R->>G: Render .rst to HTML
  G-->>U: Display README on repo frontpage
  U->>R: Click integration/news links
  R-->>U: External resources open (or 404 if broken)

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

The referenced quickstart.ipynb file does not exist in docs/examples/. The actual notebooks in that directory are fp8_primer.ipynb, advanced_optimizations.ipynb, and te_jax_integration.ipynb. Consider using one of these existing notebooks or creating the quickstart notebook before merging.

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

extra whitespace in "Megatron Core" framework names - inconsistent with other rows

Suggested change

	| LLM-8B | Megatron Core | https://arxiv.org/abs/2506.08027 |
	+------------+------------------+---------------------------------------------------------------------------------------------------------+
	| MPT-13B | Mosaic Composer | https://www.databricks.com/blog/turbocharged-training-optimizing-databricks-mosaic-ai-stack-fp8 |
	+------------+------------------+---------------------------------------------------------------------------------------------------------+
	| GPT-22B | NeMo Framework | Available on request |
	| MoE-16B | Megatron Core | https://arxiv.org/abs/2506.08027 |
	| LLM-8B | Megatron Core | https://arxiv.org/abs/2506.08027 |
	+------------+------------------+---------------------------------------------------------------------------------------------------------+
	| MPT-13B | Mosaic Composer | https://www.databricks.com/blog/turbocharged-training-optimizing-databricks-mosaic-ai-stack-fp8 |
	+------------+------------------+---------------------------------------------------------------------------------------------------------+
	| MoE-16B | Megatron Core | https://arxiv.org/abs/2506.08027 |

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

extra space before "Megatron Core" - should have 2 spaces like other rows, not 3

Suggested change

	| LLM-8B | Megatron Core | https://arxiv.org/abs/2506.08027 |
	| LLM-8B | Megatron Core | https://arxiv.org/abs/2506.08027 |

[greptile-apps]

extra space before "Megatron Core" - should have 2 spaces like other rows, not 3

Suggested change

	| MoE-16B | Megatron Core | https://arxiv.org/abs/2506.08027 |
	| MoE-16B | Megatron Core | https://arxiv.org/abs/2506.08027 |

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

README.rst
Broken reST link markup

This link uses ...__(double-underscore), while the rest of the README uses..._. In reStructuredText, __ denotes an anonymous hyperlink reference and can render incorrectly here.

* `Stable and Scalable FP8 Deep Learning Training on Blackwell | GTC 2025 <https://www.nvidia.com/en-us/on-demand/session/gtc24-s62457/>`_