--- a/doc/announcement.txt	Thu Jun 21 19:49:26 2018 -0400
+++ b/doc/announcement.txt	Sat Jun 23 21:24:42 2018 -0400
@@ -42,7 +42,8 @@
   otherwise they will clash with the "hidden" input elements generated by
   indexargs_form itself.
 
-  For example:
+  For example::
+
     <tal:block replace="structure python:request.indexargs_form(
                       sort=0,group=0,filter=0,columns=0,
                       exclude=['type','status','assignedto'])"/>
@@ -82,9 +83,9 @@
   quiet=True/False option for all property types. When quiet=True
   changes to the property will not be displayed in the::
 
-    confirmation banner (shown in green) when a change is made
-    property change section of change note (nosy emails)
-    web history display for an item.
+    * confirmation banner (shown in green) when a change is made
+    * property change section of change note (nosy emails)
+    * web history display for an item.
 
   Note that this may confuse users if used on a property that is
   meant to be changed by a user. It is most useful on administrative
@@ -94,9 +95,9 @@
 
     http://psf.upfronthosting.co.za/roundup/meta/issue249
 
-  Support for setting quiet when calling the class specifiers::
+  Support for setting quiet when calling the class specifiers.
+  E.G. prop=String(quiet=True) rather than::
 
-    E.G. prop=String(quiet=True) rather than::
       prop=String()
       prop.quiet=True
 
@@ -106,7 +107,7 @@
   changed while implementing fix for issue2550864. Filtering of
   quiet properties pushed down to the hyperdb.py::Class::history
   function. This fixes a small bug in the implementation that caused
-  a limiting the templating history call to display fewer than the
+  a limiting the templating history call to display fewer than
   the requested number of items if some were quiet.)
 - issue2550767: Add newitemcopy.py detector to notify users of new
   items.  Added to detectors directory and a README.txt generated to
@@ -140,7 +141,7 @@
   Change to classic tracker template to provide a check box (checked
   by default) that keeps the user on the "Add new keyword" page after
   submitting a new keyword. Usually after submission, you will see the
-  the page for the new keyword to allow you to change the name of the
+  page for the new keyword to allow you to change the name of the
   keyword. (John Rouillard)
 - issue2550757 - internal restructuring to allow admin.py to be tested
   more easily. W. Trevor King (wking)/ John Rouillard.
@@ -293,7 +294,7 @@
   pagesize is not propigated to the prev link. This patch fixes that.
   Patch provided by John Kristensen. (Applied, light testing by John
   Rouillard.)
-- issue2550850 anypy/email_.py uses BSPACE which is not defined in python 2.7
+- issue2550850 anypy/email\_.py uses BSPACE which is not defined in python 2.7
   Supplied a definition for BSPACE since it seems to not be defined
   anywhere. Reported by Dennis Boone. (John Rouillard)
 - Validate properties specified for sorting and grouping in index
@@ -390,7 +391,7 @@
   db/text-index: already locked. Put in a retry loop that will attempt
   to get the lock. Total delay approx 4.5 seconds. (John Rouillard)
 - issue2550727: db.newid is broken with sqlite. Added proper transaction
-  lock around the sql code to get a new id. The the locking
+  lock around the sql code to get a new id. The locking
   that pysqlite attempts had to be defeated because it is broken.
   Had to explicitly manage transactions with BEGIN IMMEDIATE and call
   sql_commit. Note that this reduces performance in return for accuracy.
@@ -533,7 +534,7 @@
     python demo.py
 
 Release info and download page:
-     http://pypi.python.org/pypi/roundup
+     http://pypi.org/project/roundup
 Source and documentation is available at the website:
      http://roundup-tracker.org/
 Mailing lists - the place to ask questions:
@@ -566,11 +567,11 @@
 
 It comes with five issue tracker templates
 
- * a classic bug/feature tracker
- * a minimal skeleton;
- * a more extensive devel tracker for bug/features etc.
- * a responsive version of the devel tracker
- * a jinja2 based template based on devel
+* a classic bug/feature tracker
+* a minimal skeleton;
+* a more extensive devel tracker for bug/features etc.
+* a responsive version of the devel tracker
+* a jinja2 based template based on devel
 
 and four database back-ends (anydbm, sqlite, mysql and postgresql).