Fix final batch of contractions found in comprehensive search

Co-authored-by: liammcalpineduckietown <[email protected]>

Author: Copilot

src/70-developer-manual/basics/terminal/terminal-basics.md

@@ -28,7 +28,7 @@ tutorial can be found [on the Ubuntu website](https://tutorials.ubuntu.com/tutor
 The terminal requires using a conding language called [BASH](https://en.wikipedia.org/wiki/Bash_(Unix_shell)), or "Bourne Again SHell". BASH is completely free and works on all major operating systems (e.g., Linux, macOS, Windows). If you are looking for an extensive list of commands that can be used from the terminal, [this command line cheatsheet](https://ss64.com/bash/) is a good resource.
 
 ```{todo}
-1. write section on how to pimp up the terminal; 2. write section on IDEs and provide a preset configuration for Pycharme CE and VisualStudio; 3. Provide some best practices for development; 4. Arguably move this away from the developer manual. It's too basic.
+1. write section on how to pimp up the terminal; 2. write section on IDEs and provide a preset configuration for Pycharme CE and VisualStudio; 3. Provide some best practices for development; 4. Arguably move this away from the developer manual. It is too basic.
 ```
 
 (sec:using-dt-shell)=

src/70-developer-manual/dtros/duckietown-dtros-class.md

@@ -513,7 +513,7 @@ Use `self.my_param = DTParam("~my_param")` to create a `DTParam` object and
 Then we initialize all the non-ROS attributes that we will need for this class.
 Note that this is done _before_ initializing the Publishers and Subscribers.
 The reason is that if a subscriber's callback depends on one of these attributes,
-we need to define it before we use it. Here's an example that might fail:
+we need to define it before we use it. Here is an example that might fail:
 
 ```python
 class CoolNode(DTROS):
@@ -571,7 +571,7 @@ Often we want to publish some information which helps us analyze the behavior an
 A frequent (__but bad design__) way of handling that is to have a topic, to which one can publish a message, which when received will induce the node to start building a publishing the debug message. A much better way, and the one that __should be used__ in Duckietown is to create and publish the debug message _only if_ someone has subscribed to the debug topic.
 This is very easy to achieve with the help of `dtros`.
 Publishers created within a DTROS node exports the utility function `anybody_listening()`.
-Here's an example:
+Here is an example:
 
 ```python
 if self.pub_debug_img.anybody_listening():

src/80-instructor-manual/introduction/duckietown-professor-journey.md

@@ -18,7 +18,7 @@ To do so, consider the following "journey" (although there could be many others)
 (professor-journey-evaluation)=
 ## Semester 0: Evaluate the platform
 
-There are many freely available resources available to get started. It's a great idea for you and/or some people from your group to try out the software,  hardware, and pedagogical materials  before committing to any next step.
+There are many freely available resources available to get started. It is a great idea for you and/or some people from your group to try out the software,  hardware, and pedagogical materials  before committing to any next step.
 
 A great place to start could be to sign up for the [Self-Driving Cars with Duckietown MOOC on EdX](https://www.edx.org/learn/technology/eth-zurich-self-driving-cars-with-duckietown).