Fix: Edits from @ucodery

Co-authored-by: Jeremy Paige <[email protected]>

clean-modular-code/activity-2/clean-code-activity-2.md

@@ -28,7 +28,7 @@ You can use the script you worked on in Activity 1 here. Or you can use the clea
 
 ## Remember the strategies for cleaner code 
 
-* Document what the code does by adding a docstring at the top of the script to help your future self, a future lab mate, or another user understand that tasks that your code performs.
+* Document what the code does by adding a docstring at the top of the script to help your future self, a future lab mate, or another user understand the tasks that your code performs.
 
 In this exercise, you will focus specifically on:
 
@@ -199,7 +199,7 @@ If you complete the above activity with time to spare, here are a few additional
 In the JSON data that you have been processing, the package titles can be found in the title column as follows: `"package-name: title here."` 
 
 1. Add a processing step to the code that pulls the package name out from the title column and creates a new column called `package-name`.
-1. Create a workflow that calculates how many packages in that list are pyOpenSci packages. To calculate how many are pyOpenSci packages,   you will need the `pyos-joss-accepted-packages.csv` file in the `data/` directory with the activity 2 JSON data. This .csv file lists all pyOpenSci packages that have also gone through JOSS review.
+1. Create a workflow that calculates how many packages in that list are pyOpenSci packages. To calculate how many are pyOpenSci packages, you will need the `pyos-joss-accepted-packages.csv` file in the `data/` directory with the activity 2 JSON data. This .csv file lists all pyOpenSci packages that have also gone through JOSS review.
 :::
 
 +++ {"editable": true, "slideshow": {"slide_type": ""}}