CONTRIBUTING.md in dpl-2.0.0.beta.2 vs CONTRIBUTING.md in dpl-2.0.0.beta.3

@@ -43,11 +43,11 @@
 
 ## Navigating the Codebase
 
 All provider specific classes live in [dpl/providers](lib/dpl/providers).
 These represent the CLI commands that are executed when the command line
-exectuable `dpl` is run with a given provider name as the first argument.
+executable `dpl` is run with a given provider name as the first argument.
 
 Each provider is a subclass of `Dpl::Provider`, which is defined in
 [dpl/provider.rb](lib/dpl/provider.rb). The provider base class itself
 subclasses from `Cl::Cmd`, so it represents an executable sub command of the
 main command `dpl`.
@@ -110,11 +110,11 @@
 
 When a provider class is instantiated and run it will go through a number
 of stages that make up the deployment process.
 
 These are documented in [dpl/provider.rb](/lib/dpl/provider.rb).
-If you are adding a new deployment provider please familiarize youself with
+If you are adding a new deployment provider please familiarize yourself with
 this lifecycle.
 
 Feel free to pick and interpret these stages according to the needs and
 semantics of the service provider you are adding. By no means do all of these
 stages have to be filled in or implmented. The `Provider` base class checks for
@@ -317,10 +317,10 @@
 test.
 
 ## Testing Dpl Branches or Forks on Travis CI
 
 It is possible to test a new deployment provider or new functionality of dpl on
-Travis CI. In order to do so, add proper configuraiton on the `edge` key to
+Travis CI. In order to do so, add proper configuration on the `edge` key to
 your `.travis.yml` like so:
 
 ```yaml
 deploy:
   provider: [name]