Revising policy key names to match new UI

docs/en_us/course_authors/source/building_course/setting_up_student_view.rst

@@ -137,32 +137,29 @@ could advertise the start date as **Spring, 2014**.
 To set an advertised start date:
 
 #. From the **Settings** menu, select **Advanced Settings**.
-#. Find the policy key **advertised_start**. The default value is **null**.
-#. Enter the date you want as an advertised start date.  You can use any string,
-   enclosed in double quotation marks. If you format the string as a date (for
-   example, as 02/01/2014), the value is parsed and presented to students as a
-   date.
+#. Find the **Course Advertised Start Date** policy key. The default value is
+   **null**.
+#. Enter the value you want to display as the advertised start date. You can
+   use any string, enclosed in double quotation marks. If you format the string
+   as a date (for example, as 02/01/2014), the value is parsed and presented to
+   students as a date.
 
   .. image:: ../Images/advertised_start.png
-   :alt: Image of the advertised start date policy key
+   :alt: Image of the advertised start date policy key with a value of "anytime, self-paced"
 
 4. Click **Save Changes** at the bottom of the page.
 
-The start date shown on the student's dashboard is now the value of the
-advertised_start policy key:
+  The start date shown on the dashboard is now the value of the **Course
+  Advertised Start Date** policy key:
 
-.. image:: ../Images/dashboard-course_adver_start.png
- :alt: An image of a course listing in the student dashboard, with the
+  .. image:: ../Images/dashboard-course_adver_start.png
+   :alt: An image of a course listing in the student dashboard, with the
      advertised start date circled.
 
 If you do not change the default course start date (01/01/2030), and the
-**advertised_start** policy value is ``null``, then the student dashboard does
-not list a start date for the course.  Students just see that the course has not
-yet started:
-
-.. image:: ../Images/dashboard-course_not_started.png
- :alt: Image of a course listing in the student dashboard, with no start date
-
+**Course Advertised Start Date** policy value is ``null``, then the student
+dashboard does not list a start date for the course. Students just see that
+the course has not yet started.
 
 .. _The Course End Date:
 

docs/en_us/course_authors/source/creating_content/create_html_component.rst

@@ -436,10 +436,8 @@ To create an HTML component that contains LaTeX code:
 #. Enable the policy key in your course.
 
    #. In Studio, click **Settings**, and then click **Advanced Settings**.
-   #. On the **Advanced Settings** page, scroll down to the
-      **use_latex_compiler** policy key.
-   #. In the **Policy Value** field next to the **use_latex_compiler** policy
-      key, change **false** to **true**.
+   #. In the field for the **Enable LaTeX Compiler** policy key, change
+      **false** to **true**.
    #. At the bottom of the page, click **Save Changes**.
 
 #. In the unit where you want to create the component, click **html** under

docs/en_us/course_authors/source/exercises_tools/annotation.rst

@@ -20,24 +20,21 @@ To create an annotation problem, you'll add the Annotation advanced component to
 
 #. Add the Annotation advanced component. 
 
-    #. On the **Settings** menu, click **Advanced Settings**.
+    #. From the **Settings** menu select **Advanced Settings**.
 
-    #. On the **Advanced Settings** page, locate the **Manual Policy Definition** section, and then locate the **advanced_modules** policy key (this key is at the top of the list).
+    #. In the field for the **Advanced Module List** policy key, place your
+       cursor between the brackets.
 
-    .. image:: /Images/AdvancedModulesEmpty.png
-         :alt: Image of the Manual Policy Definition section of the Advanced Settings page
-
-    3. Under **Policy Value**, place your cursor between the brackets, and
-       then enter the following. Make sure to include the quotation marks.
+    #. Enter the following value. Make sure to include the quotation marks.
 
        ``"annotatable"``
 
-    #. At the bottom of the page, click **Save Changes**.
+    4. At the bottom of the page, click **Save Changes**.
 
        The page refreshes automatically. At the top of the page, you see a
        notification that your changes have been saved.
 
-    #. Return to the unit where you want to add the specialized problem. The
+    5. Return to the unit where you want to add the specialized problem. The
        list of possible components now contains an Advanced component.
 
        .. image:: /Images/AdvancedComponent.png
@@ -46,8 +43,8 @@ To create an annotation problem, you'll add the Annotation advanced component to
 2. Add the **Instructions** and **Guided Discussion** segments of the
 problem.
 
