Adds a short paragraph explaining git pull and PRs are not the same

episodes/07-github.md

@@ -491,7 +491,7 @@ Our local and remote repositories are now in this state:
 You may see a `-u` option used with `git push` in some documentation.  This
 option is synonymous with the `--set-upstream-to` option for the `git branch`
 command, and is used to associate the current branch with a remote branch so
-that the `git pull` command can be used without any arguments. To do this,
+that the `git push` command can be used without any arguments. To do this,
 simply use `git push -u origin main` once the remote has been set up.
 
 Here, we are telling Git to push the branch

episodes/10-pull-requests.md

@@ -166,7 +166,7 @@ The PR is now successfully merged into the `main` branch.
 We can safely delete the `forecast` branch from the GitHub repo.
 Click on the **Delete branch button**.
 
-### Updating your Local Repo
+## Updating your Local Repo
 
 The new `forecast.md` file is currently only on the `main` branch in GitHub.
 We should pull the changes down to our local copy.
@@ -199,6 +199,12 @@ Fast-forward
  create mode 100644 forecast.md
 ```
 
+`git pull` and GitHub's Pull Requests are not the same.
+GitHub Pull Requests are where we performed code and science review,
+then merged our feature branch changes into the `main` branch.
+`git pull` is fetching changes to the remote branch on GitHub
+and merging them into your local copy.
+
 :::::::::::::::::::::::::::::::::::::::::  callout
 
 ## You may need to tell Git what to do