update links and add images

lab-p2/README.md

@@ -25,7 +25,7 @@ Let's start by looking at interactive mode, where code is executed one line at a
 Run `python --version` in the terminal.  You might see something like this:
 
 ```
-Python 3.11.3
+Python 3.11.4
 ```
 
 If it says something like 2.X.X, try running `python3 --version` instead. If you need to run the latter, please use `python3` whenever we say `python` in the directions this semester.  
@@ -37,7 +37,7 @@ Many commands support some type of version argument. How do you think you could
 ### Task 1.2: Use `pwd` to verify that you are in the `lab-p2` directory.
 
 The command `pwd` is a command line argument that stands for **P**rint **W**orking **D**irectory.
-If the `pwd` command prints out a different directory path than your `lab-p2` directory path, use `cd` commands to move to the correct working directory. See [lab-p1](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/lab-p1#task-15-navigate-to-the-lab1-directory) if you don’t recall how to use `cd` commands to navigate to a directory.
+If the `pwd` command prints out a different directory path than your `lab-p2` directory path, use `cd` commands to move to the correct working directory. See [Lab-P1](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/lab-p1#task-15-navigate-to-the-lab1-directory) if you don’t recall how to use `cd` commands to navigate to a directory.
 
 ### Task 1.3: Start Python in **interactive** mode.
 
@@ -46,12 +46,12 @@ Type `python` and press Enter.
 You should see something roughly like this (details will vary):
 
 ```
-Python 3.11.3 | packaged by Anaconda, Inc. | (main, Apr 19 2023, 23:46:34) [MSC v.1916 64 bit (AMD64)] on win32
+Python 3.11.4 | packaged by Anaconda, Inc. | (main, Jul  5 2023, 13:38:37) [MSC v.1916 64 bit (AMD64)] on win32
 Type "help", "copyright", "credits" or "license" for more information.
 >>>
 ```
 
-Those `>>>` symbols are a Python prompt. This means you can type Python code, but your shell commands will not work until you exit Python again. Recall that we learned about shell commands in [lab-p1](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/lab-p1#commonly-used-terminalpowershell-commands). Examples of shell commands include `cd`, `ls`, `mkdir`, etc.
+Those `>>>` symbols are a Python prompt. This means you can type Python code, but your shell commands will not work until you exit Python again. Recall that we learned about shell commands in [Lab-P1](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/lab-p1#commonly-used-terminalpowershell-commands). Examples of shell commands include `cd`, `ls`, `mkdir`, etc.
 
 ### Task 1.4: Run Python in interactive mode.
 
@@ -239,7 +239,7 @@ That's the end of this segment! Take a moment to summarize for yourself what you
 
 ## Segment 4: Otter tests check for project submission
 
-This segment is informational only and has no tasks. Remember that your work is **not complete** when you **submit** the project on Gradescope. It is **your responsibility** to make sure that your project clears the auto-grader tests on Gradescope. Otter test results should be available **within twenty to thirty minutes** after your submission. Your final score for the project is exactly the score that you will see on Gradescope. If you fail the tests on Gradescope for any reason, please contact a TA/PM, and have them look at your code.
+This segment is informational only and has no tasks. Remember that your work is **not complete** when you **submit** the project on Gradescope. It is **your responsibility** to make sure that your project clears the auto-grader tests on Gradescope. Otter test results should be available **within forty minutes** (but usually within ten minutes) after your submission. Your final score for the project is exactly the score that you will see on Gradescope. If you fail the tests on Gradescope for any reason, please contact a TA/PM, and have them look at your code.
 
 You **must** review the project's rubric and make sure that you have followed the directions provided in the project to solve the questions. The rubric is meant to reinforce your understanding of the project's directions. The Gradescope autograder will make **deductions** to your project score based on the rubric. Rubrics will become progressively stricter as we make progress during this semester.
 

p2/README.md

@@ -36,8 +36,12 @@ in Gradescope when uploading the P2 zip file.
 
    **Warning:** You will have to add your partner on Gradescope even if you have filled out this information in your `p2.ipynb` notebook.
 
-- It is **your responsibility** to make sure that your project clears auto-grader tests on the Gradescope test system. Otter test results should be available within forty minutes after your submission (usually within ten minutes). You should be able to see both PASS / FAIL results for the 20 test cases, which is accessible via Gradescope Dashboard (as in the image below):
+- It is **your responsibility** to make sure that your project clears auto-grader tests on the Gradescope test system. Otter test results should be available within forty minutes after your submission (usually within ten minutes). **Ignore** the `-/100.00` that is displayed to the right. You should be able to see both PASS / FAIL results for the 20 test cases, which is accessible via Gradescope Dashboard (as in the image below):
 
     <img src="images/gradescope.png" width="400">
 
-   You can view your **final score** at the end of the page.
+- You can view your **final score** at the **end of the page**. If you pass all tests, then you will receive **full points** for the project. Otherwise, you can see your final score in the **summary** section of the test results (as in the image below):
+
+   <img src="images/summary.png" width="400">
+
+   If you want more details on why you lost points on a particular test, you can scroll up to find more details about the test.