-    #. In the unit where you want to create the problem, click **Advanced**
-       under **Add New Component**.
+    #. In the unit where you want to create the problem, under **Add New
+       Component** click **Advanced**.
     #. In the list of problem types, click **Annotation**.
     #. In the component that appears, click **Edit**.
     #. In the component editor, replace the example code with your own code.

docs/en_us/course_authors/source/exercises_tools/lti_component.rst

@@ -15,11 +15,14 @@ version 1.1.1 specifications.
 
 You can use an LTI component in several ways.
 
-- You can add external LTI content that is displayed only, such as
-   textbook content that doesn’t require a student response.
-- You can add external LTI content that requires a student response. An
-   external provider will grade student responses.
-- You can use the component as a placeholder for syncing with an external grading system. 
+* You can add external LTI content that is displayed only, such as textbook
+  content that doesn’t require a student response.
+
+* You can add external LTI content that requires a student response. An external
+  provider will grade student responses.
+
+* You can use the component as a placeholder for syncing with an external
+  grading system.
 
 For example, the following LTI component incorporates a Cerego tool that students interact with. 
 
@@ -40,7 +43,8 @@ unit, you need the following information.
    provider. The launch URL is the URL that Studio sends to the external
    LTI provider so that the provider can send back students’ grades.
 
-- The **lti_passports** policy key. This policy key has three parts: an LTI ID, a client key, and a client secret.
+- The **LTI Passports** policy key. This policy key has three parts: an LTI ID,
+  a client key, and a client secret.
 
   -  The **LTI ID**. This is a value that you create to refer to the external LTI
      provider. You should create an LTI ID that you can remember easily.
@@ -61,11 +65,11 @@ unit, you need the following information.
      may be a string of numbers and letters such as **23746387264** or
      **yt4984yr8**.
 
-  To create the **lti_passports** policy key, combine the LTI ID, client key, and client secret in the following format (make sure to include the colons):
+  To create the **LTI Passports** policy key, combine the LTI ID, client key, and client secret in the following format (make sure to include the colons):
 
   ``lti_id:client_key:client_secret``
 
-  For example, an **lti_passports** policy key may resemble any of the following:
+  For example, an **LTI Passports** policy key may resemble any of the following:
 
   ``test_lti_id:b289378-f88d-2929-ctools.school.edu:secret``
   
@@ -79,32 +83,31 @@ Create an LTI Component
 
 Creating an LTI component in your course has three steps.
 
-#. Add LTI to the **advanced_modules** policy key.
+#. Add LTI to the **Advanced Module List**  policy key.
 #. Register the LTI provider.
 #. Create the LTI component in an individual unit.
 
 ======================================================
-Step 1. Add LTI to the Advanced Modules Policy Key
+Step 1. Add LTI to the Advanced Module List Policy Key
 ======================================================
 
 #. On the **Settings** menu, click **Advanced Settings**.
 
-#. On the **Advanced Settings** page, locate the **advanced_modules** policy key (this key is at the top of the list).
+#. In the field for the **Advanced Module List** policy key, place your cursor
+   between the brackets.
 
-#. Under **Policy Value**, place your cursor between the brackets, and
-   then enter ``“lti”``. Make sure to include the quotation marks, but
-   not the period.
+#. Enter ``“lti”``. Make sure to include the quotation marks, but not the
+   period.
 
    .. image:: /Images/LTIPolicyKey.png
      :width: 500
      :alt: Image of the advanced_modules key in the Advanced Settings page, with the LTI value added
 
-   **Note** If the **Policy Value** field already contains text, place your
-   cursor directly after the closing quotation mark for the final item, and
-   then enter a comma followed by ``“lti”`` (make sure that you include the
-   quotation marks).
+.. note:: If the **Advanced Module List** field already contains text, place your cursor directly
+   after the closing quotation mark for the final item, and then enter a comma
+   followed by ``“lti”`` (make sure that you include the quotation marks).
 
-#. At the bottom of the page, click **Save Changes**.
+4. At the bottom of the page, click **Save Changes**.
 
 The page refreshes automatically. At the top of the page,
 you see a notification that your changes have been saved.
@@ -113,18 +116,23 @@ you see a notification that your changes have been saved.
 Step 2. Register the External LTI Provider
 ==========================================
 
-To register the external LTI provider, you’ll add the **lti_passports** policy key to the course's advanced settings.
+To register the external LTI provider, you’ll add the **LTI Passports** policy
+key to the course's advanced settings.
 
