Updating pytorch version in docs to match scripts

[jimburtoft]

AWS email alias: {jburtoft}@amazon.com

Description: Updating the pytorch version to match what is being used in the script. The examples reference https://raw.githubusercontent.com/aws-neuron/neuronx-distributed/main/examples/training/llama/requirements_ptl.txt which is updated to 2.4.0

Date this must be published by: {If empty, we will assume the release date for the branch you're merging into.}

Link to ReadTheDocs staging for this branch's doc changes: https://awsdocs-neuron-staging.readthedocs-hosted.com/en/{YOUR_BRANCH_NAME_HERE}/

Set the docs-review-needed label on the PR for tracking.

Before you request approvals

Run a spelling and grammar check over your prose and make the changes it suggests. VSCode has a number of extensions (cSpell, LTeX) that you can use. You can also provide the rendered HTML for (or a cut-and-paste of) your pages to an AI and have it correct your spelling, grammar, and formatting issues. If you need an advanced prompt, contact @erickson-doug.

Approvers

We require 3-4 approvers to merge for non-trivial content changes (where a "trivial" change is a typo/grammar fix or a minor update to the format syntax):

1. A senior+ engineer who will review your documentation for technical accuracy and clarity in communicating the technical concepts in your work
2. A product manager for your Neuron component area who will review it for customer relevance and product/component/feature messaging
3. The lead tech writer (@erickson-doug) who will review your work for overall doc design and quality, and perform the merge when all approvals are met
4. (For PRs with code/notebook submissions) A QA/test engineer who can run your code and confirm the results.

Make sure you get a commitment from these reviewers in advance! It's hard to get good quality doc reviews in order in the 11th hour of a release.

Note: For trivial changes, you only need @erickson-doug's approval. He will merge your content once he's confirmed the fixes on staging.

Doc review checklist

Engineering reviewer checklist

• [ x] I've confirmed that the contributions in this PR meet the current AWS Neuron writing guidelines.
• [ x] I've confirmed that the documentation submitted is technically correct to the best of my knowledge.
• [x ] I've confirmed that the documentation submitted has no spelling or grammar errors or use of internal jargon/terminology.
• I've verified the changes render correctly on RTD (link above).
• (If code is included) I've run tests to verify the contents of the change.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.