Adjust wording for consistency (#79758)
Requested by some of our internal review. @svekars thoughts? Thanks.
Pull Request resolved: https://github.com/pytorch/pytorch/pull/79758
Approved by: https://github.com/svekars, https://github.com/kit1980
diff --git a/docs/source/community/design.rst b/docs/source/community/design.rst
index 4225059..0ce6f49 100644
--- a/docs/source/community/design.rst
+++ b/docs/source/community/design.rst
@@ -6,7 +6,7 @@
time in PyTorch. These are not meant to be hard-and-fast rules, but to
serve as a guide to help trade off different concerns and to resolve
disagreements that may come up while developing PyTorch. For more
-information on contributing, module ownership, and how to escalate a
+information on contributing, module maintainership, and how to escalate a
disagreement to the Core Maintainers, please see `PyTorch
Governance <https://pytorch.org/docs/master/community/governance.html>`__.
@@ -135,7 +135,7 @@
users: it is flexible, familiar, and perhaps most importantly, has a
huge ecosystem of scientific computing libraries and extensions
available for use. This fact motivates a few of our most recent
-investments, which attempt to hit a Pareto optimal point close to the
+contributions, which attempt to hit a Pareto optimal point close to the
Python usability end of the curve:
- `TorchDynamo <https://dev-discuss.pytorch.org/t/torchdynamo-an-experiment-in-dynamic-python-bytecode-transformation/361>`__,