-#. On the **Advanced Settings** page, locate the **lti_passports**
+#. On the **Advanced Settings** page, locate the **LTI Passports**
    policy key.
 
-#. In the **Policy Value** field for the **lti_passports** policy key, place your cursor between the brackets, and then enter the **lti_passports** policy key surrounded by quotation marks.
+#. Place your cursor between the brackets.
+
+#. Enter the **LTI Passports** policy key surrounded by quotation marks.
 
-   For example, the text in the **Policy Value** field may resemble the following.
+   For example, the text in the **LTI Passports** field may resemble the following.
 
    ``"test_lti_id:b289378-f88d-2929-ctools.umich.edu:secret"``
 
-   If you have multiple LTI providers, separate the values for each **lti_passports** policy key with a comma. Make sure to surround each entry with quotation marks.
+   If you have multiple LTI providers, separate the values for each **LTI
+   Passports** policy key with a comma. Make sure to surround each entry with
+   quotation marks.
 
    .. code-block:: xml
 
@@ -132,12 +140,11 @@ To register the external LTI provider, you’ll add the **lti_passports** policy
       "id_21441:b289378-f88d-2929-ctools.school.edu:23746387264",
       "book_lti_provider_from_new_york:b289378-f88d-2929-ctools.company.com:yt4984yr8"
 
+4. At the bottom of the page, click **Save Changes**.
 
-#. At the bottom of the page, click **Save Changes**.
-
-The page refreshes automatically. At the top of the page,
-you see a notification that your changes have been saved, and you can
-see your entries for the **lti_passports** policy key.
+The page refreshes automatically. At the top of the page, you see a
+notification that your changes have been saved, and you can see your entries
+for the **LTI Passports** policy key.
 
 ==========================================
 Step 3. Add the LTI Component to a Unit

docs/en_us/course_authors/source/exercises_tools/problem_in_latex.rst

@@ -26,8 +26,8 @@ To create a problem written in LaTeX:
 #. Enable the policy key in your course.
 
    #. In Studio, click **Settings**, and then click **Advanced Settings**.
-   #. On the **Advanced Settings** page, scroll down to the **use_latex_compiler** policy key.
-   #. In the **Policy Value** field next to the **use_latex_compiler** policy key, change **false** to **true**.
+   #. In the field for the **Enable LaTeX Compiler** policy key, change
+      **false** to **true**.
    #. At the bottom of the page, click **Save Changes**.
    
 #. In the unit where you want to create the problem, click **Problem**

docs/en_us/course_authors/source/exercises_tools/vitalsource.rst

@@ -34,11 +34,16 @@ Step 1. Obtain Information from VitalSource
 
 To create a VitalSource Bookshelf e-reader, you need the following information from Vital Source:
 
-- The **lti_passports** policy key. This policy key enables you to create an LTI component for the VitalSource Bookshelf e-reader. For more information about the **lti_passports** policy key, see :ref:`LTI Information` in :ref:`LTI Component`.
+- The **LTI Passports** policy key. This policy key enables you to create an
+  LTI component for the VitalSource Bookshelf e-reader. For more information
+  about the **LTI Passports** policy key, see :ref:`LTI Information` in
+  :ref:`LTI Component`.
 
 - The Vital Souce Book ID (VBID) for your e-book. This is a specific code that Vital Source creates for the book when Vital Source adds the e-book to its inventory.
 
-To obtain this information, your course team selects a member point person (MPP) to work with Vital Source. Vital Source delivers the **lti_passports** policy key and VBID to the MPP.
+To obtain this information, your course team selects a member point person
+(MPP) to work with Vital Source. Vital Source delivers the **LTI Passports**
+policy key and VBID to the MPP.
 
 
 .. _VS Modify Advanced Settings:
@@ -47,30 +52,36 @@ To obtain this information, your course team selects a member point person (MPP)
 Step 1. Modify the Course's Advanced Settings
 =============================================
 
-In this step, you'll modify the course's advanced settings to allow you to create an LTI component and add the **lti_passports** policy key for Vital Source. 
+In this step, you'll modify the course's advanced settings to allow you to
+create an LTI component and add the **LTI Passports** policy key for Vital
+Source.
 
 #. In Studio, click the **Settings** menu, and then click **Advanced Settings**.
 
-#. On the **Advanced Settings** page, locate the **advanced_modules** policy key.
+#. In the field for the  **Advanced Module List** policy key, place your cursor
+   between the brackets.
 
