Sat Aug 20 12:06:50 EDT 2016

raeburn		Sat Aug 20 16:06:50 2016 EDT

  Modified files:              
    /loncom/html/adm/help/tex	Authoring_Hint_Tags.tex 
                             	Authoring_Internal_Tags.tex 
                             	Authoring_Output_Tags.tex 
                             	BridgeTask_Conditions.tex 
                             	BridgeTask_EditModeFinishing.tex 
                             	BridgeTask_EditModeIntroduction.tex 
                             	BridgeTask_EditModeQuestion.tex 
                             	BridgeTask_EditMode.tex 
                             	BridgeTask_EditModeVariable.tex 
                             	BridgeTask_Portfolio.tex 
                             	BridgeTask_SetupResource.tex 
                             	BridgeTask_XMLFinishing.tex 
                             	BridgeTask_XMLQuestions.tex 
                             	BridgeTask_XMLVariable.tex 
                             	Browsing_Resources.tex Bugzilla.tex 
                             	Change_Discussion_Display.tex 
                             	Change_Password.tex 
                             	Clicker_Registration.tex 
                             	Course_Automated_Enrollment.tex 
                             	Course_Create_Class_List.tex 
                             	Course_Manage_Group.tex 
                             	Course_Maximum_Collaborators.tex 
                             	Course_Prefs_Printouts.tex 
                             	Course_Problem_Weight.tex 
                             	Course_Request_Clone.tex 
                             	Course_Request_Crosslist.tex 
                             	Course_Request_LCSection.tex 
                             	Course_Request_Personnel.tex 
                             	Course_Request_Rolesection.tex 
                             	Authoring_Math_Editor.tex 
  Log:
  - Use LaTeX-style single and double quotes.
  
  
-------------- next part --------------
Index: loncom/html/adm/help/tex/Authoring_Hint_Tags.tex
diff -u loncom/html/adm/help/tex/Authoring_Hint_Tags.tex:1.4 loncom/html/adm/help/tex/Authoring_Hint_Tags.tex:1.5

--- loncom/html/adm/help/tex/Authoring_Hint_Tags.tex:1.4	Mon Jan 10 00:06:25 2011
+++ loncom/html/adm/help/tex/Authoring_Hint_Tags.tex	Sat Aug 20 16:06:50 2016
@@ -27,6 +27,6 @@
 \textbf{name} should be set to the value of which \textbf{hintpart}
 will be shown, and the attribute \textbf{answer} should be at least a two element
 list: first the type (\textbf{foil} or \textbf{concept}) and then
-either the foil name(s) or the concept string(s), e.g., ``('foil','greaterthan','equal')'' if the condition should be triggered by the foils named ``greaterthan'' or ``equal.''
+either the foil name(s) or the concept string(s), e.g., ``(`foil',`greaterthan',`equal')'' if the condition should be triggered by the foils named ``greaterthan'' or ``equal.''
 \item \textbf{customhint}\index{customhint}: The required attribute \textbf{name} should be set to the value of which \textbf{hintpart} will be shown.  Define the hint condition within an \textbf{answer} block inside of the \textbf{customhint} block.  The condition is defined like how an answer is defined in \textbf{customresponse} where you need to return EXACT\_ANS to indicate when customhint criteria are met. 
 \end{itemize}
Index: loncom/html/adm/help/tex/Authoring_Internal_Tags.tex
diff -u loncom/html/adm/help/tex/Authoring_Internal_Tags.tex:1.2 loncom/html/adm/help/tex/Authoring_Internal_Tags.tex:1.3
--- loncom/html/adm/help/tex/Authoring_Internal_Tags.tex:1.2	Thu Feb 24 22:26:25 2005
+++ loncom/html/adm/help/tex/Authoring_Internal_Tags.tex	Sat Aug 20 16:06:50 2016
@@ -10,14 +10,14 @@
 \item \textbf{name}\index{name}: This is the name of the group. A hash
 with this name will be generated holding the mappings for later use
 in the problem. For each location a value will be set for which label
