proposed changes to "getting started" video (#48)

* proposed changes to "getting started" video

* run precommit

Author: drammock

content/contributors/getting-started.md

@@ -21,43 +21,50 @@ youtube_id:
 
 ## Choosing a project to work on
 
-How should you choose which project to work on?
-There are many projects in the ecosystem to choose from so it’s important to find one related to something you’re interested in or is a project you already use.
-For example, if you’re interested in working with images, it might be worth looking into implementing algorithms in scikit-image.
+How do you choose which project to contribute to?
+There's no single best way to choose a project, but here are some questions to think about when choosing:
 
-Typically, it is easier to contribute to smaller projects---but you also want to choose a project that’s active enough so that the developers can review your code and provide mentorship.
-There may also be more issues and ideas to work on.
+- _Is there a project related to your background or your research?_ E.g., astronomers might prefer to contribute to [astropy]() or [sunpy]().
+- _Is there a package you're already using?_ Even well-established general-purpose packages like [numpy](), [scipy](), or [matplotlib]() are still growing and changing, and need contributors.
+- _Is the project actively developed?_ Take a look at the project's repository to see how recent the last update was, and how many people seem to be involved.
+- _Is the community healthy?_ Project maintainers will be reviewing your work and mentoring you through the contribution process, so look to see if the interactions on the project's pull request pages are polite and welcoming.
 
-Before diving into a project, take a look at their open issues and pull requests, see how maintainers interact with the community, and decide if it would be good fit for you.
+One last tip is to look at the project's open issues to see if there are any tagged as "easy" or "good first issue", and if any of those look appealing to you.
 
 For a more detailed discussion, also take a look at our `Choosing a project` video, linked below.
 
-## Tools to learn
+## Tools of the trade
 
 As with any trade, there are certain fundamental tools you should learn.
 Since the ecosystem is built in Python, you'll need to know how to program in that language.
 Other tools we use daily include:
 
-- git and Github
+- git and GitHub
 - the command-line terminal, and
-- a good editor.
+- a plain-text editor or [integrated development environment]() ("IDE").
 
-Take a look below for links on how to learn these tools.
+In this video series, the basics of using these tools are covered along the way.
+To learn more about them, take at the links below:
 
-- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
-- https://tutorial.djangogirls.org/en/intro_to_command_line/
-- https://transitionintotech.com/choose-your-code-editor/
-- https://realpython.com/python-ides-code-editors-guide/
+- Command line terminal:
+  - https://swcarpentry.github.io/shell-novice/
+  - https://tutorial.djangogirls.org/en/intro_to_command_line/
+- Git and GitHub:
+  - https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
+  - https://docs.github.com/en/get-started
+- Text editors / IDEs:
+  - https://transitionintotech.com/choose-your-code-editor/
+  - https://realpython.com/python-ides-code-editors-guide/ <!-- this is out of date; e.g. it says VSCode is mac/windows only -->
 
 ## First contribution
 
 Now that you’ve chosen a project to contribute to, it’s time to get set up.
-Most projects have a file called CONTRIBUTING in the root of the repository that will tell you how to set up your development environment, propose changes, etc.
-Developer documentation will also explain testing and review procedures, and whatever else you need to know.
+Many projects have a file called `CONTRIBUTING` in the root of the repository that will tell you how to set up your development environment, propose changes, etc.
+Most projects also have a page on their website called "Developer documentation" or "Contributor guide" that will have similar information, and usually also explain testing and review procedures, and whatever else you need to know.
 
 When first contributing to a project, it’s best to start with small, self-contained issues.
-Often, maintainers will label issues with the "good first issue" label, so take a look at those first.
 Examples of a good first issue include fixing a small bug, adding tests, fixing documentation typos, or writing up simple documentation.
+If you haven't already found an issue you want to work on, now is the time (remember to look for the "good first issue" label if the project has it).
 
 It is not uncommon to get stuck while making your first contribution.
 Don't panic!
@@ -68,7 +75,7 @@ For more details, also check out our `First contribution` video.
 
 ## What's next
 
-Once you’re comfortable making small changes to the project, you can start taking on bigger features.
+Once you’re comfortable making small changes to the project, you can start taking on bigger contributions.
 There are many different ways to help: you may, e.g., implement new features, write documentation, refactor and clean up code, improve testing, work on build infrastructure, and so forth.
 
 No matter what you contribute, or whether you contribution is big or small, it is much appreciated.