-#. Under **Policy Value**, place your cursor between the brackets, and then enter ``“lti”``. Make sure to include the quotation marks, but not the period.
+#. Enter ``“lti”``. Make sure to include the quotation marks, but not the
+   period.
 
    .. image:: /Images/LTIPolicyKey.png
-    :alt: Image of the advanced_modules key in the Advanced Settings page, with the LTI value added
+    :alt: Image of the Advanced Module List key in the Advanced Settings page, with the LTI value added
 
-   **Note** If the **Policy Value** field already contains text, place your cursor directly after the closing quotation mark for the final item, and then enter a comma followed by ``“lti”`` (make sure that you include the quotation marks). For example, the text in the **Policy Value** field may resemble the following:
+  .. note:: If the value field already contains text, place your cursor directly after the closing quotation mark for the final item, and then enter a comma followed by ``“lti”`` (make sure that you include the quotation marks). For example, the value for **Advanced Module List** may resemble the following:
 
    ``["value_1","lti"]``
 
-4. Scroll down to the **lti_passports** policy key.
+4. Scroll down to the **LTI Passports** policy key.
 
-#. Under **Policy Value**, place your cursor between the brackets, and then enter the value for the **lti_passports** policy key that you obtained from Vital Source. Make sure to surround the value with quotation marks.
+#. In the policy value field, place your cursor between the brackets, and then
+   enter the value for the **LTI Passports** policy key that you obtained from
+   Vital Source. Make sure to surround the value with quotation marks.
 
-    For example, the value in this field may resemble the following:
+   For example, the value in this field may resemble the following:
 
-    ``"id_21441:b289378-ctools.school.edu:23746387264"``
+   ``"id_21441:b289378-ctools.school.edu:23746387264"``
 
-#. At the bottom of the page, click **Save Changes**.
+6. At the bottom of the page, click **Save Changes**.
 
 The page refreshes automatically. At the top of the page, you see a notification that your changes have been saved.
 

docs/en_us/course_authors/source/exercises_tools/word_cloud.rst

@@ -29,19 +29,19 @@ To create a word cloud tool:
 
     #. On the **Settings** menu, click **Advanced Settings**.
 
-    #. On the **Advanced Settings** page, locate the **Manual Policy Definition** section, and then locate the **advanced_modules** policy key (this key is at the top of the list).
+    #. In the field for the **Advanced Module List** policy key, place your
+       cursor between the brackets.
 
-    #. Under **Policy Value**, place your cursor between the brackets, and
-       then enter the following. Make sure to include the quotation marks.
+    #. Enter the following value. Make sure to include the quotation marks.
 
        ``"word_cloud"``
 
-    #. At the bottom of the page, click **Save Changes**.
+    4. At the bottom of the page, click **Save Changes**.
 
        The page refreshes automatically. At the top of the page, you see a
        notification that your changes have been saved.
 
-    #. Return to the unit where you want to add the specialized problem. The
+    5. Return to the unit where you want to add the specialized problem. The
        list of possible components now contains an Advanced component.
 
 #. In the unit where you want to create the problem, click **Advanced**

docs/en_us/course_authors/source/releasing_course/beta_testing.rst

@@ -4,9 +4,17 @@
 Beta Testing a Course
 #############################
 
-When a course is being designed in Studio, the course team can choose **View Live** to assess their progress in designing the course, test their work, find gaps and errors, and mimic the student experience. To gather information about the overall experience of taking a course, you can also conduct a beta test of the course. 
-
-Beta testers have early access to the course. Beta testers are not members of the course team or staff: they don't have information about "how it's supposed to work". They use their own computers and internet connections to view videos, follow links, and complete problems. They interact with the course exactly as students will, but see the course materials before other enrolled students do. 
+When a course is being designed in Studio, the course team can choose **View
+Live** to assess their progress in designing the course, test their work, find
+gaps and errors, and mimic the student experience. To gather information about
+the overall experience of taking a course, you can also conduct a beta test of
+the course.
+
+Beta testers have early access to the course. Beta testers are not members of
+the course team or staff: they don't have information about "how it's supposed
+to work". They use their own computers and internet connections to view videos,
+follow links, and complete problems. They interact with the course exactly as
+students will, but see the course materials before other enrolled students do.
 
 * :ref:`Beta_Process`
 * :ref:`Qualities_Testers`
