Update _augment.py

[david20571015]

Fix the typos in the docstrings of torchvision.transforms.v2.MixUp and torchvision.transforms.v2.CutMix.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ 7 Unrelated Failures

As of commit 054432d with merge base 054432d ():

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• unittests-windows (3.10, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.11, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.8, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.8, windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh)
• unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh)
• windows (windows.4xlarge, cpu) / windows-job (gh)
• windows (windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh)

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

[facebook-github-bot]

Hi @david20571015!

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!

[NicolasHug]

Thanks @david20571015

[david20571015]

@NicolasHug
I apologize for the confusion. By accident, I deleted the commit using the "sync fork" option in my forked repository on Github. This happens to be my first attempt at contributing to an open-source repository. Could you inform me if there exists a method to restore the deleted commit?

[NicolasHug]

No worries @david20571015 ,

I think you should be able to simply re-do the changes on your branch and if you push, this PR will probably be updated automatically.

If that doesn't work then feel free to simply start over and open a new PR.

[david20571015]

Thank you, @NicolasHug, for your prompt reply. However, it appears that the issue persists even after attempting to redo it. As a result, I have opened a new PR (#7877) that is identical to this one.