Update CONTRIBUTING.md

Author: sleepyStick

CONTRIBUTING.md

@@ -434,15 +434,14 @@ you are attempting to validate new spec tests in PyMongo.
 
 ### Automated Specification Test Resyncing
 There is a script (`/.evergreen/scripts/resync-all-specs.sh`) that will
-automatically run once a week to resync all the specs with the [specifications
-repo](https://github.com/mongodb/specifications).
+automatically run once a week to resync all the specs with the [specifications repo](https://github.com/mongodb/specifications).
 If there are changes, a PR will be generated by mongodb-drivers-pr-bot.
 If any errors occurred, the PR description will display the name of the spec along
 with stderr from the `bash resync-spec.sh <spec>` command.
 
 Naturally, there will be spec tests that will fail if merged since the associated fix
 or behavioral change has not been implemented yet. For existing tests that have been
-modified, we will add these changes to a patch file (in `/.evergreen/patch`). Each patch
+modified, we will add these changes to a patch file (in `/.evergreen/spec-patch`). Each patch
 file will be named after a PYTHON ticket and the contents of the file will be the associated
 test differences between PyMongo's tests and the specification.
 To be clear, changes listed in these patch files will be *undone* by the script, and thus won't
@@ -457,13 +456,21 @@ the fix or behavioral change.
 
 #### Adding to a patch file
 Assuming the changes are committed somewhere, to add to any of the
-patch files, run `git diff` to show the desired changes and paste the
+patch files, run `git diff` to show the desired changes to undo and paste (or add) the
 results into the patch file.
 
-For example, there are new test files on the most recent commit of the current branch that are failing.
-To add those changes to `new.patch`, I would do the following:
+For example, there are modifications to test files on the most recent commit of the current branch that are failing.
+To add those changes to `PYTHON-1234.patch` (where PYTHON-1234 is the ticket associated with the changes),
+I would do the following:
 ```bash
-git diff HEAD~1 path/to/new/file >> .evergreen/patch/new.patch
+git diff HEAD~1 path/to/file >> .evergreen/spec-patch/PYTHON-1234.spec-patch
+```
+
+#### Running Locally
+Both `resync-all-specs.sh` and `resync-all-specs.py` can be run locally (and won't generate a PR).
+```bash
+./.evergreen/scripts/resync-all-specs.sh
+python3 ./.evergreen/scripts/resync-all-specs.py
 ```
 
 ## Making a Release