[Fix] minor typos and unwanted whitespace in usability content

Author: sp35

content/contributing-code/usability/contents.lr

@@ -19,7 +19,7 @@ If you’re interested in volunteering your time, we invite you to sign up to ta
 
 ## What to Expect
 - After scheduling a time to talk to us, here’s what you can expect:
-- You’ll need to sign and return a [consent form](https://drive.google.com/file/d/1XWt5QDu-IR76BwsPP7OidqNncha3rHbm/view) , allowing us to record the screen during the session. We typically do screen share, and the value of the session is greatly increased when we can refer back to a recording while reviewing notes and findings.
+- You’ll need to sign and return a [consent form](https://drive.google.com/file/d/1XWt5QDu-IR76BwsPP7OidqNncha3rHbm/view), allowing us to record the screen during the session. We typically do screen share, and the value of the session is greatly increased when we can refer back to a recording while reviewing notes and findings.
 - You’ll need a good internet connection, a functioning microphone, and the ability to use Google Meet.
 - When the session starts, we begin with introductions and some general questions about you!
 - We then move on to screen share, where we may do a number of things: complete tasks through prototypes, look at existing products, review proposed designs, compare interfaces of similar services, or talk about a topic related to the session. There are no wrong answers. As researchers, we’re interested in hearing your honest thoughts and ideas. We’ll ask you to talk out loud as much as possible, and filter nothing!
@@ -51,10 +51,10 @@ Decide which tools suit best for the purposes of the test. Depending on the goal
 
 Have a notes document prepared, or better yet, enlist someone else to join the call to take notes. If (and only if) your participant has consented to screen share being recorded, be ready with software that records the screen. We often use QuickTime (if on a Mac), it is simple and free. Another option is [OBS](https://obsproject.com/), which is free, open source, and cross platform.
 
-Remember that the point of the test is to ask questions and get feedback. It is not to educate, give guidance, or explain. Whether you are running a usability test, remember that you want  to see what the user will do to complete the task when no one is around to help them. Ask them to think out loud, so that you can better understand what is clear and what is confusing, and pay close attention to how the user interacts with the prototype. If something related to your research purpose catches your attention, dive into it by asking why.
+Remember that the point of the test is to ask questions and get feedback. It is not to educate, give guidance, or explain. Whenever you are running a usability test, remember that you want to see what the user will do to complete the task when no one is around to help them. Ask them to think out loud, so that you can better understand what is clear and what is confusing, and pay close attention to how the user interacts with the prototype. If something related to your research purpose catches your attention, dive into it by asking why.
 
 **Thank the user.** At the end of the test, remember to thank the user. If you have the budget for it, we recommend signaling gratitude with a gift card, or other reward. Members of your community may politely decline this offer, because their reward is the ability to contribute to improving your product.
 
 **Review your findings.** Spend time with your notes, rewatching the screen recording, and deeply thinking about what you have learned.
 
-We strongly recommend reading [Rocket Surgery Made Easy by Steve Krug](http://stevekrug.com/rsme.html ). The methods we employ at CC are to a large extent based on the guidance in that book. Have you read something fantastic about usability testing? Join us in the #cc-usability channel in the [Creative Commons Slack](https://slack-signup.creativecommons.org/) and share your resources!
+We strongly recommend reading [Rocket Surgery Made Easy by Steve Krug](http://stevekrug.com/rsme.html ). The methods we employ at CC are to a large extent based on the guidance in that book. Have you read something fantastic about usability testing? Join us in the `#cc-usability` channel in the [Creative Commons Slack](https://slack-signup.creativecommons.org/) and share your resources!