Some cleanup in the docs.
diff --git a/Doc/library/xml.dom.rst b/Doc/library/xml.dom.rst
index 5f0a9aa..1fbca03 100644
--- a/Doc/library/xml.dom.rst
+++ b/Doc/library/xml.dom.rst
@@ -40,13 +40,13 @@
package <http://pyxml.sourceforge.net/>`_. Refer to the documentation bundled
with that package for information on the current state of DOM Level 3 support.
-.. % What if your needs are somewhere between SAX and the DOM? Perhaps
-.. % you cannot afford to load the entire tree in memory but you find the
-.. % SAX model somewhat cumbersome and low-level. There is also a module
-.. % called xml.dom.pulldom that allows you to build trees of only the
-.. % parts of a document that you need structured access to. It also has
-.. % features that allow you to find your way around the DOM.
-.. % See http://www.prescod.net/python/pulldom
+.. What if your needs are somewhere between SAX and the DOM? Perhaps
+ you cannot afford to load the entire tree in memory but you find the
+ SAX model somewhat cumbersome and low-level. There is also a module
+ called xml.dom.pulldom that allows you to build trees of only the
+ parts of a document that you need structured access to. It also has
+ features that allow you to find your way around the DOM.
+ See http://www.prescod.net/python/pulldom
DOM applications typically start by parsing some XML into a DOM. How this is
accomplished is not covered at all by DOM Level 1, and Level 2 provides only
@@ -157,7 +157,7 @@
within the class rather than at the module level to conform with the DOM
specifications.
-.. % Should the Node documentation go here?
+.. Should the Node documentation go here?
.. _dom-objects:
@@ -906,7 +906,7 @@
This is raised if data is specified for a node which does not support data.
- .. % XXX a better explanation is needed!
+ .. XXX a better explanation is needed!
.. exception:: NoModificationAllowedErr
@@ -919,7 +919,7 @@
Raised when an invalid or illegal string is specified.
- .. % XXX how is this different from InvalidCharacterErr ???
+ .. XXX how is this different from InvalidCharacterErr?
.. exception:: WrongDocumentErr
@@ -1001,8 +1001,8 @@
a Python string or Unicode string. Applications should be able to handle
Unicode whenever a string is returned from the DOM.
-The IDL :keyword:`null` value is mapped to ``None``, which may be accepted or
-provided by the implementation whenever :keyword:`null` is allowed by the API.
+The IDL ``null`` value is mapped to ``None``, which may be accepted or
+provided by the implementation whenever ``null`` is allowed by the API.
.. _dom-accessor-methods:
@@ -1011,7 +1011,7 @@
^^^^^^^^^^^^^^^^
The mapping from OMG IDL to Python defines accessor functions for IDL
-:keyword:`attribute` declarations in much the way the Java mapping does.
+``attribute`` declarations in much the way the Java mapping does.
Mapping the IDL declarations ::
readonly attribute string someValue;
@@ -1030,13 +1030,13 @@
objects are accessed via CORBA. While this does require some additional
consideration for CORBA DOM clients, the implementers with experience using DOM
over CORBA from Python do not consider this a problem. Attributes that are
-declared :keyword:`readonly` may not restrict write access in all DOM
+declared ``readonly`` may not restrict write access in all DOM
implementations.
In the Python DOM API, accessor functions are not required. If provided, they
should take the form defined by the Python IDL mapping, but these methods are
considered unnecessary since the attributes are accessible directly from Python.
-"Set" accessors should never be provided for :keyword:`readonly` attributes.
+"Set" accessors should never be provided for ``readonly`` attributes.
The IDL definitions do not fully embody the requirements of the W3C DOM API,
such as the notion of certain objects, such as the return value of