On completion-engines page, put example first.

On that page, we have regular expressions (which are not new-user
friendly) and an example (which is new-user friendly).  So the example
should come before the regular expressions.

1 files changed, 7 insertions, 7 deletions

diff --git a/pages/completion_engines.coffee b/pages/completion_engines.coffee
index 790f2968..4ae9d447 100644
--- a/pages/completion_engines.coffee
+++ b/pages/completion_engines.coffee
@@ -13,13 +13,6 @@ DomUtils.documentReady ->
     html.push "<div class=\"engine\">"
     if engine.example.explanation
       html.push "<p>#{engine.example.explanation}</p>"
-    if engine.regexps
-      html.push "<p>"
-      html.push "Regular expression#{if 1 < engine.regexps.length then 's' else ''}:"
-      html.push "<pre>"
-      html.push "#{cleanUpRegexp re}\n" for re in engine.regexps
-      html.push "</pre>"
-      html.push "</p>"
     if engine.example.searchUrl and engine.example.keyword
       engine.example.description ||= engine.constructor.name
       html.push "<p>"
@@ -28,6 +21,13 @@ DomUtils.documentReady ->
       html.push "#{engine.example.keyword}: #{engine.example.searchUrl} #{engine.example.description}"
       html.push "</pre>"
       html.push "</p>"
+    if engine.regexps
+      html.push "<p>"
+      html.push "Regular expression#{if 1 < engine.regexps.length then 's' else ''}:"
+      html.push "<pre>"
+      html.push "#{cleanUpRegexp re}\n" for re in engine.regexps
+      html.push "</pre>"
+      html.push "</p>"
     html.push "</div>"
 
   document.getElementById("engineList").innerHTML = html.join ""