diff --git a/PIP_COMPATIBILITY.md b/PIP_COMPATIBILITY.md
index 77bde9115..594c60096 100644
--- a/PIP_COMPATIBILITY.md
+++ b/PIP_COMPATIBILITY.md
@@ -30,7 +30,7 @@ drawbacks:
    target tool the user is expecting to use.
 4. It prevents uv from introducing any settings or configuration that don't exist in the target
    tool, since otherwise `pip.conf` (or similar) would no longer be usable with `pip`.
-5. It can lead user confusion, since uv would be reading settings that don't actually affect its
+5. It can lead to user confusion, since uv would be reading settings that don't actually affect its
    behavior, and many users may _not_ expect uv to read configuration files intended for other
    tools.
 
@@ -107,7 +107,7 @@ the available versions of a given package. However, uv and `pip` differ in how t
 packages that exist on multiple indexes.
 
 For example, imagine that a company publishes an internal version of `requests` on a private index
-(`--extra-index-url`), but also allow installing packages from PyPI by default. In this case, the
+(`--extra-index-url`), but also allows installing packages from PyPI by default. In this case, the
 private `requests` would conflict with the public [`requests`](https://pypi.org/project/requests/)
 on PyPI.
 
@@ -117,7 +117,7 @@ finds a match. This means that if a package exists on multiple indexes, uv will
 candidate versions to those present in the first index that contains the package.
 
 `pip`, meanwhile, will combine the candidate versions from all indexes, and select the best
-version from the combined set., though it makes [no guarantees around the order](https://github.com/pypa/pip/issues/5045#issuecomment-369521345)
+version from the combined set, though it makes [no guarantees around the order](https://github.com/pypa/pip/issues/5045#issuecomment-369521345)
 in which it searches indexes, and expects that packages are unique up to name and version, even
 across indexes.