@@ -22,21 +30,33 @@ Beta testers have early access to the course. Beta testers are not members of th
 The Beta Testing Process
 ******************************************
 
-During a beta test, you gather information about the experience of taking your course in an effort to improve its quality. The phases of the beta testing process, and some questions that you may find useful to consider as you prepare for each phase, follow.
+During a beta test, you gather information about the experience of taking your
+course in an effort to improve its quality. The phases of the beta testing
+process, and some questions that you may find useful to consider as you prepare
+for each phase, follow.
 
-#. **Planning**: What are your objectives for the test? What is the schedule for testing? 
+#. **Planning**: What are your objectives for the test? What is the schedule for
+   testing?
 
-#. **Recruitment**: How many testers do you need? How much time do you expect testers to spend? When do you need them to complete their feedback? 
+#. **Recruitment**: How many testers do you need? How much time do you expect
+   testers to spend? When do you need them to complete their feedback?
 
-#. **Provide access to your course**: Can testers access your entire course immediately, or are its sections and subsections available at different times? How will that affect the schedule?
+#. **Provide access to your course**: Can testers access your entire course
+   immediately, or are its sections and subsections available at different
+   times? How will that affect the schedule?
 
-#. **Collect feedback**: How do you want testers to provide feedback? Who checks for feedback, and how often?  
+#. **Collect feedback**: How do you want testers to provide feedback? Who checks
+   for feedback, and how often?
 
-#. **Evaluate feedback**: How is feedback evaluated? Who decides what changes to make as a result, and on what schedule?
+#. **Evaluate feedback**: How is feedback evaluated? Who decides what changes to
+   make as a result, and on what schedule?
 
-#. **Conclusion**: How do you acknowledge the efforts of your testers? What do you share with them about the results of their efforts? 
+#. **Conclusion**: How do you acknowledge the efforts of your testers? What do
+   you share with them about the results of their efforts?
 
-There is no one answer to any of these questions. They are included here as background on the role that beta testing can play in the preparation of your course. 
+There is no one answer to any of these questions. They are included here as
+background on the role that beta testing can play in the preparation of your
+course.
 
 .. _Qualities_Testers:
 
@@ -44,7 +64,10 @@ There is no one answer to any of these questions. They are included here as back
 Qualities of Good Beta Testers
 ***************************************
 
-A beta test is valuable in part because it is unscripted. Your beta testers are not following a predetermined series of steps, or using a particular computer environment, when they access your course. When you recruit beta testers, however, you may find these skills and characteristics to be helpful.
+A beta test is valuable in part because it is unscripted. Your beta testers are
+not following a predetermined series of steps, or using a particular computer
+environment, when they access your course. When you recruit beta testers,
+however, you may find these skills and characteristics to be helpful.
 
 * Curiosity.
 
@@ -52,21 +75,35 @@ A beta test is valuable in part because it is unscripted. Your beta testers are
 
 * Solid communication skills for reporting problems to course staff. 
 
-Your beta testers should also have varying levels of knowledge about the course content:
+Your beta testers should also have varying levels of knowledge about the course
+content:
 
-* To recognize when material is wrong or missing, at least one tester should know the content well. 
+* To recognize when material is wrong or missing, at least one tester should
+  know the content well.
 
-* To identify material that is unclear, at least one tester should be less familiar with the content. 
+* To identify material that is unclear, at least one tester should be less
+  familiar with the content.
 
-Depending on the objectives you set for your beta test, you may want to consider recruiting testers who use assistive technologies, who have different native languages, or who have varying levels of familiarity with computer software.
+Depending on the objectives you set for your beta test, you may want to consider
+recruiting testers who use assistive technologies, who have different native
+languages, or who have varying levels of familiarity with computer software.
 
 =========================================
 Using Course Staff as Beta Testers 
 =========================================
 
-Course staff can provide valuable feedback about your course. However, they are typically stakeholders in the success of your course and have a significant amount of knowledge about it. As a result, they can be too close to the course to interact with it in the same way as students will. They can also be either reluctant to provide feedback, or overly zealous.
+Course staff can provide valuable feedback about your course. However, they are
+typically stakeholders in the success of your course and have a significant
+amount of knowledge about it. As a result, they can be too close to the course
+to interact with it in the same way as students will. They can also be either
+reluctant to provide feedback, or overly zealous.
 
