summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2007-11-13 15:43:54 -0500
committerJoey Hess <joey@kodama.kitenet.net>2007-11-13 15:43:54 -0500
commit335942c0ea3b3e0b3fa286592ffee55873c7f9a2 (patch)
treee10d657cc6d024ce036860a3819685b6c7c9ea86
parentc3b0e5fd035d82472408fd75b8f604ae95a88fe0 (diff)
silly markdown
-rw-r--r--doc/bugs/search_for_locale_data_in_the_installed_location.mdwn4
-rw-r--r--doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn2
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/bugs/search_for_locale_data_in_the_installed_location.mdwn b/doc/bugs/search_for_locale_data_in_the_installed_location.mdwn
index 6a4bd03a6..a7fab5571 100644
--- a/doc/bugs/search_for_locale_data_in_the_installed_location.mdwn
+++ b/doc/bugs/search_for_locale_data_in_the_installed_location.mdwn
@@ -15,8 +15,8 @@ It seems like gettext only searches for locale information in /usr/share/locale,
-- [[ThomasBleher]]
> According to my testing, this patch makes ikiwiki's localisation fail for
-> LANG=fr_FR when everything is installed to the default locations,
-> though LANG=es_ES works. I don't understand this behavior, especially
+> `LANG=fr_FR` when everything is installed to the default locations,
+> though `LANG=es_ES` works. I don't understand this behavior, especially
> since strace shows it successfully opening the file
> `/usr/share/locale/fr/LC_MESSAGES/ikiwiki.mo`.
>
diff --git a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
index 40c0e79b8..9382056da 100644
--- a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
+++ b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn
@@ -9,6 +9,6 @@ In our team internal wiki, we wish to impose a policy that all edits must have a
> I don't feel this belongs in ikiwiki core, but would accept a plugin that
> does it. I think that can be done using a formbuilder_setup hook.
-> BTW, it wmuld probably be better to validate against a comment_regexp,
+> BTW, it wuld probably be better to validate against a `comment_regexp`,
> so that when the evil admins notice that /.+/ is absurdly easy for users
> to get around (by using " "), they can tighten it down. --[[Joey]]