Fix whitespace errors

These were largely found with three regular expressions:
%> [.;,]
( <%
%> \w+ <

lib/philomena_web/templates/channel/_form.html.heex

@@ -14,11 +14,7 @@
         picarto_channel_name
       </em>
     </code>
-    is
+    is <code>picarto_channel_name</code>.
-    <code>
-      picarto_channel_name
-    </code>
-    .
   </div>
   <div class="fieldlabel">
     The short name of
@@ -28,11 +24,7 @@
         piczel_channel_name
       </em>
     </code>
-    is
+    is <code>piczel_channel_name</code>. <br />
-    <code>
-      piczel_channel_name
-    </code>
-    . <br />
     <br />
   </div>
   <div class="field">

lib/philomena_web/templates/comment/index.html.heex

@@ -7,11 +7,7 @@
     <%= submit("Search", class: "hform__button button") %>
   </div>
   <div class="fieldlabel">
-    For more information, see the
+    For more information, see the <a href="/pages/search_syntax">search syntax documentation</a>. Search results are sorted by creation date.
-    <a href="/pages/search_syntax">
-      search syntax documentation
-    </a>
-    . Search results are sorted by creation date.
   </div>
 <% end %>
 <h2>
@@ -52,31 +48,8 @@
   Default search
 </h3>
 <p>
-  If you do not specify a field to search over, the search engine will
+  If you do not specify a field to search over, the search engine will search for comments with a body that is similar to the query's <em>word stems</em>. For example, comments containing the words <code>winged humanization</code>, <code>wings</code>, and <code>spread wings</code>
-  search for comments with a body that is similar to the query's
+  would all be found by a search for <code>wing</code>, but <code>sewing</code>
-  <em>
-    word stems
-  </em>
-  . For example, comments containing the words
-  <code>
-    winged humanization
-  </code>
-  ,
-  <code>
-    wings
-  </code>
-  , and
-  <code>
-    spread wings
-  </code>
-  would all be found by a search for
-  <code>
-    wing
-  </code>
-  , but
-  <code>
-    sewing
-  </code>
   would not be.
 </p>
 <h3>

lib/philomena_web/templates/gallery/show.html.heex

@@ -57,10 +57,7 @@ info = render(PhilomenaWeb.PaginationView, "_pagination_info.html", page: @image
         A gallery by
       </span>
       <%= link(@gallery.creator.name, to: ~p"/profiles/#{@gallery.creator}") %> with <%= @gallery.image_count %>
-      <%= pluralize("image", "images", @gallery.image_count) %>
+      <%= pluralize("image", "images", @gallery.image_count) %><span class="hide-mobile-t">, last updated <%= pretty_time(@gallery.updated_at) %></span>
-      <span class="hide-mobile-t">
-        , last updated <%= pretty_time(@gallery.updated_at) %>
-      </span>
     </div>
     <div class="block__content flex js-imagelist-info">
       <div class="flex__fixed thumb-tiny-container spacing-right">

lib/philomena_web/templates/post/index.html.heex

@@ -7,11 +7,7 @@
     <%= submit("Search", class: "hform__button button") %>
   </div>
   <div class="fieldlabel">
-    For more information, see the
+    For more information, see the <a href="/pages/search_syntax">search syntax documentation</a>. Search results are sorted by creation date.
-    <a href="/pages/search_syntax">
-      search syntax documentation
-    </a>
-    . Search results are sorted by creation date.
   </div>
 <% end %>
 <h2>
@@ -62,31 +58,8 @@
   Default search
 </h3>
 <p>
-  If you do not specify a field to search over, the search engine will
+  If you do not specify a field to search over, the search engine will search for posts with a body that is similar to the query's <em>word stems</em>. For example, posts containing the words <code>winged humanization</code>, <code>wings</code>, and <code>spread wings</code>
-  search for posts with a body that is similar to the query's
+  would all be found by a search for <code>wing</code>, but <code>sewing</code>
-  <em>
-    word stems
-  </em>
-  . For example, posts containing the words
-  <code>
-    winged humanization
-  </code>
-  ,
-  <code>
-    wings
-  </code>
-  , and
-  <code>
-    spread wings
-  </code>
-  would all be found by a search for
-  <code>
-    wing
-  </code>
-  , but
-  <code>
-    sewing
-  </code>
   would not be.
 </p>
 <h3>

lib/philomena_web/templates/search/_form.html.heex

@@ -111,53 +111,26 @@
     <div class="block__content">
       <div class="hidden walloftext" data-search-help="boolean">
         <strong class="js-search-help-subject"></strong>
-        is a Boolean-valued field. It only accepts the values
+        is a Boolean-valued field. It only accepts the values <code>true</code>
-        <code>
+        and <code>false</code>. <br />
-          true
-        </code>
-        and
-        <code>
-          false
-        </code>
-        . <br />
         <br />
         <em>
           Example:
         </em>
-        to find images which are not animated, you would use
+        to find images which are not animated, you would use <code>animated:false</code>.
-        <code>
-          animated:false
-        </code>
-        .
       </div>
       <div class="hidden walloftext" data-search-help="numeric">
         <strong class="js-search-help-subject"></strong>
-        is a numerical range field. Four qualifiers,
+        is a numerical range field. Four qualifiers, <code>gte</code>
-        <code>
+        (greater than or equal), <code>lte</code>
-          gte
+        (less than or equal), <code>gt</code>
-        </code>
+        (greater than), and <code>lt</code>
-        (greater than or equal),
-        <code>
-          lte
-        </code>
-        (less than or equal),
-        <code>
-          gt
-        </code>
-        (greater than), and
-        <code>
-          lt
-        </code>
         (less than), can be applied to the desired value. <br />
         <br />
         <em>
           Example:
         </em>
-        to find images with a score greater than 100, you would use
+        to find images with a score greater than 100, you would use <code>score.gt:100</code>.
-        <code>
-          score.gt:100
-        </code>
-        .
       </div>
       <div class="hidden walloftext" data-search-help="date">
         <strong class="js-search-help-subject"></strong>
@@ -165,53 +138,26 @@
         <a href="/pages/search_syntax#date-range">
           tweaked subset of the ISO 8601 standard
         </a>
-        , as well as relative dates
+        , as well as relative dates <code>(X minutes/hours/days/months/years ago)</code>. Four qualifiers, <code>gte</code>
-        <code>
+        (greater than or equal), <code>lte</code>
-          (X minutes/hours/days/months/years ago)
+        (less than or equal), <code>gt</code>
-        </code>
+        (greater than), and <code>lt</code>
-        . Four qualifiers,
-        <code>
-          gte
-        </code>
-        (greater than or equal),
-        <code>
-          lte
-        </code>
-        (less than or equal),
-        <code>
-          gt
-        </code>
-        (greater than), and
-        <code>
-          lt
-        </code>
         (less than), can be applied to the desired value. <br />
         <br />
         <em>
           Example:
         </em>
-        to find images created before 2013, you would use
+        to find images created before 2013, you would use <code>created_at.lt:2013</code>.
-        <code>
-          created_at.lt:2013
-        </code>
-        .
       </div>
       <div class="hidden walloftext" data-search-help="literal">
         <strong class="js-search-help-subject"></strong>
-        is a literal field. You can apply apply a wildcard
+        is a literal field. You can apply apply a wildcard <code>*</code>
-        <code>
-          *
-        </code>
         as a substitute for zero or more characters. <br />
         <br />
         <em>
           Example:
         </em>
-        to find images from DeviantArt, you would use
+        to find images from DeviantArt, you would use <code>source_url:*deviantart.com*</code>.
-        <code>
-          source_url:*deviantart.com*
-        </code>
-        .
       </div>
     </div>
   </div>