aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2011-04-03 07:55:18 +0000
committerSimon Tatham <anakin@pobox.com>2011-04-03 07:55:18 +0000
commit2054da9f682680392ce28a04333ca659479d9606 (patch)
treef0794024630ca067d74668eb75a2d0a12e540c95
parent980880be1f2801b2a69fcc67abc0f5827fd106f2 (diff)
downloadpuzzles-2054da9f682680392ce28a04333ca659479d9606.zip
puzzles-2054da9f682680392ce28a04333ca659479d9606.tar.gz
puzzles-2054da9f682680392ce28a04333ca659479d9606.tar.bz2
puzzles-2054da9f682680392ce28a04333ca659479d9606.tar.xz
Move up midend_is_solved() in the developer docs from subheading to
heading level. It's _almost_ apt to have it as a subheading of midend_solve(), but not quite, and it certainly wasn't intentional - I must have absentmindedly typed the wrong Halibut command letter. [originally from svn r9142]
-rw-r--r--devel.but2
1 files changed, 1 insertions, 1 deletions
diff --git a/devel.but b/devel.but
index 571b960..5e9ff22 100644
--- a/devel.but
+++ b/devel.but
@@ -3118,7 +3118,7 @@ The front end can expect its drawing API and/or
\cw{activate_timer()} to be called from within a call to this
function.
-\S{midend-is-solved} \cw{midend_is_solved()}
+\H{midend-is-solved} \cw{midend_is_solved()}
\c int midend_is_solved(midend *me);