PEP 518: Reword paragraphs describing defined tables (#682)

pep-0518.txt

@@ -151,12 +151,12 @@ PEPs.
 build-system table
 ------------------
 
-There will be a ``[build-system]`` table in the
-configuration file to store build-related data. Initially only one key
-of the table will be valid and mandatory: ``requires``. That key will
-have a value of a list of strings representing the PEP 508
-dependencies required to execute the build system (currently that
-means what dependencies are required to execute a ``setup.py`` file).
+The ``[build-system]`` table is used to store build-related data.
+Initially only one key of the table will be valid and mandatory:
+``requires``. This key must have a value of a list of strings
+representing PEP 508 dependencies required to execute the build
+system (currently that means what dependencies are required to
+execute a ``setup.py`` file).
 
 For the vast majority of Python projects that rely upon setuptools,
 the ``pyproject.toml`` file will be::
@@ -173,10 +173,10 @@ configuration file above as their default semantics when a
 tool table
 ----------
 
-Tools can have users specify configuration data as long as they use
-a sub-table within ``[tool]``, e.g. the
-`flit <https://pypi.python.org/pypi/flit>`_ tool would store its
-configuration in ``[tool.flit]``.
+The ``[tool]`` table is where tools can have users specify
+configuration data as long as they use a sub-table within ``[tool]``,
+e.g. the `flit <https://pypi.python.org/pypi/flit>`_ tool would store
+its configuration in ``[tool.flit]``.
 
 We need some mechanism to allocate names within the ``tool.*``
 namespace, to make sure that different projects don't attempt to use