Update index.html

stages/task-recent-changes/index.html

@@ -57,29 +57,25 @@ <h3>Criteria for pathways to be <b>approved</b>:</h3>
      <h2>Instructions</h2>
 
 	  <ul>
-	  <li>Click the pathway image or title below to view the pathway at WikiPathways (classic). You will need to be logged in at WikiPathways.</li> 
-	  <li>There are a couple of ways you can assess the edits:</li>
+	  <li>Click the pathway image or title below to view the pathway at WikiPathways (classic). You will need to be logged in at WikiPathways. There are a couple of ways you can assess the edits:</li> 
 		<ul>
-		<li>Using the <b>History</b> tab, open the previous version in a new window and visually compare the two.</li> 
+		<li>Using the <b>History</b> tab, open the previous version in a new window and visually compare the two revisions.</li> 
 		<li>Using GitHub's diff viewer is a convenient way to review the difference between two versions of the pathway. Let's use <b>WP5424</b> as an example:</li>
 			<ul>
 			<li>Navigate to the pathway page on WikiPathways.org, for example <a href="https://www.wikipathways.org/pathways/WP5424.html" target="_blank">https://www.wikipathways.org/pathways/WP5424.html</a>.</li> 
 			<li>In the <b>Activity</b> section under the pathway, click the <b>last edited</b> date badge. This will take you to the GitHub page listing <a href="https://github.com/wikipathways/wikipathways.github.io/commits/main/_pathways/WP5424.md" target="_blank">all commits</a> 
 			for this pathway. Click on the latest entry.</li>
-			<li>Commits might contain changes to more than one pathway; you can filter it by entering the pathway id, for example <b>WP5424</b>, in the <b>Filter changed files</b> field in the upper left. 
-				You can then easily select a changed file (datanodes, markdown and image file) relevant to WP5424 from the list to focus the view.</li>
-			<li>The diff viewer will highlight lines that had deletions in red and lines that had additions in green, with the parts that were deleted/added in darker shades.</li>
+			<li>Each commit will contain changes to more than one pathway; you can filter it by entering the pathway id, for example <b>WP5424</b>, in the <b>Filter changed files</b> field in the upper left. 
+				You can then easily select a changed file (datanodes, markdown or image file) relevant to WP5424 from the list.</li>
+			<li>The diff viewer will highlight deletions in red and additions in green, with the parts that were deleted/added in darker shades.</li>
 			<li>For example, changes to References, Description and Annotations would be seen in the markdown (.md) file, and changes to the data node identifiers would be seen in the datanodes (.tsv) file.</li>
 			<img src="gh-diffview.png" width="900px">
 		</ul>	
 	  <li>If the change is not valid, revert the edit in the <b>History</b> table on the classic site. If unsure, start a discussion using the links in the <b>Talk</b> page.</li>
       	  <li>If the pathway is a new pathway, consider adding the <b>Approved version</b> tag to the pathway if it fulfills the criteria listed above.</li>
-	  <li>Consider adding quality tags to the pathway:</li>
-			<ul>
-	  		<li><b>Under Construction</b>: the pathway appears incomplete, but is not a test pathway (i.e. the content is unique).</li>
-     			<li><b>Test Pathway</b>: the pathway is entirely empty, is filled with random content, or has "Test" in the title.</li>
-	  		</ul>
-		</ul>
+	  <li>Add other quality tags where appropriate; <b>Under Construction</b> for pathways that appear incomplete, but are not test pathways (i.e. the content is unique), <b>Test Pathway</b> for pathways 
+	  that are mostly empty, filled with random content, or has "Test" in the title.</li>
+	</ul>
 	<li>Click the <b>Next pathway</b> to load the next pathway and repeat the process. The function simply counts down the pathways edited in the last 10 days. Refresh will restart the countdown.</li>
 	  </ul> 
 	<p>If you have a question related to one of the pathways you reviewed, report it to our curation issues tracker by clicking the button below. Issues reported here will be discussed in the Community Curation meetings.</p>