-is there (EX. \$hash\{'1'\}=''TEXT-2''). For locations with values,
-the hash will contain 2 items, a location to value mapping (\$hash\{'value\_1'\}=10),
-and a label to value mapping (\$hash\{'labelvalue\_2'\}=10). For all
+is there (EX. \$hash\{`1'\}=``TEXT-2''). For locations with values,
+the hash will contain 2 items, a location to value mapping (\$hash\{`value\_1'\}=10),
+and a label to value mapping (\$hash\{`labelvalue\_2'\}=10). For all
 image style of labels there will also be a label description to label
-URL mapping (\$hash\{'image\_2'\}=IMG-URL). The entry \textbf{numlocations}
+URL mapping (\$hash\{`image\_2'\}=IMG-URL). The entry \textbf{numlocations}
 will also be set to the total number of locations that exist (Note: locations and labels start counting from one.) 
 \item \textbf{type}\index{type}: the type of labels in this group, either
-'\textbf{image}' or '\textbf{text}'
+`\textbf{image}' or `\textbf{text}'
 \item \textbf{location}\index{location}: declares a location on the image
 that a label should appear at. Possible attributes are:
 
Index: loncom/html/adm/help/tex/Authoring_Output_Tags.tex
diff -u loncom/html/adm/help/tex/Authoring_Output_Tags.tex:1.20 loncom/html/adm/help/tex/Authoring_Output_Tags.tex:1.21
--- loncom/html/adm/help/tex/Authoring_Output_Tags.tex:1.20	Fri May  6 21:37:06 2016
+++ loncom/html/adm/help/tex/Authoring_Output_Tags.tex	Sat Aug 20 16:06:50 2016
@@ -135,8 +135,8 @@
 \begin{itemize}
 \item \textbf{heading} heading text of the box, by default no heading
 \item \textbf{headerbg} background color of the header, by default white
-\item \textbf{showtext} the text that appears to make the box visible, by default the translation of 'show'
-\item \textbf{hidetext} the text that appears to hide the box again, by default the translation of 'hide'
+\item \textbf{showtext} the text that appears to make the box visible, by default the translation of `show'
+\item \textbf{hidetext} the text that appears to hide the box again, by default the translation of `hide'
 \end{itemize}
 
 When printing, the included text will be rendered in a visible box.
Index: loncom/html/adm/help/tex/BridgeTask_Conditions.tex
diff -u loncom/html/adm/help/tex/BridgeTask_Conditions.tex:1.2 loncom/html/adm/help/tex/BridgeTask_Conditions.tex:1.3
--- loncom/html/adm/help/tex/BridgeTask_Conditions.tex:1.2	Tue Aug 20 15:35:30 2013
+++ loncom/html/adm/help/tex/BridgeTask_Conditions.tex	Sat Aug 20 16:06:50 2016
@@ -6,13 +6,13 @@
 
 The author must create various conditionals to determine which resources to show. The easiest way to do this is by using advanced edit. The advanced edit visualizes the various conditions and resources. This interface needs popups, so make sure  popups are enabled in the browser.
 
-In the main starting view of the advanced edit, there are two squares, marked start and end respectively. Start by creating a link between the start square and the end square. To do this click on the start square (on the row under the text start), select "Link Resource", then click on the end square. A link is now created between the start and the end boxes.
+In the main starting view of the advanced edit, there are two squares, marked start and end respectively. Start by creating a link between the start square and the end square. To do this click on the start square (on the row under the text start), select ``Link Resource'', then click on the end square. A link is now created between the start and the end boxes.
 
 Once a link is created the author adds resources and conditions. Click on the link and then choose insert resource into link. This allows the placement of a resource such as a bridge task into the sequence. Once the resource is placed into the link, the author should create a mapalias. To do this, select the resource, then click on set parameters, and change the value of Custom Parameter to an alias. 
 
 Under each square is an area of the same color as the square, these areas can be used to create conditionals to get to the next resource to the sequence. This document only discusses using conditionals to block access to the next resource (including Bridge Tasks).
 
-Add conditionals by clicking on the area just under the squares. A popup window will appear with a condition box and some options. The condition box allows the author to enter a variety of different conditions. To block access to the next resource, select the second option "Blocking this link if false". 
+Add conditionals by clicking on the area just under the squares. A popup window will appear with a condition box and some options. The condition box allows the author to enter a variety of different conditions. To block access to the next resource, select the second option ``Blocking this link if false''. 
 
 The conditions used will be :
 \begin{verbatim}
Index: loncom/html/adm/help/tex/BridgeTask_EditModeFinishing.tex
diff -u loncom/html/adm/help/tex/BridgeTask_EditModeFinishing.tex:1.2 loncom/html/adm/help/tex/BridgeTask_EditModeFinishing.tex:1.3
--- loncom/html/adm/help/tex/BridgeTask_EditModeFinishing.tex:1.2	Thu Apr 11 14:59:44 2013
+++ loncom/html/adm/help/tex/BridgeTask_EditModeFinishing.tex	Sat Aug 20 16:06:50 2016
@@ -1,12 +1,12 @@
 \label{BridgeTask_EditModeFinishing}
 
-Once the construction is complete, click on the "Submit Changes and View" button. Click on list to list the current author's directory. The author should now publish the file so that the domain coordinator will be able to use the file. To do this select publish (or re-publish) in the select action combo box next to the filename.
+Once the construction is complete, click on the ``Submit Changes and View'' button. Click on list to list the current author's directory. The author should now publish the file so that the domain coordinator will be able to use the file. To do this select publish (or re-publish) in the select action combo box next to the filename.
 
 The LON CAPA interface allows you to view the bridge task from different point of views. You can see it from the student's view, the grader view, or the student's view after feedback. 
 \begin{enumerate}
 \item From the list of files authored, click on the bridge task that has just been created/edited. 
-\item A pull-down menu with the label "Problem Status" is located just above the question. select "Answerable" to see the original view, "Criteria Grading"  to see a grader view, and "Show Feedback" to see the feedback view.
+\item A pull-down menu with the label ``Problem Status'' is located just above the question. select ``Answerable'' to see the original view, ``Criteria Grading''  to see a grader view, and ``Show Feedback'' to see the feedback view.
 \item To see the feedback view properly, you must have graded the student with the grader view. 
-\item Once you have graded using the feedback view however, the answerable view will be similar to the feedback view. To reset the view a "Reset Submissions" button is provided.
+\item Once you have graded using the feedback view however, the answerable view will be similar to the feedback view. To reset the view a ``Reset Submissions'' button is provided.
 \end{enumerate}
 
Index: loncom/html/adm/help/tex/BridgeTask_EditModeIntroduction.tex
diff -u loncom/html/adm/help/tex/BridgeTask_EditModeIntroduction.tex:1.1 loncom/html/adm/help/tex/BridgeTask_EditModeIntroduction.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_EditModeIntroduction.tex:1.1	Wed May 30 15:35:14 2007
+++ loncom/html/adm/help/tex/BridgeTask_EditModeIntroduction.tex	Sat Aug 20 16:06:50 2016
@@ -4,7 +4,7 @@
 
 To insert these sections:
 \begin{enumerate}
-\item Select "Introductory Information" or "Closing Information" in the insert pull-down menu and press the submit button. 
+\item Select ``Introductory Information'' or ``Closing Information'' in the insert pull-down menu and press the submit button. 
 \item A new section appears with a text box inside it. You may enter any text inside the text box and the text may be formatted with HTML tags. Everything inside the text box will be shown to the students as introductory or closing text.
 \end{enumerate}
 
Index: loncom/html/adm/help/tex/BridgeTask_EditModeQuestion.tex
diff -u loncom/html/adm/help/tex/BridgeTask_EditModeQuestion.tex:1.1 loncom/html/adm/help/tex/BridgeTask_EditModeQuestion.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_EditModeQuestion.tex:1.1	Wed May 30 15:35:14 2007
+++ loncom/html/adm/help/tex/BridgeTask_EditModeQuestion.tex	Sat Aug 20 16:06:50 2016
@@ -10,10 +10,10 @@
 
 Figure \ref{BTEdit_Question} shows a screenshot of the question creation page. To create a question:
 \begin{enumerate}
-\item Select "Question" in the main insert pull-down (circled as 1). 
+\item Select ``Question'' in the main insert pull-down (circled as 1). 
 \item Press the submit changes and edit button. 
 \item In this question create a unique id which can be any kind of text (in circle 3). 
-\item Set whether a student must pass this question by setting the value of  "Passing is Mandatory" to "yes" (circle 4) or whether this question is optional by setting the value to "no". 
+\item Set whether a student must pass this question by setting the value of  ``Passing is Mandatory'' to ``yes'' (circle 4) or whether this question is optional by setting the value to ``no''. 
 \item Set the number of optional subquestions/criteria that the students must get correct in order to pass this question. You can also wait until later to fill this in.
 \item Create the question information by choosing Question information in the insert pull-down (circled as 2) and pressing the submit button. 
 \item A text box should appear (circle 6) and you can insert any text in this text box. Anything that is typed in this text box will appear to the student as part of the question. HTML tags can also be used to format the text in the text box. Subquestions can be added by inserting a new question (circle 2).
@@ -27,11 +27,11 @@
 
 To add a criteria (see Figure \ref{BTEdit_Criteria}):
 \begin{enumerate}
-\item Instead of choosing "Question" in the insert pull down, select "Question Criteria" (circled as 1). Pressing the submit button will bring up the Question criteria as well as the criteria information where you can write the criteria (Circled 3). The criteria is shown to the student only when the student is reading his/her feedback. The criteria is also shown to the grader in order for the grader to be able to grade the student submission.
+\item Instead of choosing ``Question'' in the insert pull down, select ``Question Criteria'' (circled as 1). Pressing the submit button will bring up the Question criteria as well as the criteria information where you can write the criteria (Circled 3). The criteria is shown to the student only when the student is reading his/her feedback. The criteria is also shown to the grader in order for the grader to be able to grade the student submission.
 \item In the criteria block, first create a unique id for this criteria (any text) (circle 1). 
 \item Specify whether a criteria is mandatory or not, this is set in the Passing is mandatory pull-down similar to that of the question (circle 2). 
 \item Text in the text block (circle 4) is shown as the criteria. The text can be formatted with HTML. 
-\item You can also insert a grader note which will only be shown to the user. To do this select "Text to display to grader" in the insert pull down menu of circle number 3.
+\item You can also insert a grader note which will only be shown to the user. To do this select ``Text to display to grader'' in the insert pull down menu of circle number 3.
 \end{enumerate}
 
  
Index: loncom/html/adm/help/tex/BridgeTask_EditMode.tex
diff -u loncom/html/adm/help/tex/BridgeTask_EditMode.tex:1.2 loncom/html/adm/help/tex/BridgeTask_EditMode.tex:1.3
--- loncom/html/adm/help/tex/BridgeTask_EditMode.tex:1.2	Thu Apr 11 14:59:44 2013
+++ loncom/html/adm/help/tex/BridgeTask_EditMode.tex	Sat Aug 20 16:06:50 2016
@@ -2,16 +2,16 @@
 
 Another way of creating Bridge Task is via the edit mode. The edit mode allows authors to create resources (including Bridge Tasks) online. The basic idea of the this editor is the author inserts and deletes different section types into the file to build the bridge task.
 
-If a task file has already been created, click on the filename followed by the "Edit" button to open the file in the colorful editor. 
+If a task file has already been created, click on the filename followed by the ``Edit'' button to open the file in the colorful editor. 
 
 If a task file needs to be created:
 \begin{enumerate}
-\item Enter the filename in the area "Create a new directory or LON-CAPA document" with the combo box at the left of this set to "New File". The filename must have a .task extension.
-\item At the second screen, press continue to create a new task. At the third screen, select the blank task template and press the "Create task" button to create this blank task. 
-\item To go into the the edit mode, press the "Edit" Button.
+\item Enter the filename in the area ``Create a new directory or LON-CAPA document'' with the combo box at the left of this set to ``New File'' The filename must have a .task extension.
+\item At the second screen, press continue to create a new task. At the third screen, select the blank task template and press the ``Create task'' button to create this blank task. 
+\item To go into the the edit mode, press the ``Edit'' Button.
 \end{enumerate}
 
-The edit mode allows you to insert appropriate sections of a document at certain predetermined places. For example, in a bridge task document, you can insert a question section, a criteria section, and an introductory section. To insert a section, find a drop down box with the label "Insert", and select the section to insert. Then click on the "Submit Changes and Edit" button. The section you selected will be inserted in place of the pull down menu. 
+The edit mode allows you to insert appropriate sections of a document at certain predetermined places. For example, in a bridge task document, you can insert a question section, a criteria section, and an introductory section. To insert a section, find a drop down box with the label ``Insert'', and select the section to insert. Then click on the ``Submit Changes and Edit'' button. The section you selected will be inserted in place of the pull down menu. 
 
 Additional insert pull-downs will show up allowing you to insert sections before, inside, and after other sections. The choices on the pull down menu may differ depending on the location of the insert pull-down. For example, the insert pull down inside a question section contains question information; this option is not available anywhere else.
 
Index: loncom/html/adm/help/tex/BridgeTask_EditModeVariable.tex
diff -u loncom/html/adm/help/tex/BridgeTask_EditModeVariable.tex:1.1 loncom/html/adm/help/tex/BridgeTask_EditModeVariable.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_EditModeVariable.tex:1.1	Wed May 30 15:35:14 2007
+++ loncom/html/adm/help/tex/BridgeTask_EditModeVariable.tex	Sat Aug 20 16:06:50 2016
@@ -10,14 +10,14 @@
 
 To create a variable:
 \begin{enumerate}
-\item Choose "Setup ..." in the insert pull-down menu (circled 1 in figure). \item Press the Submit Changes and Edit just above the work space. 
-\item A new box should appear with the label "Setup ...". In this box, fill out the id box (circled 3) with any text that is unique to unique to the document. This id is the name of the variable and will be used when creating the values for the variable.
-\item The setup box has an insert pull-down menu next to the label (circled 2), select "Specific Question Instance" in this pull down menu, then again press the Submit Changes and Edit button. 
-\item This creates one single instance of a set of possible values. For each instance created, a new "Specific Question Instance" must be created. 
-\item Right now a box should appear inside the "Setup... " box with the label "Specific Question Instance". Insert a unique id for that instance which can be any unique text (circled 4).  This id is the instance name and is used as one of the property of the variable.
-\item In the question instance block, select "Information for the Instance" in the insert pull down (circled 5). Again press submit button. 
+\item Choose ``Setup ...'' in the insert pull-down menu (circled 1 in figure). \item Press the Submit Changes and Edit just above the work space. 
+\item A new box should appear with the label ``Setup ...''. In this box, fill out the id box (circled 3) with any text that is unique to unique to the document. This id is the name of the variable and will be used when creating the values for the variable.
+\item The setup box has an insert pull-down menu next to the label (circled 2), select ``Specific Question Instance'' in this pull down menu, then again press the Submit Changes and Edit button. 
+\item This creates one single instance of a set of possible values. For each instance created, a new ``Specific Question Instance'' must be created. 
+\item Right now a box should appear inside the ``Setup... '' box with the label ``Specific Question Instance''. Insert a unique id for that instance which can be any unique text (circled 4).  This id is the instance name and is used as one of the property of the variable.
+\item In the question instance block, select ``Information for the Instance'' in the insert pull down (circled 5). Again press submit button. 
 \item Add a new script (circled 6) in the insert pull down. A new text block should appear. 
-\item In this text box, a perl script will be created (circled 7). A set of parameters for this variable is added. The syntax to set the parameter of a variable is '\$variableName \{fieldname\} = "fieldValue"'. The variable name is taken from the id field of the Setup block, thefield name is the name of the parameter the author sets, and the fieldValue is simply the value of the field. The first parameter that must be set is the instance field, with the value being an identifier of the instance (which is the id of the specific question instance block). 
+\item In this text box, a perl script will be created (circled 7). A set of parameters for this variable is added. The syntax to set the parameter of a variable is `\$variableName \{fieldname\} = ``fieldValue'''. The variable name is taken from the id field of the Setup block, thefield name is the name of the parameter the author sets, and the fieldValue is simply the value of the field. The first parameter that must be set is the instance field, with the value being an identifier of the instance (which is the id of the specific question instance block). 
 \end{enumerate}
 
 The example below shows two instances of this script for the variable entitySubject with two instances, 'instanceHarry' and 'instanceBetty'.
@@ -36,7 +36,7 @@
 	$entitySubject{place} = "park";
 \end{verbatim}	
 
-The example above describes a variable question. It has two different possible values for the entity "subject", Harry and zoo or Betty and park. Variables can be placed inside the questions by using the variable name and field name. 
+The example above describes a variable question. It has two different possible values for the entity ``subject'', Harry and zoo or Betty and park. Variables can be placed inside the questions by using the variable name and field name. 
 The example of the usage of this variable inside the question is this text:
 
 This is a test question. \$entitySubject\{personname\}
Index: loncom/html/adm/help/tex/BridgeTask_Portfolio.tex
diff -u loncom/html/adm/help/tex/BridgeTask_Portfolio.tex:1.1 loncom/html/adm/help/tex/BridgeTask_Portfolio.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_Portfolio.tex:1.1	Thu May 10 15:14:02 2007
+++ loncom/html/adm/help/tex/BridgeTask_Portfolio.tex	Sat Aug 20 16:06:50 2016
@@ -9,9 +9,9 @@
 \item Submit the files
 \end{enumerate}
 
-At the end of every bridge task there will be a box to submit files in the portfolio for grading. When the student click on the link "select portfolio files", a new window is opened showing the content of the student's portfolio. The student can create directories in the portfolio and upload files using the upload file buttons.
+At the end of every bridge task there will be a box to submit files in the portfolio for grading. When the student click on the link ``select portfolio files'', a new window is opened showing the content of the student's portfolio. The student can create directories in the portfolio and upload files using the upload file buttons.
 
-Once the files that are needed are uploaded, the student select (by checking the checkbox next to the filenames) of all files that he needs to submit to the instructor. Once all files needed are checked off, the student needs to press the "select checked files and close window" button. 
+Once the files that are needed are uploaded, the student select (by checking the checkbox next to the filenames) of all files that he needs to submit to the instructor. Once all files needed are checked off, the student needs to press the ``select checked files and close window'' button. 
 
 By pressing the close window button, the student's portfolio window should close, and the student should see his or her Bridge Task Page. The text field in the upload files into portfolio should contain the list of names. The student must then press 'submit answer' to submit the answer to be graded. 
 
Index: loncom/html/adm/help/tex/BridgeTask_SetupResource.tex
diff -u loncom/html/adm/help/tex/BridgeTask_SetupResource.tex:1.1 loncom/html/adm/help/tex/BridgeTask_SetupResource.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_SetupResource.tex:1.1	Thu May 10 15:14:02 2007
+++ loncom/html/adm/help/tex/BridgeTask_SetupResource.tex	Sat Aug 20 16:06:50 2016
@@ -3,7 +3,7 @@
 The first step in making bridge tasks available to students is to include it in the document space. To do this:
 \begin{enumerate}
 \item Enter the course coordinator space for the course
-\item Go to "Course Documents" and click on import. This page gives the list of files that you have created. 
+\item Go to ``Course Documents'' and click on import. This page gives the list of files that you have created. 
 \item Select the bridge task and press import to insert the file to the list of documents. 
 \item After importing the document, you must re-initialize the course.
 \end{enumerate}
@@ -16,13 +16,13 @@
 
 If you are using slots:
 \begin{enumerate}
-\item Change the "Use slot based access controls" parameter to "Yes".
-\item Change the "Slots of availability" parameter for the course in for resource column to the name of the slot that you created. You may need to change the input type (the combo box at the top of the popup) to 'String Value' instead of 'default'.
+\item Change the ``Use slot based access controls'' parameter to ``Yes''.
+\item Change the ``Slots of availability'' parameter for the course in for resource column to the name of the slot that you created. You may need to change the input type (the combo box at the top of the popup) to 'String Value' instead of 'default'.
 \end{enumerate}
 
 If you are not using slots:
 \begin{enumerate}
-\item Change the "Use slot based access controls" parameter to "no" by clicking on the * in the for resource column
+\item Change the ``Use slot based access controls'' parameter to ``no'' by clicking on the * in the for resource column
 \end{enumerate}
 
 The bridge task should now be available to students. To see the BT in the student view, switch to a student role in your course.  Navigate contents and click on the resource. 
Index: loncom/html/adm/help/tex/BridgeTask_XMLFinishing.tex
diff -u loncom/html/adm/help/tex/BridgeTask_XMLFinishing.tex:1.3 loncom/html/adm/help/tex/BridgeTask_XMLFinishing.tex:1.4
--- loncom/html/adm/help/tex/BridgeTask_XMLFinishing.tex:1.3	Tue Aug 20 15:35:30 2013
+++ loncom/html/adm/help/tex/BridgeTask_XMLFinishing.tex	Sat Aug 20 16:06:50 2016
@@ -4,8 +4,8 @@
 
 The LON CAPA interface allows you to view the bridge task from different point of views. You can see it from the student's view, the grader view, or the student's view after feedback:
 \begin{enumerate}
-\item From the list of files authored, click on the bridge task that has just been created/edited. A pull-down menu with the label "Problem Status" is located just above the question
-\item Select "Answerable" to see the original view, "Criteria Grading"  to see a grader view, and "Show Feedback" to see the feedback view .To see the feedback view properly, you must have graded the student with the grader view. Once you have graded using the feedback view however, the answerable view will be similar to the feedback view. 
-\item To reset the view a "Reset Submissions" button is provided.
+\item From the list of files authored, click on the bridge task that has just been created/edited. A pull-down menu with the label ``Problem Status'' is located just above the question
+\item Select ``Answerable'' to see the original view, ``Criteria Grading''  to see a grader view, and ``Show Feedback'' to see the feedback view .To see the feedback view properly, you must have graded the student with the grader view. Once you have graded using the feedback view however, the answerable view will be similar to the feedback view. 
+\item To reset the view a ``Reset Submissions'' button is provided.
 \end{enumerate}
 
Index: loncom/html/adm/help/tex/BridgeTask_XMLQuestions.tex
diff -u loncom/html/adm/help/tex/BridgeTask_XMLQuestions.tex:1.1 loncom/html/adm/help/tex/BridgeTask_XMLQuestions.tex:1.2
--- loncom/html/adm/help/tex/BridgeTask_XMLQuestions.tex:1.1	Wed May 30 15:35:14 2007
+++ loncom/html/adm/help/tex/BridgeTask_XMLQuestions.tex	Sat Aug 20 16:06:50 2016
@@ -2,11 +2,11 @@
 
 The task description should be divided into questions. Questions can also be divided into sub-questions. A question or sub-question must have one or more criteria that are the scoring rubrics used to evaluate that question.  A task may also have a criteria. Graders use these criteria to evaluate student work  Both questions and criteria are interspersed within the task description, placed where students see them when reviewing their graded bridge task.
 
-Questions are created by using the Question tag. Each question must have a unique id attribute which identifies the question, the value of the id attribute is any text that is unique in the document. Each question must also have the Mandatory attribute which can be set to "Y" if the question is mandatory or "N" otherwise. Finally the question may also have a OptionalRequired attribute, which determines how many optional criteria students must pass to pass the question. 
+Questions are created by using the Question tag. Each question must have a unique id attribute which identifies the question, the value of the id attribute is any text that is unique in the document. Each question must also have the Mandatory attribute which can be set to ``Y'' if the question is mandatory or ``N'' otherwise. Finally the question may also have a OptionalRequired attribute, which determines how many optional criteria students must pass to pass the question. 
 
 The question element will have the actual text of the question. The questions are created inside the QuestionText element. The question descriptions are placed inside the file by simply typing the text. The text can be marked up to have various formatting. The mark up language used is simple HTML.
 
-Criteria are created using the Criteria tag. The attributes for the criteria tag are similar to the attributes for the questions tag. Criteria tags have id attributes as well as Mandatory attributes. Like for the question tag, the value of the id attribute is any text that is unique in the document, and the Mandatory attribute (values "Y" or "N") determines whether the criteria is mandatory or not. Criteria tags do not have OptionalRequired attributes. The criteria description is created inside the CriteriaText element and can be formatted the same way as the formatting of the questions (using HTML).
+Criteria are created using the Criteria tag. The attributes for the criteria tag are similar to the attributes for the questions tag. Criteria tags have id attributes as well as Mandatory attributes. Like for the question tag, the value of the id attribute is any text that is unique in the document, and the Mandatory attribute (values ``Y'' or ``N'') determines whether the criteria is mandatory or not. Criteria tags do not have OptionalRequired attributes. The criteria description is created inside the CriteriaText element and can be formatted the same way as the formatting of the questions (using HTML).
 
 The following is an example of a question and criteria element. Question elements are placed inside the task element or inside other question elements. Text between $<!--$and $-->$ are comments and should not be typed into the editor. 
 
@@ -54,29 +54,29 @@
 
 The question that the students will see is:
 
-"Some test explanation\\
+``Some test explanation\\
 The actual test question\\
-Instructions to the student on submitting files\\"
+Instructions to the student on submitting files\\''
 
 Any text inside a QuestionText element (lines 2, 14) and not inside a criteria element will be shown to the users. This example has one question, and one optional sub-question. The question element is given in line 1, the id of the question being 'q.testquestion', it is a mandatory question (Mandatory='Y') and it requires that 1 optional question/criteria be passed (OptionalRequired='1'). The sub-question is given in line 13, named 'q.question1', is not mandatory and has no optional questions or criteria that is required to be correctly answered.
 
 The example above shows a code for the creation of criteria. There are 2 criteria in the above question (line 4 and 16). Each criteria has a name (criteria.question1 and criteria.overall.handin) which are both mandatory (the attribute Mandatory is set to 'Y'). The text of the criteria is given inside the CriteriaText element inside each CriteriaElement. The student will never see the criteria when the student is taking the test. The grader will see this on his/her screen:
 
-"Criteria text 1. Grader Note: This part cannot be seen by the students but is used to give additional info to the grader to help evaluating the criteria.\\ 
+``Criteria text 1. Grader Note: This part cannot be seen by the students but is used to give additional info to the grader to help evaluating the criteria.\\ 
  Pass 		 Fail\\
 Comment:\\ \\ \\
 Criteria text 2.\\
  Pass 		Fail \\
-Comment:\\ \\ \\"
+Comment:\\ \\ \\''
 
 When the bridge task is graded the student will see both the questions and the criteria in his space. Anything inside the GraderNote element (line 7) is not shown to the student.
 
-"Some test explanation\\
+``Some test explanation\\
 Criteria text 1\\
 Pass\\
 The actual test question\\
 Criteria text 2.\\
 Pass\\
 Instructions to the student on submitting files\\
-"
+''
 
Index: loncom/html/adm/help/tex/BridgeTask_XMLVariable.tex
diff -u loncom/html/adm/help/tex/BridgeTask_XMLVariable.tex:1.2 loncom/html/adm/help/tex/BridgeTask_XMLVariable.tex:1.3
--- loncom/html/adm/help/tex/BridgeTask_XMLVariable.tex:1.2	Wed May 30 15:35:14 2007
+++ loncom/html/adm/help/tex/BridgeTask_XMLVariable.tex	Sat Aug 20 16:06:50 2016
@@ -4,7 +4,7 @@
 
 All variables are placed inside a Setup element. Each setup element has an id attribute which contains the name of the variable. The possible instances or values of those variables are placed inside the setup element inside an Instance tag. Each Instance element has two mandatory attributes, the OptionalRequired attribute which should be set to 0, and the unique id of that instance. The value of the id attribute can be any text as long as it is unique throughout the document.
 
-The actual data of the instance is placed inside InstanceText tags. Currently the instance data is created with a loncapa/perl script. In this script the parameters of the variable are set. The syntax to set the parameter of a variable is '\$variableName \{fieldname\} = "fieldValues"'. The variable name is taken from the attribute id from the Setup element, the field name is the name of the parameter the author sets, and the fieldValue is simply the value of the field. The first parameter that must be set is the instance field, with the value being an identifier of the instance.
+The actual data of the instance is placed inside InstanceText tags. Currently the instance data is created with a loncapa/perl script. In this script the parameters of the variable are set. The syntax to set the parameter of a variable is '\$variableName \{fieldname\} = ``fieldValues'''. The variable name is taken from the attribute id from the Setup element, the field name is the name of the parameter the author sets, and the fieldValue is simply the value of the field. The first parameter that must be set is the instance field, with the value being an identifier of the instance.
 
 The example below shows a portion of the bridge task XML file. This portion should be placed inside the task element :Lines between $<!--$ and $-->$ or $/*$ and $*/$ are comments and should not be typed into the editor. 
 
@@ -47,10 +47,10 @@
 </Setup>
 \end{verbatim}
 
-The example above describes a variable question. It has two different possible values for the entity "subject", Harry and zoo or Betty and park. Variables can be placed inside the questions by using the variable name and field name. 
-The first line $<$Setup id="entitySubject"$>$ creates a variable named entitySubject (based on the id attribute of this line).
+The example above describes a variable question. It has two different possible values for the entity ``subject'', Harry and zoo or Betty and park. Variables can be placed inside the questions by using the variable name and field name. 
+The first line $<$Setup id=``entitySubject''$>$ creates a variable named entitySubject (based on the id attribute of this line).
 
-The first instance of this variable is shown from lines 2 to 10. Line two $<$Instance OptionalRequired="0" id="instanceHarry"$>$ marks the beginning of the instance element named instanceHarry (based on the id attribute). The OptionalRequired is given a value of 0. Lines 3-9 determine the actual value of this variable. Lines 3 and 4 must be typed as shown. Lines 5-7 define the instance properties, which must be of the form \$ $<$variable\_name$>$ \{$<$property\_name$>$ \} = $<$value$>$. The first line of the property must be the instance property (see line 5 of example), with the value being the id of the instance. Other lines (6-7) can be used for any attributes you wish to define. The closing $<$/script$>$, $<$/InstanceText$>$ and $<$/Instance$>$ tags must be typed as shown.
+The first instance of this variable is shown from lines 2 to 10. Line two $<$Instance OptionalRequired=``0'' id=``instanceHarry''$>$ marks the beginning of the instance element named instanceHarry (based on the id attribute). The OptionalRequired is given a value of 0. Lines 3-9 determine the actual value of this variable. Lines 3 and 4 must be typed as shown. Lines 5-7 define the instance properties, which must be of the form \$ $<$variable\_name$>$ \{$<$property\_name$>$ \} = $<$value$>$. The first line of the property must be the instance property (see line 5 of example), with the value being the id of the instance. Other lines (6-7) can be used for any attributes you wish to define. The closing $<$/script$>$, $<$/InstanceText$>$ and $<$/Instance$>$ tags must be typed as shown.
 
 Line 12-21 shows the second instance with the same rules as the first instance. Line 23 $<$/Setup$>$ gives the closing Setup tag which must be as shown..
 The example of the usage of this variable inside the question is this text: 
Index: loncom/html/adm/help/tex/Browsing_Resources.tex
diff -u loncom/html/adm/help/tex/Browsing_Resources.tex:1.4 loncom/html/adm/help/tex/Browsing_Resources.tex:1.5
--- loncom/html/adm/help/tex/Browsing_Resources.tex:1.4	Thu Jul 25 03:29:50 2013
+++ loncom/html/adm/help/tex/Browsing_Resources.tex	Sat Aug 20 16:06:50 2016
@@ -8,8 +8,8 @@
 into your course documents except that you only have permissions to
 view the resources, not select them for importing. Note that at the
 top of the Resource Space Screen there are some options.
-For example, selecting ''Title'' will display the titles from
-the metadata from each problem. Selecting ''All versions'' will
+For example, selecting ``Title'' will display the titles from
+the metadata from each problem. Selecting ``All versions'' will
 show all versions of the resource which are saved whenever
 the resource was republished.
 
Index: loncom/html/adm/help/tex/Bugzilla.tex
diff -u loncom/html/adm/help/tex/Bugzilla.tex:1.14 loncom/html/adm/help/tex/Bugzilla.tex:1.15
--- loncom/html/adm/help/tex/Bugzilla.tex:1.14	Fri Apr 25 16:02:41 2014
+++ loncom/html/adm/help/tex/Bugzilla.tex	Sat Aug 20 16:06:50 2016
@@ -17,12 +17,12 @@
 You will be directed to send an e-mail to the LON-CAPA Helpdesk to request creation of a Bugzilla 
 account. 
 Once you have an open account, please search existing cases for related content before
-submitting a new case. Select ``LON-CAPA" in the ``Product" category when searching. 
+submitting a new case. Select ``LON-CAPA'' in the ``Product'' category when searching. 
 Hold the Ctrl key while clicking multiple items. 
-The ``Component", ``Version", and ``Target" can be left
+The ``Component'', ``Version'', and ``Target'' can be left
 undesignated. If you find a related bug, you can add comments instead of reporting a new bug. If
-you find a bug that you are interested in following, you can add your e-mail to the ``Add cc:" box
-and click ``Commit".
+you find a bug that you are interested in following, you can add your e-mail to the ``Add cc:'' box
+and click ``Commit''.
 
 You can report a bug or request an enhancement as follows:
 
@@ -34,8 +34,8 @@
 \item At the login screen, enter your e-mail address and password.
 \item Click the {[}Login{]} button.
 \item Select the LON-CAPA Version, Component, Platform and Operating System (as much as known).
-\item Enter a summary in the ``Summary" text box.
-\item Enter a description in the ``Description" text box.
+\item Enter a summary in the ``Summary'' text box.
+\item Enter a description in the ``Description'' text box.
 \item Click the {[}Commit{]} button.
 
 \end{enumerate}
Index: loncom/html/adm/help/tex/Change_Discussion_Display.tex
diff -u loncom/html/adm/help/tex/Change_Discussion_Display.tex:1.5 loncom/html/adm/help/tex/Change_Discussion_Display.tex:1.6
--- loncom/html/adm/help/tex/Change_Discussion_Display.tex:1.5	Mon Sep 23 17:35:02 2013
+++ loncom/html/adm/help/tex/Change_Discussion_Display.tex	Sat Aug 20 16:06:50 2016
@@ -3,10 +3,10 @@
 In a discussion board or resource in which there
 has been discussion, display settings will determine:
 (a) which posts are displayed, and
-(b) which are marked as 'NEW'. 
+(b) which are marked as `NEW'. 
 
 The default is for all posts to be displayed, and for new posts  
-to remain marked as 'NEW' until you explicitly mark them as read.
+to remain marked as `NEW' until you explicitly mark them as read.
 
 You can set a personal preference that will apply to your display
 of \emph{all} discussions in \emph{all} courses.
@@ -26,7 +26,7 @@
 \item At the \textbf{Set User Preferences} screen, select
 \includegraphics[width=0.03\paperwidth]{chat}
 \textbf{Discussion Display}.
-\item Check one or both 'Change' checkboxes in the \textbf{Action} column.
+\item Check one or both `Change' checkboxes in the \textbf{Action} column.
 \item Click \textbf{Save}.
 
 \end{enumerate}
Index: loncom/html/adm/help/tex/Change_Password.tex
diff -u loncom/html/adm/help/tex/Change_Password.tex:1.9 loncom/html/adm/help/tex/Change_Password.tex:1.10
--- loncom/html/adm/help/tex/Change_Password.tex:1.9	Tue Aug 27 05:01:24 2013
+++ loncom/html/adm/help/tex/Change_Password.tex	Sat Aug 20 16:06:50 2016
@@ -23,7 +23,7 @@
 \end{enumerate}
 
 If you cannot change your password, please use the Help link at the top right of the page
-and then click "Ask Helpdesk" to submit a help request to ask for instructions.
+and then click ``Ask Helpdesk'' to submit a help request to ask for instructions.
 University users often authenticate against the campus-wide
 system. For those users, changing the password used by LON-CAPA means changing the
 user's campus-wide password. Your helpdesk will be able to tell you how to go about that. 
Index: loncom/html/adm/help/tex/Clicker_Registration.tex
diff -u loncom/html/adm/help/tex/Clicker_Registration.tex:1.9 loncom/html/adm/help/tex/Clicker_Registration.tex:1.10
--- loncom/html/adm/help/tex/Clicker_Registration.tex:1.9	Tue Aug 27 05:10:21 2013
+++ loncom/html/adm/help/tex/Clicker_Registration.tex	Sat Aug 20 16:06:50 2016
@@ -14,7 +14,7 @@
 in the \textbf{My Space} group
 \item At the \textbf{Set User Preferences} screen, select 
 \includegraphics[width=0.03\paperwidth]{network-workgroup}
-\textbf{Register Response Devices ("Clickers")}. 
+\textbf{Register Response Devices (``Clickers'')}. 
 \item Type your clicker ID in the text box.
 Below are instructions on how to find your clicker ID for various clicker models.
 \item Click the \fbox{Save} button.
@@ -107,8 +107,8 @@
 
 {\it Macintosh (OS X)}
 \begin{itemize} 
-\item Under the Apple menu, select "System Preferences".
-\item Select the "Network" Pane.
+\item Under the Apple menu, select ``System Preferences''.
+\item Select the ``Network'' Pane.
 \item Doubleclick on the adapter you are using, for example ``Airport'' or ``Built-in Ethernet'' (use the adapter you would use in the lecture hall).
 \item Click on the ``Airport'' or ``Ethernet'' tab, respectively - the number is displayed.
 \end{itemize}
Index: loncom/html/adm/help/tex/Course_Automated_Enrollment.tex
diff -u loncom/html/adm/help/tex/Course_Automated_Enrollment.tex:1.12 loncom/html/adm/help/tex/Course_Automated_Enrollment.tex:1.13
--- loncom/html/adm/help/tex/Course_Automated_Enrollment.tex:1.12	Sun Jul 24 14:35:45 2016
+++ loncom/html/adm/help/tex/Course_Automated_Enrollment.tex	Sat Aug 20 16:06:50 2016
@@ -30,9 +30,9 @@
 \item Student photos: Enable/Disable automatic import of student photos from an institutional repository.  This functionality requires that (a) a conduit has been established from your library server(s) to a directory containing student photos, and (b) the \&institutional\_photos() routine in localenroll.pm has been customized to use this conduit. Your institution may require the course owner to indicate acceptance of policies governing use of digital student photos. If this is the case, the \&photo\_permission() routine will have been customized for your domain, and the course owner will need to click a button to acknowledge agreement to the policy, before the option to enable use student photos is enabled in a course. 
 \item Enrollment status: Students in a course are identified internally
 by type (auto or manual) depending on whether they were auto-enrolled.
-Only users of type 'auto' will be dropped from the course if auto-enrollment
+Only users of type `auto' will be dropped from the course if auto-enrollment
 detects expired enrollment. By default, status type is automatically
-changed from 'manual' to 'auto', if a manually enrolled student subsequently
+changed from `manual' to `auto', if a manually enrolled student subsequently
 appears in the institutional roster when auto-enrollment is run. This
 automatic migration can be prevented for individual students by locking
 the status type.
Index: loncom/html/adm/help/tex/Course_Create_Class_List.tex
diff -u loncom/html/adm/help/tex/Course_Create_Class_List.tex:1.14 loncom/html/adm/help/tex/Course_Create_Class_List.tex:1.15
--- loncom/html/adm/help/tex/Course_Create_Class_List.tex:1.14	Wed Aug 18 11:40:50 2010
+++ loncom/html/adm/help/tex/Course_Create_Class_List.tex	Sat Aug 20 16:06:50 2016
@@ -28,5 +28,5 @@
 
 \item Once you have the column assignment and defaults set,  click the \fbox{Update Users} button to finish.  
 
-\item If you had checked the "Full Update" box, after processing of the uploaded file, a list of students who are in the course, but who were not listed in the uploaded file will be displayed, and you will have the opportunity to drop some, or all, of those students.
+\item If you had checked the ``Full Update'' box, after processing of the uploaded file, a list of students who are in the course, but who were not listed in the uploaded file will be displayed, and you will have the opportunity to drop some, or all, of those students.
 \end{enumerate}
Index: loncom/html/adm/help/tex/Course_Manage_Group.tex
diff -u loncom/html/adm/help/tex/Course_Manage_Group.tex:1.4 loncom/html/adm/help/tex/Course_Manage_Group.tex:1.5
--- loncom/html/adm/help/tex/Course_Manage_Group.tex:1.4	Wed Nov 27 16:30:49 2013
+++ loncom/html/adm/help/tex/Course_Manage_Group.tex	Sat Aug 20 16:06:50 2016
@@ -4,7 +4,7 @@
 
 \begin{enumerate}
  
-\item Mouseover the \textbf{People} item in the inline menu and select \textbf{Groups} or click "Manage course users" (\includegraphics[width=0.03\paperwidth]{cprv}
+\item Mouseover the \textbf{People} item in the inline menu and select \textbf{Groups} or click ``Manage course users'' (\includegraphics[width=0.03\paperwidth]{cprv}
 on the Main Menu, and click the the \underbar{Manage Course Groups} link, or click GRPS on the Remote Control (if used).
 \item If you have already created groups these will be listed in a table.  There are also links to create a new group, or re-enable a deleted group (if any exist), if you have group modification privileges.    
 \item For a particular group, click the \underbar{View} link to display the group's homepage, and to access collaboration functions in the group.  Similarly, click the \underbar{Modify} or \underbar{Delete} links, respectively, to change group settings and/or membership, or to delete a group.
Index: loncom/html/adm/help/tex/Course_Maximum_Collaborators.tex
diff -u loncom/html/adm/help/tex/Course_Maximum_Collaborators.tex:1.6 loncom/html/adm/help/tex/Course_Maximum_Collaborators.tex:1.7
--- loncom/html/adm/help/tex/Course_Maximum_Collaborators.tex:1.6	Tue Aug 27 05:18:02 2013
+++ loncom/html/adm/help/tex/Course_Maximum_Collaborators.tex	Sat Aug 20 16:06:50 2016
@@ -20,9 +20,9 @@
 parameters that can be set for the specific problem.
 \item Scroll down to the \textbf{Maximum Number of Collaborators}
   field in the \textbf{Parameter Name} column.
-\item In the Course Columns, click "\textbf{-}" in the general column for entire course, 
-click "\textbf{-}" in the "for enclosing map or folder" for a specific map or folder, 
-click "\textbf{-}" in the "resource column" for a particular resource. A new window will 
+\item In the Course Columns, click ``\textbf{-}'' in the general column for entire course, 
+click ``\textbf{-}'' in the ``for enclosing map or folder'' for a specific map or folder, 
+click ``\textbf{-}'' in the ``resource column'' for a particular resource. A new window will 
 open.
 \item Update the selected parameter.
 \item Click \textbf{Store}.
Index: loncom/html/adm/help/tex/Course_Prefs_Printouts.tex
diff -u loncom/html/adm/help/tex/Course_Prefs_Printouts.tex:1.3 loncom/html/adm/help/tex/Course_Prefs_Printouts.tex:1.4
--- loncom/html/adm/help/tex/Course_Prefs_Printouts.tex:1.3	Mon Dec 28 04:10:45 2015
+++ loncom/html/adm/help/tex/Course_Prefs_Printouts.tex	Sat Aug 20 16:06:50 2016
@@ -7,8 +7,8 @@
 \item Print header format (default is ``name'' ``course description'' on first header line,
 resource/folder title on second header line).
 
-Whenever you set at least one item, in the "Print header format" it eliminates display
-of LON-CAPA's default header.  In the "Print header format" select what you would like to enter.  
+Whenever you set at least one item, in the ``Print header format'' it eliminates display
+of LON-CAPA's default header.  In the ``Print header format'' select what you would like to enter.  
 There are two types of item:
 \begin{enumerate}
 \item Substitution
Index: loncom/html/adm/help/tex/Course_Problem_Weight.tex
diff -u loncom/html/adm/help/tex/Course_Problem_Weight.tex:1.7 loncom/html/adm/help/tex/Course_Problem_Weight.tex:1.8
--- loncom/html/adm/help/tex/Course_Problem_Weight.tex:1.7	Mon Aug 23 11:37:23 2010
+++ loncom/html/adm/help/tex/Course_Problem_Weight.tex	Sat Aug 20 16:06:50 2016
@@ -1,6 +1,6 @@
 \label{Course_Problem_Weight}
 
-By default, the problem "weight" is equal to the amount of points the problem
+By default, the problem ``weight'' is equal to the amount of points the problem
 is worth. If the problem is made up of multiple parts, each with their own submit
 button, then those parts behave as if they were separate problems,
 and each one has its own weight.
Index: loncom/html/adm/help/tex/Course_Request_Clone.tex
diff -u loncom/html/adm/help/tex/Course_Request_Clone.tex:1.1 loncom/html/adm/help/tex/Course_Request_Clone.tex:1.2
--- loncom/html/adm/help/tex/Course_Request_Clone.tex:1.1	Thu Sep 10 03:00:24 2009
+++ loncom/html/adm/help/tex/Course_Request_Clone.tex	Sat Aug 20 16:06:50 2016
@@ -1,4 +1,4 @@
 \label{Course_Request_Clone}
-You may choose to build your new course by cloning an existing course. If you have Course Coordinator access or have been assigned "cloner" rights in an existing course currently in the LON-CAPA system you can search for the course and select it in a pop-up window, launched by the 'Select Course' link.
+You may choose to build your new course by cloning an existing course. If you have Course Coordinator access or have been assigned ``cloner'' rights in an existing course currently in the LON-CAPA system you can search for the course and select it in a pop-up window, launched by the `Select Course' link.
 
-Cloning a course will copy all course content, and most course settings.  Student enrollment, peformance data and discussion postings will not be copied.  Settings which involve dates (e.g., open dates, due dates, and close dates for availability of course content and online homework problems) will be preserved, shifted by a number of days, or omitted from the copy process, based on your choice for the 'Date Shift'.    
+Cloning a course will copy all course content, and most course settings.  Student enrollment, peformance data and discussion postings will not be copied.  Settings which involve dates (e.g., open dates, due dates, and close dates for availability of course content and online homework problems) will be preserved, shifted by a number of days, or omitted from the copy process, based on your choice for the `Date Shift'.
Index: loncom/html/adm/help/tex/Course_Request_Crosslist.tex
diff -u loncom/html/adm/help/tex/Course_Request_Crosslist.tex:1.3 loncom/html/adm/help/tex/Course_Request_Crosslist.tex:1.4
--- loncom/html/adm/help/tex/Course_Request_Crosslist.tex:1.3	Tue Mar 20 13:25:06 2012
+++ loncom/html/adm/help/tex/Course_Request_Crosslist.tex	Sat Aug 20 16:06:50 2016
@@ -1,4 +1,4 @@
 \label{Course_Request_Crosslist}
-An 'official' course may be crosslisted in your institution's schedule of courses under a different number, or a different department.  If this is the case for your course, and you would like students who are enrolled in the crosslisted courses to be enrolled automatically in your LON-CAPA course, select the appropriate options from your institution's course categorization. 
+An `official' course may be crosslisted in your institution's schedule of courses under a different number, or a different department.  If this is the case for your course, and you would like students who are enrolled in the crosslisted courses to be enrolled automatically in your LON-CAPA course, select the appropriate options from your institution's course categorization. 
 
-The 'LON-CAPA section' is the section within your LON-CAPA course with which students enrolled in the crosslisted course will be affiliated.  You can leave this box empty if you do not wish to differentiate students based on method of enrollment.  In that case students will receive a 'section-less' role in your LON-CAPA course.  Otherwise, note that LON-CAPA section names may only contain letters and numbers.
+The `LON-CAPA section' is the section within your LON-CAPA course with which students enrolled in the crosslisted course will be affiliated.  You can leave this box empty if you do not wish to differentiate students based on method of enrollment.  In that case students will receive a `section-less' role in your LON-CAPA course.  Otherwise, note that LON-CAPA section names may only contain letters and numbers.
Index: loncom/html/adm/help/tex/Course_Request_LCSection.tex
diff -u loncom/html/adm/help/tex/Course_Request_LCSection.tex:1.1 loncom/html/adm/help/tex/Course_Request_LCSection.tex:1.2
--- loncom/html/adm/help/tex/Course_Request_LCSection.tex:1.1	Thu Sep 10 03:00:24 2009
+++ loncom/html/adm/help/tex/Course_Request_LCSection.tex	Sat Aug 20 16:06:50 2016
@@ -1,4 +1,4 @@
 \label{Course_Request_LCSection}
-The 'LON-CAPA section' is the section in your LON-CAPA course with which students automatically enrolled from a particular institutional section will be affiliated.  You can leave this box empty if you do not wish to differentiate students based on institutional section.  In that case, students will receive a 'section-less' role in your LON-CAPA course.
+The `LON-CAPA section' is the section in your LON-CAPA course with which students automatically enrolled from a particular institutional section will be affiliated.  You can leave this box empty if you do not wish to differentiate students based on institutional section.  In that case, students will receive a `section-less' role in your LON-CAPA course.
 
 LON-CAPA section names may only contain letters and numbers.
Index: loncom/html/adm/help/tex/Course_Request_Personnel.tex
diff -u loncom/html/adm/help/tex/Course_Request_Personnel.tex:1.2 loncom/html/adm/help/tex/Course_Request_Personnel.tex:1.3
--- loncom/html/adm/help/tex/Course_Request_Personnel.tex:1.2	Fri Oct 12 13:27:40 2012
+++ loncom/html/adm/help/tex/Course_Request_Personnel.tex	Sat Aug 20 16:06:50 2016
@@ -7,4 +7,4 @@
 
 Additional Coordinators can be only be added to a Course/Community by either the course owner, (i.e., the person who submitted the original request), or by the domain coordinator (usually someone from the unit responsible for providing LON-CAPA service at your institution), once a course is set-up.
 
-You will probably not want to add students to your course from the 'additional personnel' page included in the course request form, as there are more efficient ways to do this once the course has been created.  If your institution has enabled automatic enrollment in official courses, then that would be the simplest way to add students to an 'official' course.  You can also upload a file containing usernames of students - and (optionally) other information - once the course has been created.  
+You will probably not want to add students to your course from the `additional personnel' page included in the course request form, as there are more efficient ways to do this once the course has been created.  If your institution has enabled automatic enrollment in official courses, then that would be the simplest way to add students to an `official' course.  You can also upload a file containing usernames of students - and (optionally) other information - once the course has been created.  
Index: loncom/html/adm/help/tex/Course_Request_Rolesection.tex
diff -u loncom/html/adm/help/tex/Course_Request_Rolesection.tex:1.1 loncom/html/adm/help/tex/Course_Request_Rolesection.tex:1.2
--- loncom/html/adm/help/tex/Course_Request_Rolesection.tex:1.1	Thu Sep 10 03:00:24 2009
+++ loncom/html/adm/help/tex/Course_Request_Rolesection.tex	Sat Aug 20 16:06:50 2016
@@ -3,9 +3,9 @@
 
 LON-CAPA section names may only contain letters and numbers.
 
-The Course Coordinator role is 'section-less' and will have access to all sections in a course with multiple sections. For other roles, you can assign access to specific sections. To assign a 'section-less' role with access to all sections choose "None" if there are 'Official' sections, or else leave the LON-CAPA Sections box empty.  
+The Course Coordinator role is `section-less' and will have access to all sections in a course with multiple sections. For other roles, you can assign access to specific sections. To assign a `section-less' role with access to all sections choose "None" if there are `Official' sections, or else leave the LON-CAPA Sections box empty.  
 
-If there are 'Official' sections, you can select multiple sections by using the following keyboard and mouse combinations in the 'official' sections drop-down box.
+If there are `Official' sections, you can select multiple sections by using the following keyboard and mouse combinations in the `official' sections drop-down box.
 
 \begin{longtable}{|ll|}
 \hline 
@@ -16,4 +16,4 @@
 \hline
 \end{longtable}
 
-Use a comma to separate section names when specifying multiple sections in the 'LON-CAPA sections' box.
+Use a comma to separate section names when specifying multiple sections in the `LON-CAPA sections' box.
Index: loncom/html/adm/help/tex/Authoring_Math_Editor.tex
diff -u loncom/html/adm/help/tex/Authoring_Math_Editor.tex:1.2 loncom/html/adm/help/tex/Authoring_Math_Editor.tex:1.3
--- loncom/html/adm/help/tex/Authoring_Math_Editor.tex:1.2	Mon Jul 28 14:00:00 2008
+++ loncom/html/adm/help/tex/Authoring_Math_Editor.tex	Sat Aug 20 16:06:50 2016
@@ -1,5 +1,5 @@
 \label{Authoring_Math_Editor}
-You can use the \char`\"{}Edit Math\char`\"{} button to open a pop-up
+You can use the {}``Edit Math'' button to open a pop-up
 window containing the Drag Math editor. Use the editor to compose
 a math expression you wish to include in the text of a LON-CAPA resource,
 click the {}``Render Latex'' button and the expression will be 
