Clarify prebuilt wheels

Author: pfmoore

source/specifications/core-metadata.rst

@@ -133,15 +133,15 @@ only, and indicates that the field value was calculated at wheel build time,
 and may not be the same as the value in the sdist or in other wheels for the
 project.
 
-Note in particular that if you have a wheel, you cannot assume that a field
-which is not marked as ``Dynamic`` will have the same value in other wheels, as
-some wheels are not built directly from the sdist, but are modified from
-existing wheels (the ``auditwheel`` tool does this, for example, and it's
-commonly used when building wheels for PyPI). Such modifications *could*
-include changing metadata (even non-dynamic metadata).  Similarly, if you have
-a sdist and a wheel which you didn't build from that sdist, you cannot assume
-that the wheel's metadata matches that of the sdist, even if the field is not
-marked as ``Dynamic``.
+Note in particular that if you have obtained a prebuilt wheel, you cannot
+assume that a field which is not marked as ``Dynamic`` will have the same value
+in other wheels, as some wheels are not built directly from the sdist, but are
+modified from existing wheels (the ``auditwheel`` tool does this, for example,
+and it's commonly used when building wheels for PyPI). Such modifications
+*could* include changing metadata (even non-dynamic metadata).  Similarly, if
+you have a sdist and a wheel which you didn't build from that sdist, you cannot
+assume that the wheel's metadata matches that of the sdist, even if the field
+is not marked as ``Dynamic``.
 
 It is advisable, but not required, that tools which modify wheel metadata add
 the modified fields to the generated wheel's ``Dynamic`` field.