X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/e42b1409b242e75df9318d6472fe6adf7ba00df2..80f464bb09a0b47e82feef77df4cfa76195af460:/doc/bugs/autosetup_python_warnings.mdwn

diff --git a/doc/bugs/autosetup_python_warnings.mdwn b/doc/bugs/autosetup_python_warnings.mdwn
index 5c081dac2..d7920b921 100644
--- a/doc/bugs/autosetup_python_warnings.mdwn
+++ b/doc/bugs/autosetup_python_warnings.mdwn
@@ -53,7 +53,8 @@ the XML-RPC libs) until the methods using them are called. --[[schmonz]]
 
 -----
 
-It's more complicated than I thought. Findings and questions:
+It's more complicated than I thought. Findings and questions so
+far:
 
 ### Failing to load an external plugin should be an error
 
@@ -64,7 +65,7 @@ written in any language, ikiwiki assumes loading succeeded.
 Let's take [[!iki plugins/rst]] as an example. It's written in
 Python and uses `proxy.py` to handle XML-RPC communication with
 ikiwiki. Let's say that `proxy.py` compiles, but `rst` itself
-doesn't. We'd like ikiwiki to know the module isn't loaded, and
+doesn't. We'd like ikiwiki to know the plugin isn't loaded, and
 we'd like an error message about it (not just the Python errors).
 
 Now let's say `rst` would be fine by itself, but `proxy.py` doesn't