diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
index 7ad590b..fd961f4 100644
--- a/.github/PULL_REQUEST_TEMPLATE
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -12,7 +12,7 @@ Closes #2
 ### Checklist
 - [ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
 - [ ] I have read the [Contribution Guide] and my PR follows them.
-- [ ] I updated my branch with the master branch.
+- [ ] I updated my branch with the development branch.
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] I have added necessary documentation about the functionality in the appropriate .md file
 - [ ] I have added in line documentation to the code I modified
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 6587186..717abab 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -128,15 +128,15 @@ Generally, we follow the style guidelines as suggested by the official language.
 2. If you cloned a while ago, get the latest changes from upstream:
 
    ```bash
-   git checkout <dev-branch>
-   git pull upstream <dev-branch>
+   git checkout development
+   git pull upstream development
    ```
 
 3. Create a new topic branch (off the main project development branch) to
    contain your feature, change, or fix:
 
    ```bash
-   git checkout -b <topic-branch-name>
+   git checkout -b <topic-branch-name> development
    ```
 
 4. Commit your changes in logical chunks. Please adhere to these [git commit
@@ -152,7 +152,7 @@ Generally, we follow the style guidelines as suggested by the official language.
 5. Locally merge (or rebase) the upstream development branch into your topic branch:
 
    ```bash
-   git pull [--rebase] upstream master
+   git pull [--rebase] upstream development
    ```
 
 6. Push your topic branch up to your fork:
@@ -162,6 +162,6 @@ Generally, we follow the style guidelines as suggested by the official language.
    ```
 
 7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-    with a clear title and description against the `master` branch. All tests must be passing before we will review the PR.
+    with a clear title and description against the `development` branch. All tests must be passing before we will review the PR.
 
 If you have any additional questions, please feel free to [email](mailto:dx@sendgrid.com) us or create an issue in this repo.