Stress appendices

pep-3151.txt

@@ -94,6 +94,10 @@ is raised for on other systems. Third, the user wanting access to low-level
 exception specifics has to examine the ``errno`` or ``winerror`` attribute
 anyway.
 
+.. note::
+    **Appendix B** surveys the use of the various exception types accross
+    the interpreter and the standard library.
+
 
 Lack of fine-grained exceptions
 -------------------------------
@@ -226,7 +230,7 @@ Step 2: define additional subclasses
 The second step of the resolution is to extend the hierarchy by defining
 subclasses which will be raised, rather than their parent, for specific
 errno values.  Which errno values is subject to discussion, but a survey
-of existing exception matching practices (see Appendix A) helps us
+of existing exception matching practices (see **Appendix A**) helps us
 propose a reasonable subset of all values.  Trying to map all errno
 mnemonics, indeed, seems foolish, pointless, and would pollute the root
 namespace.