Suggestion: Spaces before and after ---

Doc/distutils/configfile.rst

@@ -9,14 +9,14 @@ Writing the Setup Configuration File
 Often, it's not possible to write down everything needed to build a distribution
 *a priori*: you may need to get some information from the user, or from the
 user's system, in order to proceed.  As long as that information is fairly
-simple---a list of directories to search for C header files or libraries, for
-example---then providing a configuration file, :file:`setup.cfg`, for users to
+simple --- a list of directories to search for C header files or libraries, for
+example --- then providing a configuration file, :file:`setup.cfg`, for users to
 edit is a cheap and easy way to solicit it.  Configuration files also let you
 provide default values for any command option, which the installer can then
 override either on the command-line or by editing the config file.
 
 The setup configuration file is a useful middle-ground between the setup
-script---which, ideally, would be opaque to installers [#]_---and the command-line to
+script --- which, ideally, would be opaque to installers [#]_ --- and the command-line to
 the setup script, which is outside of your control and entirely up to the
 installer.  In fact, :file:`setup.cfg` (and any other Distutils configuration
 files present on the target system) are processed after the contents of the