Fix Transforms tutorial: unify target_transform and ToTensor prose

[amit-chaubey]

Fixes #3822

Summary

The Transforms tutorial defined target_transform twice with slightly different scatter_ call styles, and the second definition did not change the FashionMNIST instance already built above—only the prose matched the second form. This updates the page to a single, consistent definition and fixes a small grammar issue in the ToTensor section.

Changes

• Define target_transform once using scatter_(dim=0, index=..., value=1) and float32, and pass it into FashionMNIST.
• Replace the duplicate executable target_transform = ... block with narrative text that refers to the definition above.
• Fix wording: “FloatTensor and scales” (remove stray period after FloatTensor).

Notes

Issue #3822 did not spell out a specific bug; this addresses concrete clarity/correctness problems in the published tutorial source. If maintainers expected a different fix (e.g. download output on the rendered page), happy to follow up.

Checklist

• The issue that is being fixed is referred in the description (see above "Fixes Feedback about Transforms #3822")
• Only one issue is addressed in this pull request
• Labels from the issue that this PR is fixing are added to this pull request (none on Feedback about Transforms #3822 — leaving for maintainers)
• No unnecessary issues are included into this pull request.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3824

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Rolling out OSDC (ARC) runners on pull workflow for PyTorch trunk commits

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @amit-chaubey!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[amit-chaubey]

Hi I signed the cla.

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!