(MAINT) Fix typos

quests/agent_run.md

@@ -255,7 +255,7 @@ Open your `site.pp` manifest:
     vim /etc/puppetlabs/code/environments/production/manifests/site.pp
 
 Scroll past the comments and default node definition to the bottom of the file.
-(In Vim, you can type `G` to jump the the bottom of a file) This is where
+(In Vim, you can type `G` to jump the bottom of a file) This is where
 you'll create a new node definition for the `agent.puppet.vm` system. The
 outline of the node definition should look like this:
 

quests/defined_resource_types.md

@@ -105,7 +105,7 @@ Though a resource's title and namevar are distinct, the value you would assign
 to a resource's namevar is generally an excellent candidate for an expressive
 and unique title. For example, if the `path` of a file resource is
 `/etc/hosts`, using that path as the resource title makes it immediately clear
-what the the resource is managing. The common convention, then, is to use the
+what the resource is managing. The common convention, then, is to use the
 value of a resource's namevar as its title. To support this convention, a
 resource's namevar defaults to the value of its title unless it is explicitly
 set to a different value. This is why, for instance, you generally see the

quests/hello_puppet.md

@@ -81,7 +81,7 @@ and control, the complexity can leave a new user wondering where to start.
 By initially introducing Bolt, and now the Puppet agent and some of the
 command line tools included in
 the agent installation, there should be a balance between the
-big-picture view of Puppet and the the bottom-up fundamentals. You'll begin to
+big-picture view of Puppet and the bottom-up fundamentals. You'll begin to
 understand the agent's role in the broader Puppet architecture, as well as the
 details of how it interacts with the system where it's installed.
 

quests/puppetfile.md

@@ -211,7 +211,7 @@ can store a value in the connected database and retrieve it.
 
 ## Review
 
-In this quest, we introduced the the use of a Puppetfile to manage external
+In this quest, we introduced the use of a Puppetfile to manage external
 module dependencies.
 
 After learning the basic syntax of the Puppetfile, you used the `puppet module