PEP 751: Fix typos (#4344)

Author: maxrake

peps/pep-0751.rst

@@ -145,7 +145,7 @@ search for:
 
 E.g. a cloud host service named "spam" would first look for
 ``pylock.spam.toml`` to install from, and if that file didn't exist then install
-from ``pylock.toml`` and look for a dependency group named "spam" fo use if
+from ``pylock.toml`` and look for a dependency group named "spam" to use if
 present.
 
 The lock file(s) SHOULD be located in the directory as appropriate for the scope
@@ -180,7 +180,7 @@ consistent order. Usage of inline tables SHOULD also be kept consistent.
   updates to the standard change it -- as ``"1.0"``.
 - If a tool supports the major version but not the minor version, a tool
   SHOULD warn when an unknown key is seen.
-- If an tool doesn't support a major version, it MUST raise an error.
+- If a tool doesn't support a major version, it MUST raise an error.
 
 
 ``environments``
@@ -1026,7 +1026,7 @@ This PEP does NOT fully replace requirements files because:
 
 - They support specifying installation
   `options <https://pip.pypa.io/en/stable/reference/requirements-file-format/#supported-options>`__
-  at install-time (e.g. ``--index-url``, ``--constrants``).
+  at install-time (e.g. ``--index-url``, ``--constraint``).
 - They can
   `reference other requirements files <https://pip.pypa.io/en/stable/reference/requirements-file-format/#referring-to-other-requirements-files>`__
   via ``-r``.
@@ -1314,8 +1314,8 @@ the key was technically superfluous.
 The single drawback of not having this key is for wheels and sdists that now
 fall under ``packages.archive``. With the separate key (or having it specified
 as a part of ``packages.sdist`` or ``packages.wheels``), it would allow for
-identifying in the lock file itself that an archive file is an sdist of wheel.
-As it currently stand, an installer must infer that detail itself.
+identifying in the lock file itself that an archive file is an sdist or wheel.
+As it currently stands, an installer must infer that detail itself.
 
 
 --------------
@@ -1369,7 +1369,7 @@ encodes the project name and version, so no new info is conveyed about the file
 (when the package version is provided). And if the location is recorded then
 getting the file is handled regardless of the file name.
 
-But recording the file name can helpful when looking for an appropriate file
+But recording the file name can be helpful when looking for an appropriate file
 when the recorded file location is no longer available (while sdist file names
 are now standardized thanks to :pep:`625`, that has only been true since 2020
 and thus there are many older sdists with names that may not be guessable).