-If you do want a staff member to be a beta tester, a different, second email address must be used for this additional role. The privileges of the course staff role override those of a beta tester, so a second registration on the site, activation, and enrollment in the course are necessary using this second email address. The staff member must log in using the second email address (with the beta tester role) in order to experience the course as a student.
+If you do want a staff member to be a beta tester, a different, second email
+address must be used for this additional role. The privileges of the course
+staff role override those of a beta tester, so a second registration on the
+site, activation, and enrollment in the course are necessary using this second
+email address. The staff member must log in using the second email address (with
+the beta tester role) in order to experience the course as a student.
 
 .. _What_Test:
 
@@ -96,11 +133,13 @@ How Beta Testers See Course Content
 
 To beta test a course, you: 
 
-* Define a number of days before section and subsection release days for testing to begin.
+* Define a number of days before section and subsection release days for testing
+  to begin.
 
 * Identify beta testers.
 
-Designated beta testers see course content before students can. Beta testers access courseware: 
+Designated beta testers see course content before students can. Beta testers
+access courseware:
 
 +-------------------------------------------+------+------+
 |                                           | Yes  |  No  |
@@ -118,19 +157,24 @@ Designated beta testers see course content before students can. Beta testers acc
 | Before a draft replaces a live unit       |      |   X  |
 +-------------------------------------------+------+------+
 
-The course team can continue to add content in Studio after the beta test begins. When new content is ready for testing, be sure to change the **Visibility** setting for any units that are Private to Public. See :ref:`Units` or :ref:`Publishing Your Course`.
+The course team can continue to add content in Studio after the beta test
+begins. When new content is ready for testing, be sure to change the
+**Visibility** setting for any units that are Private to Public. See
+:ref:`Units` or :ref:`Publishing Your Course`.
 
 ================================
 Define When the Beta Test Starts
 ================================
 
-To define the start of the beta test, you use Studio to specify a number of days before the **Release Day** of each section and subsection in your course. 
-
-#. In Studio, select **Settings** > **Advanced Settings**.
+To define the start of the beta test, you use Studio to specify a number of days
+before the release day that is defined for each section and subsection in your
+course.
 
-#. Scroll down to the ``days_early_for_beta`` **Policy Key**.
+#. In Studio, from the **Settings** menu select **Advanced Settings**.
 
-#. Set the **Policy Value** to a number of days before the **Release Day** for the section and subsection. 
+#. In the field for the **Days Early for Beta Users** policy key, enter the
+   number of days before each section and subsection release day for beta
+   testers to have access.
 
 #. Click **Save Changes**.
 
@@ -140,7 +184,8 @@ Example
 
 .. Is this example helpful? how can we assess whether it is frightening/confusing to course team, or helpful?
 
-Beta tester access to courseware for a course with ``days_early_for_beta`` = 20 and 2 sections:
+Beta tester access to courseware for a course with **Days Early for Beta Users**
+= 20 and 2 sections:
 
 +-------------------------------------------+------------------------------------------------+
 | Course Enrollment Date = 31 August        | 31 August; earlier if enrolled by course staff |
@@ -163,7 +208,11 @@ Beta tester access to courseware for a course with ``days_early_for_beta`` = 20
 | subsection 2, unit 3 Visibility = Private | No access                                      |
 +-------------------------------------------+------------------------------------------------+
 
-In this example, the beta testers cannot access all of the courseware when the beta test starts on 26 August: they can access section 1 but not section 2. You may want to provide a schedule of section availability to your testers so that they can plan their time appropriately. Future release dates do not display to the beta testers in the courseware.
+In this example, the beta testers cannot access all of the courseware when the
+beta test starts on 26 August: they can access section 1 but not section 2. You
+may want to provide a schedule of section availability to your testers so that
+they can plan their time appropriately. Future release dates do not display to
+the beta testers in the courseware.
 
 .. _Add_Testers:
 
@@ -184,8 +233,9 @@ When you add beta testers, note the following.
   cannot enroll themselves in your course. However, you can enroll the beta
   testers prior to the **Enrollment Start Date**.
 
-* If you add the beta testers after the defined start of the beta test, and 
-  they are enrolled in the course, they see your course on their dashboards when they log in.
+* If you add the beta testers after the defined start of the beta test, and they
+  are enrolled in the course, they see your course on their dashboards when they
+  log in.
 
 * If you add beta testers before the test starts, or if they are not enrolled,
   they do not see your course on their dashboards. You can enroll the beta
