Rewrite documentation to not say "QSD"

Author: Anthony Lu

docs/admin/program_modules.rst

@@ -158,7 +158,7 @@ This module should be enabled if your program involves students picking and choo
 * Student module control field 'Signup verb': Controls which type of registration students are given when they select a class. The default is "Enrolled," which adds the student to the class roster (i.e. first-come first served). However, you may choose "Applied" to allow teachers to select which students to enroll, or create other registration types for your needs. 
 * Student module control field 'Use priority': When this box is checked, students will be allowed to choose multiple classes per time slot and their registration types will be annotated in the order they signed up. This is typically used with the 'Priority' registration type to allow students to indicate 1st, 2nd and 3rd choices. 
 * Student module control field 'Priority limit': If 'Use priority' is checked, this number controls the maximum number of simultaneous classes that students may register for. 
-* Student module control field 'Register from catalog': If this box is checked, students will see 'Register for section [index]' buttons below the description of each available class in the catalog. If their browser supports Javascript they will be able to register for the classes by clicking those buttons. You will need to add an appropriate fragment to the QSD area on the catalog if you would like students to see their schedule while doing this. 
+* Student module control field 'Register from catalog': If this box is checked, students will see 'Register for section [index]' buttons below the description of each available class in the catalog. If their browser supports Javascript they will be able to register for the classes by clicking those buttons. You will need to add an appropriate fragment to the editable text area on the catalog if you would like students to see their schedule while doing this. 
 * Student module control field 'Visible enrollments': If unchecked, the publicly available catalog will not show how many students are enrolled in each class section: 
 * Student module control field 'Visible meeting times': If unchecked, the publicly available catalog will not show the meeting times of each class section. 
 * Student module control field 'Show emailcodes': If unchecked, the catalog will not show codes such as 'E464:' and 'M21:' before class titles. 
@@ -207,8 +207,8 @@ To override any of these settings, create a Tag (at /admin/tagdict/tag/) for
 the program, with the key donation_settings, and with the value being a JSON
 object with the overriden keys/values.
 
-The module also has a donation pitch built into the inline QSD on that page. It
-can be edited inline by an admin to something more customized.
+The module also has a donation pitch built into the editable text area on that
+page. It can be edited inline by an admin to something more customized.
 
 The module, when enabled, is available at the url
 /learn/<program>/<instance>/donation. It will also show up as an item in the
@@ -542,8 +542,8 @@ To override any of these settings, create a Tag (at /admin/tagdict/tag/) for
 the program, with the key stripe_settings, and with the value being a JSON
 object with the overriden keys/values.
 
-The module also has a donation pitch built into the inline QSD on that page. It
-can be edited inline by an admin to something more customized.
+The module also has a donation pitch built into the editable text area on that
+page. It can be edited inline by an admin to something more customized.
 
 Credit Card Viewer
 ------------------

docs/admin/student_apps.rst

@@ -52,7 +52,7 @@ Now go to /admin/application/formstackappsettings/ and find your program.
 Student Workflow
 ================
 
-Visit /learn///studentapp. If you're logged in as an admin, you should see a page (provided that you set things up correctly). Probably, the only thing there is an empty QSD block and a button that says "Continue".
+Visit /learn///studentapp. If you're logged in as an admin, you should see a page (provided that you set things up correctly). Probably, the only thing there is an empty editable text area and a button that says "Continue".
 
 Verify that pressing "Continue" takes you to your application form, and fills in the username field with your username.
 

docs/dev/directory_structure.rst

@@ -18,7 +18,7 @@ This is not intended to be an exhaustive list, just a summary with some comments
       * ``models``: The main models for ``Program``, ``ClassSubject``, ``ClassSection``; many of the other models used by programs live in other apps, such as ``resources``.
       * ``modules``: This directory contains all the program modules.  The python code for the individual modules is in ``handlers/<name>module.py``; most of the remainder of the directory won’t be relevant to you.  See `<program_modules.rst>`_ for details on the program module system.
 
-    * ``qsd``: This app contains all of the code for QSD (which is the website’s system for admin-editable "quasi-static" text).
+    * ``qsd``: This app contains all of the code for the website’s system for admin-editable text (named QSD for historical reasons).
     * ``users``: This app contains important models like ``ESPUser``, ``Permission``, ``Record``, ``ContactInfo``, and so on.
     * ``*_settings.py``: Various files in which our django settings are kept.  ``django_settings.py`` contains settings used by all sites; ``local_settings.py`` is generated by the setup script and contains site-specific settings.
     * ``urls.py``: Master URL routing table.