mirror of
https://github.com/pytorch/pytorch.git
synced 2025-10-21 05:34:18 +08:00
Fix four misspellings of "its" in documentation (#125681)
Pull Request resolved: https://github.com/pytorch/pytorch/pull/125681 Approved by: https://github.com/Skylion007, https://github.com/svekars
This commit is contained in:
committed by
PyTorch MergeBot
parent
7f1d5aba93
commit
4d8fa7df40
@ -790,7 +790,7 @@ USE_PRECOMPILED_HEADERS=1 python setup.py develop
|
||||
```
|
||||
|
||||
This adds a build step where the compiler takes `<ATen/ATen.h>` and essentially
|
||||
dumps it's internal AST to a file so the compiler can avoid repeating itself for
|
||||
dumps its internal AST to a file so the compiler can avoid repeating itself for
|
||||
every `.cpp` file.
|
||||
|
||||
One caveat is that when enabled, this header gets included in every file by default.
|
||||
@ -1321,7 +1321,7 @@ There are two possible choices for which commit to use:
|
||||
1. Checkout commit `B`, the head of the PR (manually committed by the PR
|
||||
author).
|
||||
2. Checkout commit `C`, the hypothetical result of what would happen if the PR
|
||||
were merged into it's destination (usually `main`).
|
||||
were merged into its destination (usually `main`).
|
||||
|
||||
For all practical purposes, most people can think of the commit being used as
|
||||
commit `B` (choice **1**).
|
||||
|
@ -262,7 +262,7 @@ requires `pytorchbot`, so it's only available in PyTorch atm.
|
||||
|
||||
### Cherry Picking Reverts
|
||||
|
||||
If PR that has been cherry-picked into release branch has been reverted, it's cherry-pick must be reverted as well.
|
||||
If PR that has been cherry-picked into release branch has been reverted, its cherry-pick must be reverted as well.
|
||||
|
||||
Reverts for changes that was committed into the main branch prior to the branch cut, must be propagated into release branch as well.
|
||||
|
||||
|
@ -7587,7 +7587,7 @@ Supports strided and sparse 2-D tensors as inputs, autograd with
|
||||
respect to strided inputs.
|
||||
|
||||
This operation has support for arguments with :ref:`sparse layouts<sparse-docs>`.
|
||||
If :attr:`out` is provided it's layout will be used. Otherwise, the result
|
||||
If :attr:`out` is provided its layout will be used. Otherwise, the result
|
||||
layout will be deduced from that of :attr:`input`.
|
||||
|
||||
{sparse_beta_warning}
|
||||
|
Reference in New Issue
Block a user