Merge pull request #468 from NYUCCL/proof-announcement

Proof announcement
NYUCCL · Mar 14, 2021 · e593052 · e593052
2 parents 7c19543 + 7d7bab2
commit e593052
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 7 deletions.
diff --git a/doc/migrating.rst b/doc/migrating.rst
@@ -1,10 +1,15 @@
 .. _migrating:
 
+Migrating from psiTurk 2.0 to 3.0
+=================================
 
 Announcing psiTurk 3.0
 ~~~~~~~~~~~~~~~~~~~~~~
 
 psiTurk 2.0 launched on April 28, 2014 and there has been (according to github) 786 
+*A message from project founder Todd Gureckis.*
+
+psiTurk 2.0 launched on April 28, 2014 and there has been (according to github) 786
 commits since then to the project from a wide variety of contributors. The evolution and
 longevity of the project really has exceeded anything the original authors thought
 would be possible. In the seven years since 2.0 was first tagged so many things have changed
@@ -27,20 +32,21 @@ means psiTurk acts more like a traditional Flask "web application" rather than a
 command line tool, although the command line interface remains for interacting with Amazon and 
 for development.
 
-In addition to the hard work (lead really by Dave Eargle), version 3.0 offers several new features
-including a "campaign mode" which allows you to run a certain number of subject (say 100) by repeatedly 
-posting lower cost 9 assignment HITs, a dashboard for managing hits,. In addition, a major change 
-since 2.0 is support for Python 3.0 and the changes that entailed to work with more recent 
+In addition to the hard decoupling work (led really by Dave Eargle), version 3.0 offers several new features
+including a "campaign mode" which allows you to run a certain number of subject (say 100) by repeatedly
+posting lower cost 9 assignment HITs, and a dashboard for managing hits. In addition, a major change 
+since 2.0 is support for Python 3.0 and the changes that entailed to work with more recent
 versions of boto Mturk python api.
 
 There may be some growing pains as people adjust to the new workflow so a goal is to update the
 documentation to reflect the new changes as soon as possible. As always, assitance from the psiturk
 community to make this documentation is always appreciated!
 
 
+Migration technical considerations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Migrating from psiturk 2 to 3
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Below are some notable technical differences between psiTurk 2 and psiTurk 3.
 
 No More Secure Ad Server
 ------------------------

diff --git a/doc/tutorials/heroku.rst b/doc/tutorials/heroku.rst
@@ -97,7 +97,7 @@ database for collecting data:
  .. important::
  psiTurk prefers environment variables over all other config file settings.
  Most environment settings need to prepend ``PSITURK_`` to the corresponding
- config setting name, with the exception of two environment variables::
+ config setting name, with the exception of two environment variables:
 
  1. ``DATABASE_URL``
  2. ``PORT``