@@ -198,10 +248,10 @@ When you add beta testers, note the following.
 Add Multiple Beta Testers
 ================================
 
-If you have a number of beta testers that you want to add, you can use the "batch
-add" option to add them all at once, rather than individually. With this
-feature, you have options to enroll the beta testers in the course (before
-or after the **Enrollment Start Date**) and send an email message to notify the
+If you have a number of beta testers that you want to add, you can use the
+"batch add" option to add them all at once, rather than individually. With this
+feature, you have options to enroll the beta testers in the course (before or
+after the **Enrollment Start Date**) and send an email message to notify the
 beta testers that they have been added.
 
 To add multiple beta testers:
@@ -212,11 +262,17 @@ To add multiple beta testers:
 
 #. Click **Membership**. 
 
-#. In the **Batch Beta Tester Addition** section of the page, enter one or more addresses or usernames separated by commas or line feeds (the Enter key). You can also copy data from a CSV file of email addresses and paste it here. 
+#. In the **Batch Beta Tester Addition** section of the page, enter one or more
+   addresses or usernames separated by commas or line feeds (the Enter key). You
+   can also copy data from a CSV file of email addresses and paste it here.
  
-#. To enroll the beta testers in your course, leave **Auto Enroll** selected. If the beta test starts before the course **Enrollment Start Date**, testers cannot enroll themselves in your course. 
+#. To enroll the beta testers in your course, leave **Auto Enroll** selected. If
+   the beta test starts before the course **Enrollment Start Date**, testers
+   cannot enroll themselves in your course.
 
-#. To send an email message to the beta testers, leave **Notify users by email** selected. An example of the message that is sent to a beta tester who is not enrolled (or auto enrolled) in the course follows.
+#. To send an email message to the beta testers, leave **Notify users by email**
+   selected. An example of the message that is sent to a beta tester who is not
+   enrolled (or auto enrolled) in the course follows.
 
 .. image:: ../Images/Beta_tester_email.png
   :alt: "You have been invited to be a beta tester for <course name> at <URL>. Visit <link> to join the course and begin the beta test."
@@ -241,7 +297,8 @@ To add a single beta tester:
 
 #. Click **Membership**.
 
-#. In the **Administration List Management** section, use the drop-down list to select **Beta Testers**.
+#. In the **Administration List Management** section, use the drop-down list to
+   select **Beta Testers**.
 
 #. Under the list of users who currently have that role, enter an email address
    or username and click **Add Beta Tester**. 
@@ -259,11 +316,14 @@ user's email address.
 Issue Reporting During a Course
 *********************************
 
-Despite the efforts of the course team and the beta testers, additional problems, questions, and issues can occur while a course is running. 
+Despite the efforts of the course team and the beta testers, additional
+problems, questions, and issues can occur while a course is running.
 
-* Often, students report issues by asking questions in a discussion. Your discussion administration team can watch for posts that indicate problems.
+* Often, students report issues by asking questions in a discussion. Your
+  discussion administration team can watch for posts that indicate problems.
 
-* To let students know the best way to report problems, you can post information on the **Course Info** page or post it in a discussion. 
+* To let students know the best way to report problems, you can post information
+  on the **Course Info** page or post it in a discussion.
 
 .. per Mark 19 Feb 14: eventually we want to provide more guidance for students:  course issues > use discussions, platform issues > submit issue to edx.
 

docs/en_us/course_authors/source/running_course/course_data.rst

@@ -50,8 +50,9 @@ Studio, or derived from data that you define in Studio.
   Studio, this field is labeled **Course Name**. 
 
   This name can be changed in Studio (not recommended if your course is live):
-  select **Settings** > **Advanced Settings** and scroll down to the policy key
-  labeled **display_name**. This setting changes the **Course Display Name** in the LMS only. 
+  From the **Settings** menu select **Advanced Settings**. The value for the
+  **Course Display Name** policy key defines the course name that appears in the
+  LMS only.
 
   The illustration that follows shows the information collected by Studio for
   a new course side-by-side with the same information in the **Basic Course

docs/en_us/course_authors/source/running_course/course_student.rst

@@ -198,7 +198,7 @@ Track Student Activity
 To monitor student activity during your course, you can review the number of
 students who, each week, interacted with your course. To be considered active,
 students must visit pages, play videos, add to discussions, submit answers to
-problems, or complete other course activites. The active student count is
+problems, or complete other course activities. The active student count is
 updated weekly.
 
 To display the number of active students: