Update README.md

Author: jeremymanning

Diff for: README.md

@@ -22,13 +22,12 @@ If you're a member of [our lab](https://www.context-lab.com/) and/or a [Dartmout
 
 # Submit your own notes and/or solution(s)
 
-1. Start by [forking](https://github.com/ContextLab/leetcode-solutions/fork) this repository.  Or if you've already forked this, visit your fork and make sure to click the button to sync it up with this (source) repository.
-2. In your fork, in the menu near the top click on **Actions** to open up the GitHub Actions list.  Then click on **Create New Note for Daily LeetCode Problem** and then click **Run workflow** to create your new notes file for today's problem. Click the link to the notes on today's problem in the last row [table above](https://github.com/ContextLab/leetcode-solutions#problems-weve-attempted-thus-far) and you should see a markdown (.md) file named for your GitHub username.  Edit that to add your notes!
-  - If you're the "build it yourself" type, it's also OK to create your notes file manually.  Just navigate to the [problems](https://github.com/ContextLab/leetcode-solutions/new/main/problems) folder and click the **Add file** button on the right.  Choose the **Create new file** option:
-    - File name: `leetcode-solutions/problems/<PROBLEM NUMBER>/<your name>.md` (where you should replace `<PROBLEM NUMBER>` with the leetcode problem ID code, and `<your name>` with either your first name or your GitHub username (your choice!), in lowercase letters.  E.g., [Jeremy](https://www.context-lab.com/people)'s solution to problem 350 would be named `leetcode-solutions/blob/main/problems/350/jeremy.md`
+1. Start by [forking](https://github.com/ContextLab/leetcode-solutions/fork) this repository.  Or if you've already forked this repository, you should visit your fork and make sure to click the button to sync it up with this (source) repository.
+2. In your fork, in the menu near the top click on **Actions** to open up the GitHub Actions list.  Then click on **Create New Note for Daily LeetCode Problem** and then click **Run workflow** to create your new notes file for today's problem. Click the link to the notes on today's problem in the last row of the [table above](https://github.com/ContextLab/leetcode-solutions#problems-weve-attempted-thus-far) and you should see a markdown (.md) file named for your GitHub username.  Edit that to add your notes!
+  - If you're the "build-it-yourself" type, it's also OK to create your notes file manually.  Just navigate to the [problems](https://github.com/ContextLab/leetcode-solutions/new/main/problems) folder and click the **Add file** button on the right.  Choose the **Create new file** option:
+    - File name: `problems/<PROBLEM NUMBER>/<your name>.md` (where you should replace `<PROBLEM NUMBER>` with the leetcode problem ID code, and `<your name>` with either your first name or your GitHub username (your choice!), in lowercase letters.  E.g., [Jeremy](https://www.context-lab.com/people)'s solution to problem 350 would be named `problems/350/jeremy.md`
     - Contents: Any format is fine, but we suggest starting with our [template file](https://github.com/ContextLab/leetcode-solutions/blob/main/problems/template.md).  Then add your notes/solution as you solve the problem!  Make sure to commit your changes (and it's fine to make multiple commits as you're working on the problem).
-3. Once you've added your file, start a [pull request](https://github.com/ContextLab/leetcode-solutions/pulls) to add it into the ContextLab fork so that others can see how you approached the problem.
-4. Also make sure that the problem has been added to the [table](https://github.com/ContextLab/leetcode-solutions#problems-weve-attempted-thus-far).  If you're the first one to work on a problem, you'll need to add a row for it.  Problems should be listed in chronological order from top (earliest) to bottom (latest).
+3. Once you've added your file(s), start a [pull request](https://github.com/ContextLab/leetcode-solutions/pulls) to add your changes to the ContextLab repository so that others can see how you approached the problem.
 
 # Other stuff