Apply suggestions from code review

Co-authored-by: Carol Willing <carolcode@willingconsulting.com>

Author: henryiii

peps/pep-0808.rst

@@ -318,8 +318,7 @@ How to Teach This
 =================
 
 If you currently have dynamic metadata, but some list or table entries are
-known statically, you can now make that explicit by adding them to the
-corresponding static entry in the project table, while keeping the entry in the
+known statically, you can now make that explicit by adding the static entry in the ``[project]`` table, while also keeping the entry in the
 ``project.dynamic`` list to allow the dynamic portion to be added by your build
 backend.
 
@@ -335,7 +334,7 @@ field.
 
 It should also be noted that specifying something in ``dynamic`` will require
 any tool that requires the full metadata to invoke the backend even if it is
-partially statically specified, so it should not be used unless necessary, just
+partially statically specified. So, it should not be used unless necessary, just
 like any other dynamic metadata.