fixed typo in documentation

[shazqadeer]

Summary: Fixed typo in documentation. Trying to get familiar with the PR workflow for contributing to PyTorch.

Test Plan: None

Reviewers:

Subscribers:

Tasks:

Tags:

Fixes #ISSUE_NUMBER

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 727ed03 with merge base d7fe3c4 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / linux-focal-py3.8-clang10 / test (dynamo, 1, 3, linux.2xlarge) (gh) (detected as infra flaky with no log or failing log classifier)

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: shazqadeer / name: Shaz Qadeer (bca2c81, 727ed03)

[ezyang]

You accidentally updated submodule. https://fb.workplace.com/groups/1144215345733672/posts/2585581408263718 will help

[shazqadeer]

You accidentally updated submodule. https://fb.workplace.com/groups/1144215345733672/posts/2585581408263718 will help

Thanks. I reverted the change.

[ezyang]

Check https://github.com/pytorch/pytorch/wiki/Bot-commands#merge for how to merge it yourself

[shazqadeer]

@pytorchbot merge

[pytorchmergebot]

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Details for Dev Infra team

Raised by workflow job

[shazqadeer]

@pytorchbot label "release notes: documentation for constrain_as_size fixed"

[pytorch-bot]

Didn't find following labels among repository labels: release notes: documentation for constrain_as_size fixed

[shazqadeer]

@pytorchbot label "topic: not user facing"

[shazqadeer]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here