tidying, also: preventing comments does not hide existing ones

1 files changed, 26 insertions, 22 deletions

diff --git a/docs/running/requests.md b/docs/running/requests.md
index d3733b591..95261b46d 100644
--- a/docs/running/requests.md
+++ b/docs/running/requests.md
@@ -11,29 +11,31 @@ title: Managing requests
   <a href="{{ site.baseurl }}docs/glossary/#request" class="glossary__link">request</a>.
   As an 
   <a href="{{ site.baseurl }}docs/glossary/#super" class="glossary__link">administrator</a>,
-  there are some things about that request you can change once it's been created.
+  there are some things about that request you can change once it&rsquo;s been created.
 </p>
 
 A request is automatically created when a user submits and (where necessary)
-confirms it. Alaveteli sends it to the authority responsible and handles any
+confirms it. Alaveteli sends it to the
+<a href="{{ site.baseurl }}docs/glossary/#authority" class="glossary__link">authority</a>
+responsible and handles any
 <a href="{{ site.baseurl }}docs/glossary/#response" class="glossary__link">responses</a>.
 Usually this process runs without needing any intervention from an
-administrator. But sometimes you'll want to change some aspect of the
-request, or the way Alaveteli is handling it.
+administrator. But sometimes you'll want to change some aspect of the request,
+or the way Alaveteli is handling it.
 
 ## What state is the request in?
 
 Every request moves through a series of 
 <a href="{{ site.baseurl }}docs/glossary/#state" class="glossary__link">states</a>,
-indicating its progress. Usually a new request will be in the `waiting_response`
-state until something happens to change that &mdash; for example, a response is
-received.
+indicating its progress. Usually a new request will be in the
+`waiting_response` state until something happens to change that &mdash; for
+example, a response is received.
 
 However, states can't always be set automatically, because they require a
 decision to be made on what kind of answer the authority provided in the
 response. For states like this, Alaveteli invites the original requester to
-describe its state &mdash; for example, when a response is received they can
-change the state to `successful`, `partially_successful` or `not_held` (if the
+describe it &mdash; for example, when a response is received they can change
+the state to `successful`, `partially_successful` or `not_held` (if the
 authority replied to say they don't have the information requested).
 
 <div class="attention-box info">
@@ -49,7 +51,6 @@ sets its "awaiting description" status appropriately.
 
 ## Changing things about a request
 
-
 To change any of these settings, go to the 
 <a href="{{ site.baseurl }}docs/glossary/#admin" class="glossary__link">admin interface</a>,
 click on **Requests**, then click on the title of the request you want to affect. 
@@ -69,10 +70,10 @@ Click the **Edit metadata** button.
       Title
     </td>
     <td>
-      The title is shown on the request's page, but is also used in the URL
-      (the text is changed to lower case, punctuation is removed and, if
-      necessary, a number is added for disambiguation &mdash; this is called
-      the "slug").
+      The <em>title</em> is shown on the request&rsquo;s page, but is also used
+      in the URL (the text is changed to lower case, punctuation is removed
+      and, if necessary, a number is added for disambiguation &mdash; this is
+      called the &ldquo;slug&rdquo;).
       <p>
         Note that changing the title changes the URL, because the slug changes
         &mdash; this means any links to the <em>old</em> URL will no longer
@@ -129,15 +130,16 @@ Click the **Edit metadata** button.
       What happens to rejected responses?
     </td>
     <td>
-      The <strong>Handle rejected responses...</strong> setting specificies what happens
-      to responses that are not allowed (see previous entry):
+      The <strong>Handle rejected responses...</strong> setting specificies
+      what happens to responses that are not allowed (see previous entry):
       <ul>
         <li>
           <code>bounce</code>: responses are sent back to their sender
         </li>
         <li>
           <code>holding pen</code>: responses are put in the
-          <a href="{{ site.baseurl }}docs/glossary/#holding_pen" class="glossary__link">holding pen</a> for an administrator to deal with
+          <a href="{{ site.baseurl }}docs/glossary/#holding_pen" class="glossary__link">holding pen</a>
+          for an administrator to deal with
         </li>
         <li>
           <code>blackhole</code>: responses are destroyed by being sent to a
@@ -175,8 +177,10 @@ Click the **Edit metadata** button.
     <td>
       The <strong>Are comments allowed?</strong> setting simply you choose to 
       allow or forbid annotations and comments on this request.
-      <!-- are existing comments deleted? -->
-      <br>
+      <p>
+        Note that this won&rsquo;t hide any annotations that have already
+        been left on the reques &mdash; it only prevents users adding new ones.
+      </p>
     </td>
   </tr>
   <tr>
@@ -194,12 +198,12 @@ Click the **Edit metadata** button.
         are very many in the database.
       </p>
       <p>
-        Although it's a little more complex than tags on requests,
+        Although it&rsquo;s a little more complex than tags on requests,
         <a href="{{ site.baseurl }}docs/glossary/#category" class="glossary__link">categories</a>
         also use tags:
         see 
-        <a href="{{ site.baseurl }}docs/running/categories_and_tags/">more about tags</a> for a little
-        more information.
+        <a href="{{ site.baseurl }}docs/running/categories_and_tags/">more about tags</a>
+        for a little more information.
       </p>
     </td>
   </tr>