From 18ac2713e77ef9e369c8a934c7edf282f9263e5d Mon Sep 17 00:00:00 2001
From: Elmer Thomas <elmer@thinkingserious.com>
Date: Sun, 5 May 2019 11:09:04 -0700
Subject: [PATCH] Branding and SMS update

---
 .github/PULL_REQUEST_TEMPLATE                 |   4 +-
 CODE_OF_CONDUCT.md                            |  20 +-
 CONTRIBUTING.md                               |  38 +-
 LICENSE.md                                    |   2 +-
 README.md                                     |  31 +-
 examples/webhooks-docker/CONTRIBUTING.md      |  39 +-
 examples/webhooks-docker/LICENSE              |   2 +-
 examples/webhooks-docker/README.md            |   8 +-
 examples/webhooks-docker/app.js               |   2 +-
 examples/webhooks-docker/package.json         |   2 +-
 first-timers.md                               |   6 +-
 package.json                                  |   4 +-
 packages/client/README.md                     |  16 +-
 packages/client/USAGE.md                      | 214 ++--
 packages/client/USE_CASES.md                  |  13 +-
 packages/client/package.json                  |   4 +-
 packages/client/src/classes/client.js         |   2 +-
 packages/contact-importer/README.md           |   6 +-
 packages/contact-importer/package.json        |   4 +-
 packages/contact-importer/src/importer.js     |   2 +-
 .../contact-importer/src/importer.spec.js     |   2 +-
 packages/helpers/README.md                    |   6 +-
 packages/helpers/package.json                 |   4 +-
 packages/inbound-mail-parser/README.md        |  10 +-
 packages/inbound-mail-parser/package.json     |   4 +-
 packages/inbound-mail-parser/src/parser.js    |   4 +-
 .../inbound-mail-parser/src/parser.spec.js    |   2 +-
 packages/mail/README.md                       |  18 +-
 packages/mail/USE_CASES.md                    | 955 +-----------------
 packages/mail/package.json                    |   4 +-
 packages/subscription-widget/README.md        |  16 +-
 packages/subscription-widget/app.json         |   2 +-
 use-cases/README.md                           |   5 +-
 use-cases/domain-white-label.md               |   2 +-
 use-cases/email-stats.md                      |   2 +-
 use-cases/sms.md                              |  57 ++
 36 files changed, 307 insertions(+), 1205 deletions(-)
 create mode 100644 use-cases/sms.md

diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
index cdbed2f7b..9947dba77 100644
--- a/.github/PULL_REQUEST_TEMPLATE
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -1,6 +1,7 @@
 <!--
 We appreciate the effort for this pull request but before that please make sure you read the contribution guidelines given above, then fill out the blanks below.
 
+**All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.**
 
 Please enter each Issue number you are resolving in your PR after one of the following words [Fixes, Closes, Resolves]. This will auto-link these issues and close them when this PR is merged!
 e.g. 
@@ -10,6 +11,7 @@ Closes #2
 # Fixes # 
 
 ### Checklist
+- [ ] I acknowledge that all my contributions will be made under the project's license
 - [ ] 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 development branch.
@@ -21,4 +23,4 @@ Closes #2
 - 
 - 
 
-If you have questions, please send an email to [SendGrid](mailto:dx@sendgrid.com), or file a Github Issue in this repository.
+If you have questions, please send an email to [Twilio SendGrid](mailto:dx@sendgrid.com), or file a Github Issue in this repository.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 27620369f..74a3bc0e3 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,15 +1,15 @@
-# SendGrid Community Code of Conduct
+# Twilio SendGrid Community Code of Conduct
 
-The SendGrid open source community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines, which help steer our interactions and strive to maintain a positive, thriving and growing community.
+The Twilio SendGrid open source community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines, which help steer our interactions and strive to maintain a positive, thriving and growing community.
 
 ### Be Open
 Members of the community are open to collaboration, whether it's on pull requests, code reviews, approvals, issues or otherwise. We're receptive to constructive comments and criticism, as the experiences and skill sets of all members contribute to the whole of our efforts. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate, and everyone can make a difference.
 
 ### Be Considerate
-Members of the community are considerate of their peers, which include other contributors and users of SendGrid. We're thoughtful when addressing the efforts of others, keeping in mind that often the labor was completed with the intent of the good of the community. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
+Members of the community are considerate of their peers, which include other contributors and users of Twilio SendGrid. We're thoughtful when addressing the efforts of others, keeping in mind that often the labor was completed with the intent of the good of the community. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
 
 ### Be Respectful
-Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the SendGrid community. We're respectful of the processes outlined in the community, and we work within them. When we disagree, we are courteous in raising our issues.  Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.
+Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the Twilio SendGrid community. We're respectful of the processes outlined in the community, and we work within them. When we disagree, we are courteous in raising our issues.  Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.
 
 ## Additional Guidance
 
@@ -17,24 +17,24 @@ Members of the community are respectful. We're respectful of others, their posit
 Community discussions often involve interested parties. We expect participants to be aware when they are conflicted due to employment or other projects they are involved in and disclose those interests to other project members. When in doubt, over-disclose. Perceived conflicts of interest are important to address so that the community’s decisions are credible even when unpopular, difficult or favorable to the interests of one group over another.
 
 ### Interpretation
-This Code is not exhaustive or complete. It is not a rulebook; it serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter.  When in doubt, try to abide by [SendGrid’s cultural values](https://sendgrid.com/blog/employee-engagement-the-4h-way) defined by our “4H’s”: Happy, Hungry, Humble and Honest.  
+This Code is not exhaustive or complete. It is not a rulebook; it serves to distill our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter.  When in doubt, try to abide by [Twilio SendGrid’s cultural values](https://sendgrid.com/blog/employee-engagement-the-4h-way) defined by our “4H’s”: Happy, Hungry, Humble and Honest.  
 
 ### Enforcement
-Most members of the SendGrid community always comply with this Code, not because of the existence of this Code, but because they have long experience participating in open source communities where the conduct described above is normal and expected. However, failure to observe this Code may be grounds for suspension, reporting the user for abuse or changing permissions for outside contributors.
+Most members of the Twilio SendGrid community always comply with this Code, not because of the existence of this Code, but because they have long experience participating in open source communities where the conduct described above is normal and expected. However, failure to observe this Code may be grounds for suspension, reporting the user for abuse or changing permissions for outside contributors.
 
 ## If you have concerns about someone’s conduct
 **Initiate Direct Contact** - It is always appropriate to email a community member (if contact information is available), mention that you think their behavior was out of line, and (if necessary) point them to this Code.
 
 **Discuss Publicly** - Discussing publicly is always acceptable. Note, though, that approaching the person directly may be better, as it tends to make them less defensive, and it respects the time of other community members, so you probably want to try direct contact first.
 
-**Contact the Moderators** - You can reach the SendGrid moderators by emailing dx@SendGrid.com.
+**Contact the Moderators** - You can reach the Twilio SendGrid moderators by emailing dx@Twilio SendGrid.com.
 
-## Submission to SendGrid Repositories
-Finally, just a reminder, changes to the SendGrid repositories will only be accepted upon completion of the [SendGrid Contributor Agreement](https://cla.sendgrid.com).
+## Submission to Twilio SendGrid Repositories
+Finally, just a reminder, changes to the Twilio SendGrid repositories will only be accepted upon completion of the [Twilio SendGrid Contributor Agreement](https://cla.sendgrid.com).
 
 ## Attribution
 
-SendGrid thanks the following, on which it draws for content and inspiration:
+Twilio SendGrid thanks the following, on which it draws for content and inspiration:
 
 * [Python Community Code of Conduct](https://www.python.org/psf/codeofconduct/)  
 * [Open Source Initiative General Code of Conduct](https://opensource.org/codeofconduct/licensing)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fa0005716..d50c079a7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,31 +1,27 @@
-Hello! Thank you for choosing to help contribute to one of the SendGrid open source libraries. There are many ways you can contribute and help is always welcome.  We simply ask that you follow the following contribution policies.
+Hello! Thank you for choosing to help contribute to one of the Twilio SendGrid open source libraries. There are many ways you can contribute and help is always welcome.  We simply ask that you follow the following contribution policies.
 
-- [CLAs and CCLAs](#cla)
-- [Roadmap & Milestones](#roadmap)
+**All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.**
 - [Feature Request](#feature-request)
 - [Submit a Bug Report](#submit-a-bug-report)
+  - [Please use our Bug Report Template](#please-use-our-bug-report-template)
 - [Improvements to the Codebase](#improvements-to-the-codebase)
-- [Understanding the Code Base](#understanding-the-codebase)
+  - [Development Environment](#development-environment)
+    - [Install and Run Locally](#install-and-run-locally)
+      - [Prerequisites](#prerequisites)
+      - [Initial setup:](#initial-setup)
+- [Environment Variables](#environment-variables)
+      - [Execute:](#execute)
+- [Understanding the Code Base](#understanding-the-code-base)
 - [Codebase Overview](#codebase-overview)
+    - [Package List](#package-list)
 - [Testing](#testing)
-- [Style Guidelines & Naming Conventions](#style-guidelines-and-naming-conventions)
-- [Creating a Pull Request](#creating-a-pull-request)
+- [Style Guidelines & Naming Conventions](#style-guidelines--naming-conventions)
+- [Creating a Pull Request<a name="creating-a-pull-request"></a>](#creating-a-pull-requesta-name%22creating-a-pull-request%22a)
 - [Code Reviews](#code-reviews)
 
 <a name="roadmap"></a>
 We use [Milestones](https://github.com/sendgrid/sendgrid-nodejs/milestones) to help define current roadmaps, please feel free to grab an issue from the current milestone. Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions, and additional PRs are welcomed and encouraged.
 
-<a name="cla"></a>
-## CLAs and CCLAs
-
-Before you get started, SendGrid requires that a SendGrid Contributor License Agreement (CLA) be filled out by every contributor to a SendGrid open source project.
-
-Our goal with the CLA is to clarify the rights of our contributors and reduce other risks arising from inappropriate contributions.  The CLA also clarifies the rights SendGrid holds in each contribution and helps to avoid misunderstandings over what rights each contributor is required to grant to SendGrid when contributing.  In this way, the CLA encourages broad participation by our open source community and helps us build strong open source projects, free from any individual contributor withholding or revoking rights to any contribution.
-
-SendGrid does not merge a pull request made against a SendGrid open source project until that pull request is associated with a signed CLA. Copies of the CLA are available [here](https://gist.github.com/SendGridDX/98b42c0a5d500058357b80278fde3be8#file-sendgrid_cla).
-
-When you create a Pull Request, after a few seconds, a comment will appear with a link to the CLA. Click the link and fill out the brief form and then click the "I agree" button and you are all set. You will not be asked to re-sign the CLA unless we make a change.
-
 There are a few ways to contribute, which we'll enumerate below:
 
 <a name="feature-request"></a>
@@ -79,9 +75,9 @@ npm install
 
 ## Environment Variables
 
-First, get your free SendGrid account [here](https://sendgrid.com/free?source=sendgrid-nodejs).
+First, get your free Twilio SendGrid account [here](https://sendgrid.com/free?source=sendgrid-nodejs).
 
-You will need to setup the following environment to use the SendGrid examples in the [README](README.md), [USAGE](USAGE.md) and [USE_CASES](use-cases/README.md) files:
+You will need to setup the following environment to use the Twilio SendGrid examples in the [README](README.md), [USAGE](USAGE.md) and [USE_CASES](use-cases/README.md) files:
 
 ```bash
 echo "export SENDGRID_API_KEY='YOUR_API_KEY'" > sendgrid.env
@@ -99,7 +95,7 @@ touch example.js
 
 Copy the desired code into `example.js`. For this example, I'm assuming you create this file in the root of this project.
 
-Change the path to the SendGrid library to the relative path, for example: `./packages/mail/mail`.
+Change the path to the Twilio SendGrid library to the relative path, for example: `./packages/mail/mail`.
 
 ```bash
 node example.js
@@ -123,7 +119,7 @@ npm install or yarn install
 #### Package List
 
 **1. Client**
-This is a  wrapper written on top of the ```request``` module to suite the SendGrid module. All requests made to the SendGrid API are invoked by the `request` function in the `client.js`.
+This is a  wrapper written on top of the ```request``` module to suite the Twilio SendGrid module. All requests made to the Twilio SendGrid API are invoked by the `request` function in the `client.js`.
 
 Type declarations: client.d.ts
 Test Cases: client.spec.js
diff --git a/LICENSE.md b/LICENSE.md
index 331900b06..8c4275724 100644
--- a/LICENSE.md
+++ b/LICENSE.md
@@ -1,4 +1,4 @@
-Copyright (c) 2012-2019 SendGrid, Inc.
+Copyright (c) 2012-2019 Twilio SendGrid, Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
diff --git a/README.md b/README.md
index 3a1fce0e5..9ba1ed7f0 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
 
 [![BuildStatus](https://travis-ci.org/sendgrid/sendgrid-nodejs.svg?branch=master)](https://travis-ci.org/sendgrid/sendgrid-nodejs)
 [![npm version](https://badge.fury.io/js/%40sendgrid%2Fclient.svg)](https://www.npmjs.com/org/sendgrid)
@@ -8,11 +8,11 @@
 [![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/sendgrid/sendgrid-nodejs/blob/master/LICENSE.md)
 [![Open Source Helpers](https://www.codetriage.com/sendgrid/sendgrid-nodejs/badges/users.svg)](https://www.codetriage.com/sendgrid/sendgrid-nodejs)
 
-[SendGrid Docs](https://sendgrid.com/docs/index.html)
+[Twilio SendGrid Docs](https://sendgrid.com/docs/index.html)
 
-**This library allows you to quickly and easily use the SendGrid Web API v3 via Node.js.**
+**This library allows you to quickly and easily use the Twilio SendGrid Web API v3 via Node.js.**
 
-We want this library to be community-driven, and SendGrid led. We need your help to realize this goal. To help make sure we are building the right things in the right order, we ask that you create [issues](https://github.com/sendgrid/sendgrid-nodejs/issues) and [pull requests](https://github.com/sendgrid/sendgrid-nodejs/blob/master/CONTRIBUTING.md) or merely upvote or comment on existing issues or pull requests.
+We want this library to be community-driven, and Twilio SendGrid led. We need your help to realize this goal. To help make sure we are building the right things in the right order, we ask that you create [issues](https://github.com/sendgrid/sendgrid-nodejs/issues) and [pull requests](https://github.com/sendgrid/sendgrid-nodejs/blob/master/CONTRIBUTING.md) or merely upvote or comment on existing issues or pull requests.
 
 For updates to this library, see our [CHANGELOG](https://github.com/sendgrid/sendgrid-nodejs/blob/master/CHANGELOG.md) and [releases](https://github.com/sendgrid/sendgrid-nodejs/releases).
 
@@ -22,13 +22,14 @@ We appreciate your continued support, thank you!
 
 # Table of Contents
 
-* [Introduction - Please Read First](#introduction)
-* [Announcements](#announcements)
-* [Roadmap](#roadmap)
-* [How to Contribute](#contribute)
-* [Troubleshooting](#troubleshooting)
-* [About](#about)
-* [License](#license)
+- [Table of Contents](#table-of-contents)
+- [Introduction - Please Read First](#introduction---please-read-first)
+- [Announcements](#announcements)
+- [Roadmap](#roadmap)
+- [How to Contribute](#how-to-contribute)
+- [Troubleshooting](#troubleshooting)
+- [About](#about)
+- [License](#license)
 
 <a name="introduction"></a>
 # Introduction - Please Read First
@@ -36,10 +37,10 @@ We appreciate your continued support, thank you!
 This library is broken up into several packages as a monorepo so that you only need to install the packages necessary for your use case. This README contains information about all packages. For examples on how to get started quickly, head over to the READMEs of each package (linked and described below), which includes detailed examples.
 
 * **[@sendgrid/mail](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/mail) - if you just want to send email**
-* **[@sendgrid/client](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/client) - to use all other [SendGrid v3 Web API endpoints](https://sendgrid.com/docs/API_Reference/api_v3.html)**
+* **[@sendgrid/client](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/client) - to use all other [Twilio SendGrid v3 Web API endpoints](https://sendgrid.com/docs/API_Reference/api_v3.html)**
 
 
-* [@sendgrid/inbound-mail-parser](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/inbound-mail-parser) - help with parsing the SendGrid Inbound Parse API
+* [@sendgrid/inbound-mail-parser](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/inbound-mail-parser) - help with parsing the Twilio SendGrid Inbound Parse API
 * [@sendgrid/contact-importer](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/contact-importer) - help with importing contacts into the ContactDB
 * [@sendgrid/helpers](https://github.com/sendgrid/sendgrid-nodejs/tree/master/packages/helpers) - a collection of classes and helpers used internally by the above packages
 
@@ -75,11 +76,11 @@ Please see our [troubleshooting guide](https://github.com/sendgrid/sendgrid-node
 <a name="about"></a>
 # About
 
-sendgrid-nodejs is guided and supported by the SendGrid Developer Experience Team.
+sendgrid-nodejs is guided and supported by the Twilio Developer Experience Team.
 
 Please Email the Developer Experience Team [here](mailto:dx@sendgrid.com) in case of any queries.
 
-sendgrid-nodejs is maintained and funded by SendGrid, Inc. The names and logos for sendgrid-nodejs are trademarks of SendGrid, Inc.
+sendgrid-nodejs is maintained and funded by Twilio SendGrid, Inc. The names and logos for sendgrid-nodejs are trademarks of Twilio SendGrid, Inc.
 
 <a name="license"></a>
 # License
diff --git a/examples/webhooks-docker/CONTRIBUTING.md b/examples/webhooks-docker/CONTRIBUTING.md
index 1f531c081..b4b331b67 100644
--- a/examples/webhooks-docker/CONTRIBUTING.md
+++ b/examples/webhooks-docker/CONTRIBUTING.md
@@ -1,31 +1,28 @@
-Hello! Thank you for choosing to help contribute to one of the SendGrid open source libraries. There are many ways you can contribute and help is always welcome.  We simply ask that you follow the following contribution policies.
+Hello! Thank you for choosing to help contribute to one of the Twilio SendGrid open source libraries. There are many ways you can contribute and help is always welcome.  We simply ask that you follow the following contribution policies.
+
+**All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.**
 
-- [CLAs and CCLAs](#cla)
-- [Roadmap & Milestones](#roadmap)
 - [Feature Request](#feature-request)
 - [Submit a Bug Report](#submit-a-bug-report)
+  - [Please use our Bug Report Template](#please-use-our-bug-report-template)
 - [Improvements to the Codebase](#improvements-to-the-codebase)
-- [Understanding the Code Base](#understanding-the-codebase)
+  - [Development Environment](#development-environment)
+    - [Install and Run Locally](#install-and-run-locally)
+      - [Prerequisites](#prerequisites)
+      - [Initial setup:](#initial-setup)
+- [Environment Variables](#environment-variables)
+      - [Execute:](#execute)
+- [Understanding the Code Base](#understanding-the-code-base)
 - [Codebase Overview](#codebase-overview)
+    - [Package List](#package-list)
 - [Testing](#testing)
-- [Style Guidelines & Naming Conventions](#style-guidelines-and-naming-conventions)
-- [Creating a Pull Request](#creating-a-pull-request)
+- [Style Guidelines & Naming Conventions](#style-guidelines--naming-conventions)
+- [Creating a Pull Request<a name="creating-a-pull-request"></a>](#creating-a-pull-requesta-name%22creating-a-pull-request%22a)
 - [Code Reviews](#code-reviews)
 
 <a name="roadmap"></a>
 We use [Milestones](https://github.com/sendgrid/sendgrid-nodejs/milestones) to help define current roadmaps, please feel free to grab an issue from the current milestone. Please indicate that you have begun work on it to avoid collisions. Once a PR is made, community review, comments, suggestions and additional PRs are welcomed and encouraged.
 
-<a name="cla"></a>
-## CLAs and CCLAs
-
-Before you get started, SendGrid requires that a SendGrid Contributor License Agreement (CLA) be filled out by every contributor to a SendGrid open source project.
-
-Our goal with the CLA is to clarify the rights of our contributors and reduce other risks arising from inappropriate contributions.  The CLA also clarifies the rights SendGrid holds in each contribution and helps to avoid misunderstandings over what rights each contributor is required to grant to SendGrid when making a contribution.  In this way the CLA encourages broad participation by our open source community and helps us build strong open source projects, free from any individual contributor withholding or revoking rights to any contribution.
-
-SendGrid does not merge a pull request made against a SendGrid open source project until that pull request is associated with a signed CLA. Copies of the CLA are available [here](https://gist.github.com/SendGridDX/98b42c0a5d500058357b80278fde3be8#file-sendgrid_cla).
-
-When you create a Pull Request, after a few seconds, a comment will appear with a link to the CLA. Click the link and fill out the brief form and then click the "I agree" button and you are all set. You will not be asked to re-sign the CLA unless we make a change.
-
 There are a few ways to contribute, which we'll enumerate below:
 
 <a name="feature-request"></a>
@@ -79,9 +76,9 @@ npm install
 
 ## Environment Variables
 
-First, get your free SendGrid account [here](https://sendgrid.com/free?source=sendgrid-nodejs).
+First, get your free Twilio SendGrid account [here](https://sendgrid.com/free?source=sendgrid-nodejs).
 
-You will need to setup the following environment to use the SendGrid examples in the [README.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/README.md), [USAGE.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/USAGE.MD) and [USE_CASES.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/USE_CASES.md) files:
+You will need to setup the following environment to use the Twilio SendGrid examples in the [README.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/README.md), [USAGE.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/USAGE.MD) and [USE_CASES.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/USE_CASES.md) files:
 
 ```bash
 echo "export SENDGRID_API_KEY='YOUR_API_KEY'" > sendgrid.env
@@ -99,7 +96,7 @@ touch example.js
 
 Copy the desired code into `example.js`. For this example, I'm assuming you create this file in the root of this project.
 
-Change the path to the Sendgrid library to the relative path, for example: `./packages/mail/mail`.
+Change the path to the Twilio Sendgrid library to the relative path, for example: `./packages/mail/mail`.
 
 ```bash
 node example.js
@@ -123,7 +120,7 @@ npm install or yarn install
 #### Package List
 
 **1. Client**
-This is a  wrapper written on top of the ```request``` module to suite the sendgrid module. All requests made to the sendgrid API are invoked by the `request` function in the `client.js`.
+This is a  wrapper written on top of the ```request``` module to suite the `sendgrid` module. All requests made to the Twilio SendGrid API are invoked by the `request` function in the `client.js`.
 
 Type declarations: client.d.ts
 Test Cases: client.spec.js
diff --git a/examples/webhooks-docker/LICENSE b/examples/webhooks-docker/LICENSE
index 8fc986624..f4cba59d8 100644
--- a/examples/webhooks-docker/LICENSE
+++ b/examples/webhooks-docker/LICENSE
@@ -1,4 +1,4 @@
-Copyright (c) 2012-2018 SendGrid, Inc.
+Copyright (c) 2012-2019 Twilio SendGrid, Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
 documentation files (the "Software"), to deal in the Software without restriction, including without limitation
diff --git a/examples/webhooks-docker/README.md b/examples/webhooks-docker/README.md
index 56acbf27b..9b475e46f 100644
--- a/examples/webhooks-docker/README.md
+++ b/examples/webhooks-docker/README.md
@@ -1,14 +1,14 @@
 # Introduction
 
-This is an example project for using a Docker container as a [SendGrid](https://sendgrid.com) [inbound parse email](https://sendgrid.com/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook/) webhooks and [event webhooks](https://sendgrid.com/docs/for-developers/tracking-events/getting-started-event-webhook/)
+This is an example project for using a Docker container as a [Twilio SendGrid](https://sendgrid.com) [inbound parse email](https://sendgrid.com/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook/) webhooks and [event webhooks](https://sendgrid.com/docs/for-developers/tracking-events/getting-started-event-webhook/)
 
 # Prerequisites
 
 * [Docker CE 18](https://www.docker.com/get-started)
 * (Optional for development) A local Kubernetes installation
-* SendGrid Account with inbound parse enabled to send form data (default)
+* Twilio SendGrid Account with inbound parse enabled to send form data (default)
     * [Setup Inbound Parse Webhook](https://sendgrid.com/docs/for-developers/parsing-email/setting-up-the-inbound-parse-webhook/)
-* SendGrid Account with event webhooks enabled
+* Twilio SendGrid Account with event webhooks enabled
     * [Getting Started with Event Webhook](https://sendgrid.com/docs/for-developers/tracking-events/getting-started-event-webhook/)
 * [Ngrok](https://ngrok.com/) or Internet accessible URL
 
@@ -39,7 +39,7 @@ At the moment, the `app.js` only prints data to the console.  You can extend thi
 
 ### Inbound Parse Webhook
 
-The [routes/inbound-parse.js](routes/inbound-parse.js) route uses the [express-formidable](https://github.com/utatti/express-formidable) middleware to process the form data sent by SendGrid's Inbound Parse Webhook.  
+The [routes/inbound-parse.js](routes/inbound-parse.js) route uses the [express-formidable](https://github.com/utatti/express-formidable) middleware to process the form data sent by Twilio SendGrid's Inbound Parse Webhook.  
 
 The events are available in the `/parse_webhook` route in the `req.fields` object.  The [app.js](app.js) contains logging statements for the elements that are available to you.  It may be useful to review the [example-webhook-payload.txt](example-webhook-payload.txt) for what the form data looks like when extending this application.
 
diff --git a/examples/webhooks-docker/app.js b/examples/webhooks-docker/app.js
index 13c1c6f72..e53ef5203 100644
--- a/examples/webhooks-docker/app.js
+++ b/examples/webhooks-docker/app.js
@@ -11,4 +11,4 @@ app.use('/event_webhook', eventWebhook)
 app.use('/parse_webhook', parseWebhook)
 
 
-app.listen(port, () => console.log(`SendGrid webhook listener started on port ${port}!`))
\ No newline at end of file
+app.listen(port, () => console.log(`Twilio SendGrid webhook listener started on port ${port}!`))
\ No newline at end of file
diff --git a/examples/webhooks-docker/package.json b/examples/webhooks-docker/package.json
index f863f6082..099e0154e 100644
--- a/examples/webhooks-docker/package.json
+++ b/examples/webhooks-docker/package.json
@@ -1,7 +1,7 @@
 {
   "name": "inbound-parse-docker",
   "version": "1.0.0",
-  "description": "A containter to capture webhook data from SendGrid inbound parse",
+  "description": "A containter to capture webhook data from Twilio SendGrid inbound parse",
   "main": "app.js",
   "dependencies": {
     "body-parser": "^1.18.3",
diff --git a/first-timers.md b/first-timers.md
index 94bd1e8a2..483ca0ac0 100644
--- a/first-timers.md
+++ b/first-timers.md
@@ -1,7 +1,7 @@
-# How To Contribute to SendGrid Repositories via GitHub
- Contributing to the SendGrid is easy! All you need to do is find an open issue (see the bottom of this page for a list of repositories containing open issues), fix it and submit a pull request. Once you have submitted your pull request, the team can easily review it before it is merged into the repository.
+# How To Contribute to Twilio SendGrid Repositories via GitHub
+ Contributing to the Twilio SendGrid is easy! All you need to do is find an open issue (see the bottom of this page for a list of repositories containing open issues), fix it and submit a pull request. Once you have submitted your pull request, the team can easily review it before it is merged into the repository.
  To make a pull request, follow these steps:
- 1. Log into GitHub. If you do not already have a GitHub account, you will have to create one in order to submit a change. Click the Sign up link in the upper right-hand corner to create an account. Enter your username, password, and email address. If you are an employee of SendGrid, please use your full name with your GitHub account and enter SendGrid as your company so we can easily identify you.
+ 1. Log into GitHub. If you do not already have a GitHub account, you will have to create one in order to submit a change. Click the Sign up link in the upper right-hand corner to create an account. Enter your username, password, and email address. If you are an employee of Twilio SendGrid, please use your full name with your GitHub account and enter Twilio SendGrid as your company so we can easily identify you.
 
 <img src="/static/img/github-sign-up.png" width="800">
 
diff --git a/package.json b/package.json
index 1cf0dbc46..e34db77d4 100644
--- a/package.json
+++ b/package.json
@@ -41,7 +41,7 @@
     "test": "npm run test:all -s",
     "coverage": "open -a \"Google Chrome\" ./coverage/lcov-report/index.html"
   },
-  "description": "![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)",
+  "description": "![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)",
   "bugs": {
     "url": "https://github.com/sendgrid/sendgrid-nodejs/issues"
   },
@@ -57,5 +57,5 @@
     "esdoc-coverage-plugin": "^1.1.0",
     "esdoc-type-inference-plugin": "^1.0.1"
   },
-  "author": "SendGrid"
+  "author": "Twilio SendGrid"
 }
diff --git a/packages/client/README.md b/packages/client/README.md
index 4d04fefe1..3f2a09f7e 100644
--- a/packages/client/README.md
+++ b/packages/client/README.md
@@ -5,7 +5,7 @@
 **This package is part of a monorepo, please see [this README](https://github.com/sendgrid/sendgrid-nodejs/blob/master/README.md) for details.**
 
 # Client for the Sendgrid v3 Web API
-This client library is used by the other [SendGrid service packages](https://www.npmjs.com/org/sendgrid) to make requests to the [Sendgrid v3 Web API](https://sendgrid.com/docs/API_Reference/api_v3.html). You can also use it independently to make custom requests to the SendGrid v3 Web API and other HTTP APIs.
+This client library is used by the other [Twilio SendGrid service packages](https://www.npmjs.com/org/sendgrid) to make requests to the [Twilio SendGrid v3 Web API](https://sendgrid.com/docs/API_Reference/api_v3.html). You can also use it independently to make custom requests to the Twilio SendGrid v3 Web API and other HTTP APIs.
 
 To be notified when this package is updated, please subscribe to email [notifications](https://dx.sendgrid.com/newsletter/nodejs) for releases and breaking changes.
 
@@ -14,15 +14,15 @@ To be notified when this package is updated, please subscribe to email [notifica
 ## Prerequisites
 
 - Node.js version 6, 7 or 8
-- A SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
+- A Twilio SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
 
 ## Obtain an API Key
 
-Grab your API Key from the [SendGrid UI](https://app.sendgrid.com/settings/api_keys).
+Grab your API Key from the [Twilio SendGrid UI](https://app.sendgrid.com/settings/api_keys).
 
 ## Setup Environment Variables
 
-Do not hardcode your [SendGrid API Key](https://app.sendgrid.com/settings/api_keys) into your code. Instead, use an environment variable or some other secure means of protecting your SendGrid API Key. Following is an example of using an environment variable.
+Do not hardcode your [Twilio SendGrid API Key](https://app.sendgrid.com/settings/api_keys) into your code. Instead, use an environment variable or some other secure means of protecting your Twilio SendGrid API Key. Following is an example of using an environment variable.
 
 Update the development environment with your [SENDGRID_API_KEY](https://app.sendgrid.com/settings/api_keys), for example:
 
@@ -49,7 +49,7 @@ yarn add @sendgrid/client
 <a name="general"></a>
 ## General v3 Web API Usage Example
 
-Please see [USAGE.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md) for all endpoint examples for the [SendGrid v3 Web API](https://sendgrid.com/docs/API_Reference/api_v3.html).
+Please see [USAGE.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md) for all endpoint examples for the [Twilio SendGrid v3 Web API](https://sendgrid.com/docs/API_Reference/api_v3.html).
 
 ```js
 const client = require('@sendgrid/client');
@@ -118,8 +118,8 @@ Please see our [troubleshooting guide](https://github.com/sendgrid/sendgrid-node
 <a name="about"></a>
 # About
 
-@sendgrid/client is guided and supported by the SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
+@sendgrid/client is guided and supported by the Twilio SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
 
-@sendgrid/client is maintained and funded by SendGrid, Inc. The names and logos for @sendgrid/client are trademarks of SendGrid, Inc.
+@sendgrid/client is maintained and funded by Twilio SendGrid, Inc. The names and logos for @sendgrid/client are trademarks of Twilio SendGrid, Inc.
 
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
diff --git a/packages/client/USAGE.md b/packages/client/USAGE.md
index a78734d2b..99c539b3b 100644
--- a/packages/client/USAGE.md
+++ b/packages/client/USAGE.md
@@ -330,7 +330,7 @@ A JSON request body containing a "name" property is required. If the number of m
 
 There is a limit of 100 API Keys on your account.
 
-The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the Twilio SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 See the [API Key Permissions List](https://sendgrid.com/docs/API_Reference/Web_API_v3/API_Keys/api_key_permissions_list.html) for a list of all available scopes.
 
@@ -360,7 +360,7 @@ See the [API Key Permissions List](https://sendgrid.com/docs/API_Reference/Web_A
 
 **This endpoint allows you to retrieve all API Keys that belong to the authenticated user.**
 
-The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the Twilio SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 ### GET /api_keys
 
@@ -385,7 +385,7 @@ The API Keys feature allows customers to be able to generate an API Key credenti
 A JSON request body with a "name" property is required.
 Most provide the list of all the scopes an API key should have.
 
-The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the Twilio SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 ### PUT /api_keys/{api_key_id}
 
@@ -413,7 +413,7 @@ The API Keys feature allows customers to be able to generate an API Key credenti
 
 A JSON request body with a "name" property is required.
 
-The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the Twilio SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 ## URI Parameters
 
@@ -443,7 +443,7 @@ The API Keys feature allows customers to be able to generate an API Key credenti
 
 Authentications using this API Key will fail after this request is made, with some small propagation delay. If the API Key ID does not exist an HTTP 404 will be returned.
 
-The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+The API Keys feature allows customers to be able to generate an API Key credential which can be used for authentication with the Twilio SendGrid v3 Web API or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 ## URI Parameters
 
@@ -1306,7 +1306,7 @@ Advanced Stats provide a more in-depth view of your email statistics and the act
 
 **This endpoint allows you to create a custom field.**
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### POST /contactdb/custom_fields
 
@@ -1329,7 +1329,7 @@ The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](
 
 **This endpoint allows you to retrieve all custom fields.** 
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### GET /contactdb/custom_fields
 
@@ -1347,7 +1347,7 @@ The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](
 
 **This endpoint allows you to delete a custom field by ID.**
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### DELETE /contactdb/custom_fields/{custom_field_id}
 
@@ -1365,7 +1365,7 @@ The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](
 
 **This endpoint allows you to retrieve a custom field by ID.**
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### GET /contactdb/custom_fields/{custom_field_id}
 
@@ -1609,7 +1609,7 @@ The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.co
 
 **This endpoint allows you to add a Marketing Campaigns recipient.**
 
-You can add custom field data as a parameter on this endpoint. We have provided an example using some of the default custom fields SendGrid provides.
+You can add custom field data as a parameter on this endpoint. We have provided an example using some of the default custom fields Twilio SendGrid provides.
 
 The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html) recipients.
 
@@ -1646,7 +1646,7 @@ The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.co
 
 The body of an API call to this endpoint must include an array of recipient IDs of the recipients you want to delete.
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### DELETE /contactdb/recipients
 
@@ -1697,9 +1697,9 @@ The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.co
 
 The body of an API call to this endpoint must include an array of one or more recipient objects.
 
-It is of note that you can add custom field data as parameters on recipient objects. We have provided an example using some of the default custom fields SendGrid provides.
+It is of note that you can add custom field data as parameters on recipient objects. We have provided an example using some of the default custom fields Twilio SendGrid provides.
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### PATCH /contactdb/recipients
 
@@ -1745,7 +1745,7 @@ The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.co
 
 **This endpoint allows you to retrieve the total number of Marketing Campaigns recipients.**
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### GET /contactdb/recipients/count
 
@@ -1772,7 +1772,7 @@ your epoch time to a date range encompassing the entire day. For example, an epo
 Mon, 02 Feb 2015 00:06:40 GMT, but internally the system will search from Mon, 02 Feb 2015 00:00:00 GMT through
 Mon, 02 Feb 2015 23:59:59 GMT.
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### GET /contactdb/recipients/search
 
@@ -1850,7 +1850,7 @@ The Contacts API helps you manage your [Marketing Campaigns](https://sendgrid.co
 
 **This endpoint allows you to list all fields that are reserved and can't be used for custom field names.**
 
-The contactdb is a database of your contacts for [SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
+The contactdb is a database of your contacts for [Twilio SendGrid Marketing Campaigns](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/index.html).
 
 ### GET /contactdb/reserved_fields
 
@@ -2229,7 +2229,7 @@ A single IP address or a range of IP addresses may be dedicated to an account to
 
 **Each user can create up to 10 different IP pools.**
 
-IP Pools allow you to group your dedicated SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
+IP Pools allow you to group your dedicated Twilio SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
 
 IP pools can only be used with whitelabeled IP addresses.
 
@@ -2255,7 +2255,7 @@ If an IP pool is NOT specified for an email, it will use any IP available, inclu
 
 **This endpoint allows you to retrieve all of your IP pools.**
 
-IP Pools allow you to group your dedicated SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
+IP Pools allow you to group your dedicated Twilio SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
 
 IP pools can only be used with whitelabeled IP addresses.
 
@@ -2277,7 +2277,7 @@ If an IP pool is NOT specified for an email, it will use any IP available, inclu
 
 **This endpoint allows you to update the name of an IP pool.**
 
-IP Pools allow you to group your dedicated SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
+IP Pools allow you to group your dedicated Twilio SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
 
 IP pools can only be used with whitelabeled IP addresses.
 
@@ -2303,7 +2303,7 @@ If an IP pool is NOT specified for an email, it will use any IP available, inclu
 
 **This endpoint allows you to delete an IP pool.**
 
-IP Pools allow you to group your dedicated SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
+IP Pools allow you to group your dedicated Twilio SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
 
 IP pools can only be used with whitelabeled IP addresses.
 
@@ -2325,7 +2325,7 @@ If an IP pool is NOT specified for an email, it will use any IP available, inclu
 
 **This endpoint allows you to list all of the IP addresses that are in a specific IP pool.**
 
-IP Pools allow you to group your dedicated SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
+IP Pools allow you to group your dedicated Twilio SendGrid IP addresses. For example, you could create separate pools for your transactional and marketing email. When sending marketing emails, specify that you want to use the marketing IP pool. This allows you to maintain separate reputations for your different email traffic.
 
 IP pools can only be used with whitelabeled IP addresses.
 
@@ -2407,7 +2407,7 @@ This endpoint gets the amount of IP Addresses that can still be created during a
 
 **This endpoint allows you to enter an IP address into warmup mode.**
 
-SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how SendGrid limits your email traffic for IPs in warmup.
+Twilio SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how Twilio SendGrid limits your email traffic for IPs in warmup.
 
 For more general information about warming up IPs, please see our [Classroom](https://sendgrid.com/docs/Classroom/Deliver/Delivery_Introduction/warming_up_ips.html).
 
@@ -2431,7 +2431,7 @@ For more general information about warming up IPs, please see our [Classroom](ht
 
 **This endpoint allows you to retrieve all of your IP addresses that are currently warming up.**
 
-SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how SendGrid limits your email traffic for IPs in warmup.
+Twilio SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how Twilio SendGrid limits your email traffic for IPs in warmup.
 
 For more general information about warming up IPs, please see our [Classroom](https://sendgrid.com/docs/Classroom/Deliver/Delivery_Introduction/warming_up_ips.html).
 
@@ -2451,7 +2451,7 @@ For more general information about warming up IPs, please see our [Classroom](ht
 
 **This endpoint allows you to remove an IP address from warmup mode.**
 
-SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how SendGrid limits your email traffic for IPs in warmup.
+Twilio SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how Twilio SendGrid limits your email traffic for IPs in warmup.
 
 For more general information about warming up IPs, please see our [Classroom](https://sendgrid.com/docs/Classroom/Deliver/Delivery_Introduction/warming_up_ips.html).
 
@@ -2471,7 +2471,7 @@ For more general information about warming up IPs, please see our [Classroom](ht
 
 **This endpoint allows you to retrieve the warmup status for a specific IP address.**
 
-SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how SendGrid limits your email traffic for IPs in warmup.
+Twilio SendGrid can automatically warm up dedicated IP addresses by limiting the amount of mail that can be sent through them per hour, with the limit determined by how long the IP address has been in warmup. See the [warmup schedule](https://sendgrid.com/docs/API_Reference/Web_API_v3/IP_Management/ip_warmup_schedule.html) for more details on how Twilio SendGrid limits your email traffic for IPs in warmup.
 
 For more general information about warming up IPs, please see our [Classroom](https://sendgrid.com/docs/Classroom/Deliver/Delivery_Introduction/warming_up_ips.html).
 
@@ -2556,12 +2556,12 @@ More Information:
 ```
 ## v3 Mail Send
 
-This endpoint allows you to send an email over SendGrids v3 Web API, the most recent version of our API. If you are looking for documentation about the v2 Mail Send endpoint, please see our [v2 API Reference](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
+This endpoint allows you to send an email over Twilio SendGrid's v3 Web API, the most recent version of our API. If you are looking for documentation about the v2 Mail Send endpoint, please see our [v2 API Reference](https://sendgrid.com/docs/API_Reference/Web_API/mail.html).
 
 * Top level parameters are referred to as "global".
 * Individual fields within the personalizations array will override any other global, or message level, parameters that are defined outside of personalizations.
  
-**SendGrid provides libraries to help you quickly and easily integrate with the v3 Web API in 7 different languages: [C#](https://github.com/sendgrid/sendgrid-csharp), [Go](https://github.com/sendgrid/sendgrid-go), [Java](https://github.com/sendgrid/sendgrid-java), [Node JS](https://github.com/sendgrid/sendgrid-nodejs), [PHP](https://github.com/sendgrid/sendgrid-php), [Python](https://github.com/sendgrid/sendgrid-python), and [Ruby](https://github.com/sendgrid/sendgrid-ruby).**
+**Twilio SendGrid provides libraries to help you quickly and easily integrate with the v3 Web API in 7 different languages: [C#](https://github.com/sendgrid/sendgrid-csharp), [Go](https://github.com/sendgrid/sendgrid-go), [Java](https://github.com/sendgrid/sendgrid-java), [Node JS](https://github.com/sendgrid/sendgrid-nodejs), [PHP](https://github.com/sendgrid/sendgrid-php), [Python](https://github.com/sendgrid/sendgrid-python), and [Ruby](https://github.com/sendgrid/sendgrid-ruby).**
 
 
 For more detailed information about how to use the v3 Mail Send endpoint, please visit our [Classroom](https://sendgrid.com/docs/Classroom/Send/v3_Mail_Send/index.html).
@@ -2615,7 +2615,7 @@ For more detailed information about how to use the v3 Mail Send endpoint, please
 
 **This endpoint allows you to retrieve a list of all mail settings.**
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings
 
@@ -2640,7 +2640,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The address whitelist setting whitelists a specified email address or domain for which mail should never be suppressed. For example, you own the domain example.com, and one or more of your recipients use email@example.com addresses, by placing example.com in the address whitelist setting, all bounces, blocks, and unsubscribes logged for that domain will be ignored and sent as if under normal sending conditions.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/address_whitelist
 
@@ -2668,7 +2668,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The address whitelist setting whitelists a specified email address or domain for which mail should never be suppressed. For example, you own the domain example.com, and one or more of your recipients use email@example.com addresses, by placing example.com in the address whitelist setting, all bounces, blocks, and unsubscribes logged for that domain will be ignored and sent as if under normal sending conditions.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/address_whitelist
 
@@ -2686,9 +2686,9 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 **This endpoint allows you to update your current BCC mail settings.**
 
-When the BCC mail setting is enabled, SendGrid will automatically send a blind carbon copy (BCC) to an address for every email sent without adding that address to the header. Please note that only one email address may be entered in this field if you wish to distribute BCCs to multiple addresses you will need to create a distribution group or use forwarding rules.
+When the BCC mail setting is enabled, Twilio SendGrid will automatically send a blind carbon copy (BCC) to an address for every email sent without adding that address to the header. Please note that only one email address may be entered in this field if you wish to distribute BCCs to multiple addresses you will need to create a distribution group or use forwarding rules.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/bcc
 
@@ -2711,9 +2711,9 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 **This endpoint allows you to retrieve your current BCC mail settings.**
 
-When the BCC mail setting is enabled, SendGrid will automatically send a blind carbon copy (BCC) to an address for every email sent without adding that address to the header. Please note that only one email address may be entered in this field if you wish to distribute BCCs to multiple addresses you will need to create a distribution group or use forwarding rules.
+When the BCC mail setting is enabled, Twilio SendGrid will automatically send a blind carbon copy (BCC) to an address for every email sent without adding that address to the header. Please note that only one email address may be entered in this field if you wish to distribute BCCs to multiple addresses you will need to create a distribution group or use forwarding rules.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/bcc
 
@@ -2731,9 +2731,9 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 **This endpoint allows you to update your current bounce purge settings.**
 
-This setting allows you to set a schedule for SendGrid to automatically delete contacts from your soft and hard bounce suppression lists.
+This setting allows you to set a schedule for Twilio SendGrid to automatically delete contacts from your soft and hard bounce suppression lists.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/bounce_purge
 
@@ -2757,9 +2757,9 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 **This endpoint allows you to retrieve your current bounce purge settings.**
 
-This setting allows you to set a schedule for SendGrid to automatically delete contacts from your soft and hard bounce suppression lists.
+This setting allows you to set a schedule for Twilio SendGrid to automatically delete contacts from your soft and hard bounce suppression lists.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/bounce_purge
 
@@ -2779,7 +2779,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The footer setting will insert a custom footer at the bottom of the text and HTML bodies. Use the embedded HTML editor and plain text entry fields to create the content of the footers to be inserted into your emails.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/footer
 
@@ -2805,7 +2805,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The footer setting will insert a custom footer at the bottom of the text and HTML bodies. Use the embedded HTML editor and plain text entry fields to create the content of the footers to be inserted into your emails.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/footer
 
@@ -2825,7 +2825,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 Activating this setting allows you to specify an email address to which bounce reports are forwarded.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/forward_bounce
 
@@ -2850,7 +2850,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 Activating this setting allows you to specify an email address to which bounce reports are forwarded.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/forward_bounce
 
@@ -2870,7 +2870,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 Enabling the forward spam setting allows you to specify an email address to which spam reports will be forwarded.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/forward_spam
 
@@ -2895,7 +2895,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 Enabling the forward spam setting allows you to specify an email address to which spam reports will be forwarded.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/forward_spam
 
@@ -2915,7 +2915,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The plain content setting will automatically convert any plain text emails that you send to HTML before sending.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/plain_content
 
@@ -2939,7 +2939,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The plain content setting will automatically convert any plain text emails that you send to HTML before sending.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/plain_content
 
@@ -2959,7 +2959,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The spam checker filter notifies you when emails are detected that exceed a predefined spam threshold.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/spam_check
 
@@ -2985,7 +2985,7 @@ Mail settings allow you to tell SendGrid specific things to do to every email th
 
 The spam checker filter notifies you when emails are detected that exceed a predefined spam threshold.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/spam_check
 
@@ -3007,7 +3007,7 @@ This setting refers to our original email templates. We currently support more f
 
 The legacy email template setting wraps an HTML template around your email content. This can be useful for sending out marketing email and/or other HTML formatted messages.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### PATCH /mail_settings/template
 
@@ -3034,7 +3034,7 @@ This setting refers to our original email templates. We currently support more f
 
 The legacy email template setting wraps an HTML template around your email content. This can be useful for sending out marketing email and/or other HTML formatted messages.
 
-Mail settings allow you to tell SendGrid specific things to do to every email that you send to your recipients over SendGrids [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
+Mail settings allow you to tell Twilio SendGrid specific things to do to every email that you send to your recipients over Twilio SendGrid's [Web API](https://sendgrid.com/docs/API_Reference/Web_API/mail.html) or [SMTP Relay](https://sendgrid.com/docs/API_Reference/SMTP_API/index.html).
 
 ### GET /mail_settings/template
 
@@ -3189,7 +3189,7 @@ For a tutorial on how to get started, check out [Getting Started with the Email
     <td><code>unique_args%3D%22example%20argument%22</code></td>
   </tr>
   <tr>
-    <td><code>outbound_ip</code> - this is the SendGrid dedicated IP address used to send the email</td>
+    <td><code>outbound_ip</code> - this is the Twilio SendGrid dedicated IP address used to send the email</td>
     <td><code>outbound_ip="4.77.777.77"</code></td>
     <td><code>outbound_ip%3D%224.77.777.77%22</code></td>
   </tr>
@@ -3306,7 +3306,7 @@ The CSV fill contain the last 1 million messages. This endpoint will be rate lim
 
 **This endpoint allows you to retrieve a list of all partner settings that you can enable.**
 
-Our partner settings allow you to integrate your SendGrid account with our partners to increase your SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
+Our partner settings allow you to integrate your Twilio SendGrid account with our partners to increase your Twilio SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
 
 ### GET /partner_settings
 
@@ -3329,9 +3329,9 @@ Our partner settings allow you to integrate your SendGrid account with our partn
 
 **This endpoint allows you to update or change your New Relic partner settings.**
 
-Our partner settings allow you to integrate your SendGrid account with our partners to increase your SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
+Our partner settings allow you to integrate your Twilio SendGrid account with our partners to increase your Twilio SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
 
-By integrating with New Relic, you can send your SendGrid email statistics to your New Relic Dashboard. If you enable this setting, your stats will be sent to New Relic every 5 minutes. You will need your New Relic License Key to enable this setting. For more information, please see our [Classroom](https://sendgrid.com/docs/Classroom/Track/Collecting_Data/new_relic.html).
+By integrating with New Relic, you can send your Twilio SendGrid email statistics to your New Relic Dashboard. If you enable this setting, your stats will be sent to New Relic every 5 minutes. You will need your New Relic License Key to enable this setting. For more information, please see our [Classroom](https://sendgrid.com/docs/Classroom/Track/Collecting_Data/new_relic.html).
 
 ### PATCH /partner_settings/new_relic
 
@@ -3355,9 +3355,9 @@ By integrating with New Relic, you can send your SendGrid email statistics to yo
 
 **This endpoint allows you to retrieve your current New Relic partner settings.**
 
-Our partner settings allow you to integrate your SendGrid account with our partners to increase your SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
+Our partner settings allow you to integrate your Twilio SendGrid account with our partners to increase your Twilio SendGrid experience and functionality. For more information about our partners, and how you can begin integrating with them, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/partners.html).
 
-By integrating with New Relic, you can send your SendGrid email statistics to your New Relic Dashboard. If you enable this setting, your stats will be sent to New Relic every 5 minutes. You will need your New Relic License Key to enable this setting. For more information, please see our [Classroom](https://sendgrid.com/docs/Classroom/Track/Collecting_Data/new_relic.html).
+By integrating with New Relic, you can send your Twilio SendGrid email statistics to your New Relic Dashboard. If you enable this setting, your stats will be sent to New Relic every 5 minutes. You will need your New Relic License Key to enable this setting. For more information, please see our [Classroom](https://sendgrid.com/docs/Classroom/Track/Collecting_Data/new_relic.html).
 
 ### GET /partner_settings/new_relic
 
@@ -3378,7 +3378,7 @@ By integrating with New Relic, you can send your SendGrid email statistics to yo
 
 **This endpoint returns a list of all scopes that this user has access to.**
 
-API Keys can be used to authenticate the use of [SendGrids v3 Web API](https://sendgrid.com/docs/API_Reference/Web_API_v3/index.html), or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html). API Keys may be assigned specific permissions, or scopes, that limit which API endpoints they can access. For a more detailed explanation of how you can use API Key permissions, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/api_keys.html#-API-Key-Permissions) or [Classroom](https://sendgrid.com/docs/Classroom/Basics/API/api_key_permissions.html).
+API Keys can be used to authenticate the use of [Twilio SendGrid's v3 Web API](https://sendgrid.com/docs/API_Reference/Web_API_v3/index.html), or the [Mail API Endpoint](https://sendgrid.com/docs/API_Reference/Web_API/mail.html). API Keys may be assigned specific permissions, or scopes, that limit which API endpoints they can access. For a more detailed explanation of how you can use API Key permissions, please visit our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/api_keys.html#-API-Key-Permissions) or [Classroom](https://sendgrid.com/docs/Classroom/Basics/API/api_key_permissions.html).
 
 ### GET /scopes
 
@@ -4320,7 +4320,7 @@ There are two options for deleting spam reports:
 1) You can delete all spam reports by setting "delete_all" to true in the request body. 
 2) You can delete some spam reports by specifying the email addresses in an array in the request body.
 
-[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to SendGrid.
+[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to Twilio SendGrid.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Suppressions/spam_reports.html).
 
@@ -4348,7 +4348,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/User
 
 **This endpoint allows you to retrieve all spam reports.**
 
-[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to SendGrid.
+[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to Twilio SendGrid.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Suppressions/spam_reports.html).
 
@@ -4375,7 +4375,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/User
 
 **This endpoint allows you to delete a specific spam report.**
 
-[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to SendGrid.
+[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to Twilio SendGrid.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Suppressions/spam_reports.html).
 
@@ -4395,7 +4395,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/User
 
 **This endpoint allows you to retrieve a specific spam report.**
 
-[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to SendGrid.
+[Spam reports](https://sendgrid.com/docs/Glossary/spam_reports.html) happen when a recipient indicates that they think your email is [spam](https://sendgrid.com/docs/Glossary/spam.html) and then their email provider reports this to Twilio SendGrid.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Suppressions/spam_reports.html).
 
@@ -5020,7 +5020,7 @@ For more information about tracking, please see our [User Guide](https://sendgri
 
 **This endpoint allows you to update your current settings for open tracking.**
 
-Open Tracking adds an invisible image at the end of the email which can track email opens. If the email recipient has images enabled on their email client, a request to SendGrids server for the invisible image is executed and an open event is logged. These events are logged in the Statistics portal, Email Activity interface, and reported by the Event Webhook.
+Open Tracking adds an invisible image at the end of the email which can track email opens. If the email recipient has images enabled on their email client, a request to Twilio SendGrid's server for the invisible image is executed and an open event is logged. These events are logged in the Statistics portal, Email Activity interface, and reported by the Event Webhook.
 
 You can track a variety of the actions your recipients may take when interacting with your emails including opening your emails, clicking on links in your emails, and subscribing to (or unsubscribing from) your emails.
 
@@ -5046,7 +5046,7 @@ For more information about tracking, please see our [User Guide](https://sendgri
 
 **This endpoint allows you to retrieve your current settings for open tracking.**
 
-Open Tracking adds an invisible image at the end of the email which can track email opens. If the email recipient has images enabled on their email client, a request to SendGrids server for the invisible image is executed and an open event is logged. These events are logged in the Statistics portal, Email Activity interface, and reported by the Event Webhook.
+Open Tracking adds an invisible image at the end of the email which can track email opens. If the email recipient has images enabled on their email client, a request to Twilio SendGrid's server for the invisible image is executed and an open event is logged. These events are logged in the Statistics portal, Email Activity interface, and reported by the Event Webhook.
 
 You can track a variety of the actions your recipients may take when interacting with your emails including opening your emails, clicking on links in your emails, and subscribing to (or unsubscribing from) your emails.
 
@@ -5126,11 +5126,11 @@ For more information about tracking, please see our [User Guide](https://sendgri
 
 Your user's account information includes the user's account type and reputation.
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### GET /user/account
 
@@ -5166,11 +5166,11 @@ Your monthly credit allotment limits the number of emails you may send before in
 
 **This endpoint allows you to update the email address currently on file for your account.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### PUT /user/email
 
@@ -5192,11 +5192,11 @@ For more information about your user profile:
 
 **This endpoint allows you to retrieve the email address currently on file for your account.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### GET /user/email
 
@@ -5214,11 +5214,11 @@ For more information about your user profile:
 
 **This endpoint allows you to update your password.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### PUT /user/password
 
@@ -5241,11 +5241,11 @@ For more information about your user profile:
 
 **This endpoint allows you to update your current profile details.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 It should be noted that any one or more of the parameters can be updated via the PATCH /user/profile endpoint. The only requirement is that you include at least one when you PATCH.
 
@@ -5269,11 +5269,11 @@ It should be noted that any one or more of the parameters can be updated via the
 ```
 ## Get a user's profile
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### GET /user/profile
 
@@ -5438,11 +5438,11 @@ The Enforced TLS settings specify whether or not the recipient is required to su
 
 **This endpoint allows you to update the username for your account.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### PUT /user/username
 
@@ -5464,11 +5464,11 @@ For more information about your user profile:
 
 **This endpoint allows you to retrieve your current account username.**
 
-Keeping your user profile up to date is essential. This will help SendGrid to verify who you are as well as contact you should we need to.
+Keeping your user profile up to date is essential. This will help Twilio SendGrid to verify who you are as well as contact you should we need to.
 
 For more information about your user profile:
 
-* [SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
+* [Twilio SendGrid Account Settings](https://sendgrid.com/docs/User_Guide/Settings/account.html)
 
 ### GET /user/username
 
@@ -5488,7 +5488,7 @@ For more information about your user profile:
 
 If an event type is marked as `true`, then the event webhook will include information about that event.
 
-SendGrids Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as SendGrid processes your email.
+Twilio SendGrid's Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as Twilio SendGrid processes your email.
 
 Typical uses of this data are to remove unsubscribes, react to spam reports, determine unengaged recipients, identify bounced email addresses, or create advanced analytics of your email program.
 
@@ -5526,7 +5526,7 @@ Typical uses of this data are to remove unsubscribes, react to spam reports, det
 
 If an event type is marked as `true`, then the event webhook will include information about that event.
 
-SendGrids Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as SendGrid processes your email.
+Twilio SendGrid's Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as Twilio SendGrid processes your email.
 
 Typical uses of this data are to remove unsubscribes, react to spam reports, determine unengaged recipients, identify bounced email addresses, or create advanced analytics of your email program.
 
@@ -5546,7 +5546,7 @@ Typical uses of this data are to remove unsubscribes, react to spam reports, det
 
 **This endpoint allows you to test your event webhook by sending a fake event notification post to the provided URL.**
 
-SendGrids Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as SendGrid processes your email.
+Twilio SendGrid's Event Webhook will notify a URL of your choice via HTTP POST with information about events that occur as Twilio SendGrid processes your email.
 
 Typical uses of this data are to remove unsubscribes, react to spam reports, determine unengaged recipients, identify bounced email addresses, or create advanced analytics of your email program.
 
@@ -5570,7 +5570,7 @@ Typical uses of this data are to remove unsubscribes, react to spam reports, det
 
 **This endpoint allows you to create a new inbound parse setting.**
 
-The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
+The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by Twilio SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
 
 ### POST /user/webhooks/parse/settings
 
@@ -5595,7 +5595,7 @@ The inbound parse webhook allows you to have incoming emails parsed, extracting
 
 **This endpoint allows you to retrieve all of your current inbound parse settings.**
 
-The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
+The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by Twilio SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
 
 ### GET /user/webhooks/parse/settings
 
@@ -5613,7 +5613,7 @@ The inbound parse webhook allows you to have incoming emails parsed, extracting
 
 **This endpoint allows you to delete a specific inbound parse setting.**
 
-The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
+The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by Twilio SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
 
 ### DELETE /user/webhooks/parse/settings/{hostname}
 
@@ -5631,7 +5631,7 @@ The inbound parse webhook allows you to have incoming emails parsed, extracting
 
 **This endpoint allows you to update a specific inbound parse setting.**
 
-The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
+The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by Twilio SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
 
 ### PATCH /user/webhooks/parse/settings/{hostname}
 
@@ -5655,7 +5655,7 @@ The inbound parse webhook allows you to have incoming emails parsed, extracting
 
 **This endpoint allows you to retrieve a specific inbound parse setting.**
 
-The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
+The inbound parse webhook allows you to have incoming emails parsed, extracting some or all of the content, and then have that content POSTed by Twilio SendGrid to a URL of your choosing. For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Webhooks/parse.html).
 
 ### GET /user/webhooks/parse/settings/{hostname}
 
@@ -5673,9 +5673,9 @@ The inbound parse webhook allows you to have incoming emails parsed, extracting
 
 **This endpoint allows you to retrieve the statistics for your Parse Webhook usage.**
 
-SendGrid's Inbound Parse Webhook allows you to parse the contents and attachments of incoming emails. The Parse API can then POST the parsed emails to a URL that you specify. The Inbound Parse Webhook cannot parse messages greater than 20MB in size, including all attachments.
+Twilio SendGrid's Inbound Parse Webhook allows you to parse the contents and attachments of incoming emails. The Parse API can then POST the parsed emails to a URL that you specify. The Inbound Parse Webhook cannot parse messages greater than 20MB in size, including all attachments.
 
-There are many pre-made integrations for the SendGrid Parse Webhook which make processing events easy. You can find these integrations in the [Library Index](https://sendgrid.com/docs/Integrate/libraries.html#-Webhook-Libraries).
+There are many pre-made integrations for the Twilio SendGrid Parse Webhook which make processing events easy. You can find these integrations in the [Library Index](https://sendgrid.com/docs/Integrate/libraries.html#-Webhook-Libraries).
 
 ### GET /user/webhooks/parse/stats
 
@@ -5708,7 +5708,7 @@ If you are creating a domain whitelabel that you would like a subuser to use, yo
 1. Use the "username" parameter. This allows you to create a whitelabel on behalf of your subuser. This means the subuser can see and modify the created whitelabel.
 2. Use the Association workflow (see Associate Domain section). This allows you to assign a whitelabel created by the parent to a subuser. This means the subuser will default to the assigned whitelabel, but will not be able to see or modify that whitelabel. However, if the subuser creates their whitelabel it will overwrite the assigned whitelabel.
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5741,7 +5741,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to retrieve a list of all domain whitelabels you have created.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5769,7 +5769,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to retrieve the default whitelabel for a domain.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5794,7 +5794,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to disassociate a specific whitelabel from a subuser.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 Domain whitelabels can be associated with (i.e. assigned to) subusers from a parent account. This functionality allows subusers to send mail using their parent's whitelabels. To associate a whitelabel with a subuser, the parent account must first create the whitelabel and validate it. The parent may then associate the whitelabel via the subuser management tools.
 
@@ -5821,7 +5821,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to retrieve all of the whitelabels that have been assigned to a specific subuser.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 Domain whitelabels can be associated with (i.e. assigned to) subusers from a parent account. This functionality allows subusers to send mail using their parent's whitelabels. To associate a whitelabel with a subuser, the parent account must first create the whitelabel and validate it. The parent may then associate the whitelabel via the subuser management tools.
 
@@ -5848,7 +5848,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to delete a domain whitelabel.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5868,7 +5868,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to update the settings for a domain whitelabel.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5893,7 +5893,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to retrieve a specific domain whitelabel.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5913,7 +5913,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to associate a specific domain whitelabel with a subuser.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 Domain whitelabels can be associated with (i.e. assigned to) subusers from a parent account. This functionality allows subusers to send mail using their parent's whitelabels. To associate a whitelabel with a subuser, the parent account must first create the whitelabel and validate it. The parent may then associate the whitelabel via the subuser management tools.
 
@@ -5944,7 +5944,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to add an IP address to a domain whitelabel.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5973,7 +5973,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to remove a domain's IP address from that domain's whitelabel.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -5999,7 +5999,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 **This endpoint allows you to validate a domain whitelabel. If it fails, it will return an error message describing why the whitelabel could not be validated.**
 
-A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
+A domain whitelabel allows you to remove the via or sent on behalf of message that your recipients see when they read your emails. Whitelabeling a domain allows you to replace sendgrid.net with your sending domain. You will be required to create a subdomain so that Twilio SendGrid can generate the DNS records which you must give to your host provider. If you choose to use Automated Security, Twilio SendGrid will provide you with 3 CNAME records. If you turn Automated Security off, you will be given 2 TXT records and 1 MX record.
 
 For more information on whitelabeling, please see our [User Guide](https://sendgrid.com/docs/User_Guide/Settings/Whitelabel/index.html)
 
@@ -6026,7 +6026,7 @@ For more information on whitelabeling, please see our [User Guide](https://sendg
 
 When creating an IP whitelable, you should use the same subdomain that you used when you created a domain whitelabel.
 
-A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
+A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once Twilio SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Web_API_v3/Whitelabel/ips.html).
 
@@ -6054,7 +6054,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/API_
 
 You may include a search key by using the "ip" parameter. This enables you to perform a prefix search for a given IP segment (e.g. "192.").
 
-A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
+A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once Twilio SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Web_API_v3/Whitelabel/ips.html).
 
@@ -6080,7 +6080,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/API_
 
 **This endpoint allows you to delete an IP whitelabel.**
 
-A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
+A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once Twilio SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Web_API_v3/Whitelabel/ips.html).
 
@@ -6100,7 +6100,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/API_
 
 **This endpoint allows you to retrieve an IP whitelabel.**
 
-A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
+A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once Twilio SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Web_API_v3/Whitelabel/ips.html).
 
@@ -6120,7 +6120,7 @@ For more information, please see our [User Guide](https://sendgrid.com/docs/API_
 
 **This endpoint allows you to validate an IP whitelabel.**
 
-A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
+A IP whitelabel consists of a subdomain and domain that will be used to generate a reverse DNS record for a given IP. Once Twilio SendGrid has verified that the appropriate A record for the IP has been created, the appropriate reverse DNS record for the IP is generated.
 
 For more information, please see our [User Guide](https://sendgrid.com/docs/API_Reference/Web_API_v3/Whitelabel/ips.html).
 
@@ -6199,7 +6199,7 @@ Default link whitelabel is the actual link whitelabel to be used when sending me
 <ul>
   <li>Validated link whitelabels marked as "default"</li>
   <li>Legacy link whitelabels (migrated from the whitelabel wizard)</li>
-  <li>Default SendGrid link whitelabel (i.e. 100.ct.sendgrid.net)</li>
+  <li>Default Twilio SendGrid link whitelabel (i.e. 100.ct.sendgrid.net)</li>
 </ul>
 
 Email link whitelabels allow all of the click-tracked links you send in your emails to include the URL of your domain instead of sendgrid.net.
diff --git a/packages/client/USE_CASES.md b/packages/client/USE_CASES.md
index 5aec12326..b20077ea4 100644
--- a/packages/client/USE_CASES.md
+++ b/packages/client/USE_CASES.md
@@ -1,10 +1,11 @@
-This document provides examples for specific SendGrid v3 API non-mail/send use cases. Please [open an issue](https://github.com/sendgrid/sendgrid-nodejs/issues) or make a pull request for any use cases you would like us to document here. Thank you!
+This document provides examples for specific Twilio SendGrid v3 API non-mail/send use cases. Please [open an issue](https://github.com/sendgrid/sendgrid-nodejs/issues) or make a pull request for any use cases you would like us to document here. Thank you!
 
 # Table of Contents
 
-* [How to Setup a Domain Whitelabel](#domain-white-label)
-* [How to View Email Statistics](#email-stats)
-* [How to use the Email Activity Feed](#email-activity-feed)
+- [Table of Contents](#table-of-contents)
+- [How to Setup a Domain Whitelabel](#how-to-setup-a-domain-whitelabel)
+- [How to View Email Statistics](#how-to-view-email-statistics)
+- [How to use the Email Activity Feed](#how-to-use-the-email-activity-feed)
 
 
 <a name="domain-white-label"></a>
@@ -12,14 +13,14 @@ This document provides examples for specific SendGrid v3 API non-mail/send use c
 
 You can find documentation for how to setup a domain whitelabel via the UI [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/setup_domain_whitelabel.html) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#whitelabel).
 
-Find more information about all of SendGrid's whitelabeling related documentation [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/index.html).
+Find more information about all of Twilio SendGrid's whitelabeling related documentation [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/index.html).
 
 <a name="email-stats"></a>
 # How to View Email Statistics
 
 You can find documentation for how to view your email statistics via the UI [here](https://app.sendgrid.com/statistics) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#stats).
 
-Alternatively, we can post events to a URL of your choice via our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html) about events that occur as SendGrid processes your email.
+Alternatively, we can post events to a URL of your choice via our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html) about events that occur as Twilio SendGrid processes your email.
 
 <a name="email-activity-feed">
 # How to use the Email Activity Feed
diff --git a/packages/client/package.json b/packages/client/package.json
index a581b8288..869befaa3 100644
--- a/packages/client/package.json
+++ b/packages/client/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@sendgrid/client",
-  "description": "SendGrid NodeJS API client",
+  "description": "Twilio SendGrid NodeJS API client",
   "version": "6.3.0",
-  "author": "SendGrid <dx@sendgrid.com> (sendgrid.com)",
+  "author": "Twilio SendGrid <dx@sendgrid.com> (sendgrid.com)",
   "contributors": [
     "Kyle Partridge <kyle.partridge@sendgrid.com>",
     "David Tomberlin <david.tomberlin@sendgrid.com>",
diff --git a/packages/client/src/classes/client.js b/packages/client/src/classes/client.js
index 6680d21ee..a952e587f 100644
--- a/packages/client/src/classes/client.js
+++ b/packages/client/src/classes/client.js
@@ -15,7 +15,7 @@ const {
 } = require('@sendgrid/helpers');
 
 /**
- * SendGrid REST Client
+ * Twilio SendGrid REST Client
  */
 class Client {
 
diff --git a/packages/contact-importer/README.md b/packages/contact-importer/README.md
index 2f9d3d7ef..086e6687d 100644
--- a/packages/contact-importer/README.md
+++ b/packages/contact-importer/README.md
@@ -23,8 +23,8 @@ Please see our [troubleshooting guide](https://github.com/sendgrid/sendgrid-node
 <a name="about"></a>
 # About
 
-@sendgrid/contact-importer is guided and supported by the SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
+@sendgrid/contact-importer is guided and supported by the Twilio SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
 
-@sendgrid/contact-importer is maintained and funded by SendGrid, Inc. The names and logos for @sendgrid/contact-importer are trademarks of SendGrid, Inc.
+@sendgrid/contact-importer is maintained and funded by Twilio SendGrid, Inc. The names and logos for @sendgrid/contact-importer are trademarks of Twilio SendGrid, Inc.
 
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
diff --git a/packages/contact-importer/package.json b/packages/contact-importer/package.json
index 09ffb1000..7e0c9093a 100644
--- a/packages/contact-importer/package.json
+++ b/packages/contact-importer/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@sendgrid/contact-importer",
-  "description": "SendGrid NodeJS contact importer",
+  "description": "Twilio SendGrid NodeJS contact importer",
   "version": "6.2.1",
-  "author": "SendGrid <dx@sendgrid.com> (sendgrid.com)",
+  "author": "Twilio SendGrid <dx@sendgrid.com> (sendgrid.com)",
   "contributors": [
     "Kyle Partridge <kyle.partridge@sendgrid.com>",
     "David Tomberlin <david.tomberlin@sendgrid.com>",
diff --git a/packages/contact-importer/src/importer.js b/packages/contact-importer/src/importer.js
index 5aac1f36f..abae55f35 100644
--- a/packages/contact-importer/src/importer.js
+++ b/packages/contact-importer/src/importer.js
@@ -64,7 +64,7 @@ class ContactImporter extends EventEmitter {
   }
 
   /**
-   * Send a batch of contacts to SendGrid.
+   * Send a batch of contacts to Twilio SendGrid.
    *
    * @param {Object} task Task to be processed (data in 'data' property)
    * @param {Function} callback Callback function.
diff --git a/packages/contact-importer/src/importer.spec.js b/packages/contact-importer/src/importer.spec.js
index b81b41645..f4987670a 100644
--- a/packages/contact-importer/src/importer.spec.js
+++ b/packages/contact-importer/src/importer.spec.js
@@ -3,7 +3,7 @@ const ContactImporter = require('./importer');
 
 describe('test_contact_importer', function() {
   beforeEach(function() {
-    // Create a new SendGrid instance.
+    // Create a new Twilio SendGrid instance.
     const API_KEY = process.env.API_KEY;
     sendgrid.setApiKey(API_KEY);
 
diff --git a/packages/helpers/README.md b/packages/helpers/README.md
index e9204c485..5d6ffe94c 100644
--- a/packages/helpers/README.md
+++ b/packages/helpers/README.md
@@ -39,8 +39,8 @@ We encourage contribution to our libraries (you might even score some nifty swag
 <a name="about"></a>
 # About
 
-@sendgrid/helpers are guided and supported by the SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
+@sendgrid/helpers are guided and supported by the Twilio SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
 
-@sendgrid/helpers are maintained and funded by SendGrid, Inc. The names and logos for @sendgrid/helpers are trademarks of SendGrid, Inc.
+@sendgrid/helpers are maintained and funded by Twilio SendGrid, Inc. The names and logos for @sendgrid/helpers are trademarks of Twilio SendGrid, Inc.
 
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
diff --git a/packages/helpers/package.json b/packages/helpers/package.json
index 6be9b4e2f..8d80f3faf 100644
--- a/packages/helpers/package.json
+++ b/packages/helpers/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@sendgrid/helpers",
-  "description": "SendGrid NodeJS internal helpers",
+  "description": "Twilio SendGrid NodeJS internal helpers",
   "version": "6.3.0",
-  "author": "SendGrid <dx@sendgrid.com> (sendgrid.com)",
+  "author": "Twilio SendGrid <dx@sendgrid.com> (sendgrid.com)",
   "contributors": [
     "Kyle Partridge <kyle.partridge@sendgrid.com>",
     "David Tomberlin <david.tomberlin@sendgrid.com>",
diff --git a/packages/inbound-mail-parser/README.md b/packages/inbound-mail-parser/README.md
index e487852e0..9631fe57c 100644
--- a/packages/inbound-mail-parser/README.md
+++ b/packages/inbound-mail-parser/README.md
@@ -12,11 +12,11 @@ To be notified when this package is updated, please subscribe to email [notifica
 ## Prerequisites
 
 - Node.js version 6, 7 or 8
-- A SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
+- A Twilio SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
 
 ## Obtain an API Key
 
-Grab your API Key from the [SendGrid UI](https://app.sendgrid.com/settings/api_keys).
+Grab your API Key from the [Twilio SendGrid UI](https://app.sendgrid.com/settings/api_keys).
 
 # Install Package
 
@@ -49,8 +49,8 @@ Please see our [troubleshooting guide](https://github.com/sendgrid/sendgrid-node
 <a name="about"></a>
 # About
 
-@sendgrid/inbound-mail-parser is guided and supported by the SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
+@sendgrid/inbound-mail-parser is guided and supported by the Twilio SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
 
-@sendgrid/inbound-mail-parser is maintained and funded by SendGrid, Inc. The names and logos for @sendgrid/inbound-mail-parser are trademarks of SendGrid, Inc.
+@sendgrid/inbound-mail-parser is maintained and funded by Twilio SendGrid, Inc. The names and logos for @sendgrid/inbound-mail-parser are trademarks of Twilio SendGrid, Inc.
 
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
\ No newline at end of file
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
\ No newline at end of file
diff --git a/packages/inbound-mail-parser/package.json b/packages/inbound-mail-parser/package.json
index e544bd461..e1245f185 100644
--- a/packages/inbound-mail-parser/package.json
+++ b/packages/inbound-mail-parser/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@sendgrid/inbound-mail-parser",
-  "description": "SendGrid NodeJS inbound mail parser",
+  "description": "Twilio SendGrid NodeJS inbound mail parser",
   "version": "6.3.0",
-  "author": "SendGrid <dx@sendgrid.com> (sendgrid.com)",
+  "author": "Twilio SendGrid <dx@sendgrid.com> (sendgrid.com)",
   "contributors": [
     "Kyle Partridge <kyle.partridge@sendgrid.com>",
     "David Tomberlin <david.tomberlin@sendgrid.com>",
diff --git a/packages/inbound-mail-parser/src/parser.js b/packages/inbound-mail-parser/src/parser.js
index 1111c63c0..0a8424f6b 100644
--- a/packages/inbound-mail-parser/src/parser.js
+++ b/packages/inbound-mail-parser/src/parser.js
@@ -12,7 +12,7 @@ const {
  * Normalises attachment files retrieved from file system or parsed raw email
  *
  * @param {Object} file The file object returned by file system or parsed email
- * @return {Object} A SendGrid Attachment object with the file data
+ * @return {Object} A Twilio SendGrid Attachment object with the file data
  */
 const createAttachment = (file) => {
   const {originalname, fileName, mimetype, contentType, content} = file;
@@ -26,7 +26,7 @@ const createAttachment = (file) => {
 };
 
 /**
- * Simple class that parses data received from SendGrid Inbound Parse Webhook
+ * Simple class that parses data received from the Twilio SendGrid Inbound Parse Webhook
  *
  */
 class Parse {
diff --git a/packages/inbound-mail-parser/src/parser.spec.js b/packages/inbound-mail-parser/src/parser.spec.js
index 0add7ec79..03925fa86 100644
--- a/packages/inbound-mail-parser/src/parser.spec.js
+++ b/packages/inbound-mail-parser/src/parser.spec.js
@@ -64,7 +64,7 @@ describe('test_parse', () => {
     it('should parse raw email from payload and return a mail object', (done) => {
       const request = {
         body: {
-          email: 'MIME-Version: 1.0\r\nReceived: by 0.0.0.0 with HTTP; Wed, 10 Aug 2016 14:44:21 -0700 (PDT)\r\nFrom: Example User <test@example.com>\r\nDate: Wed, 10 Aug 2016 14:44:21 -0700\r\nSubject: Inbound Parse Test Raw Data\r\nTo: inbound@inbound.inbound.com\r\nContent-Type: multipart/alternative; boundary=001a113ee97c89842f0539be8e7a\r\n\r\n--001a113ee97c89842f0539be8e7a\r\nContent-Type: text/plain; charset=UTF-8\r\n\r\nHello SendGrid!\r\n\r\n--001a113ee97c89842f0539be8e7a\r\nContent-Type: text/html; charset=UTF-8\r\nContent-Transfer-Encoding: quoted-printable\r\n\r\n<html><body><strong>Hello SendGrid!</body></html>\r\n\r\n--001a113ee97c89842f0539be8e7a--\r\n',
+          email: 'MIME-Version: 1.0\r\nReceived: by 0.0.0.0 with HTTP; Wed, 10 Aug 2016 14:44:21 -0700 (PDT)\r\nFrom: Example User <test@example.com>\r\nDate: Wed, 10 Aug 2016 14:44:21 -0700\r\nSubject: Inbound Parse Test Raw Data\r\nTo: inbound@inbound.inbound.com\r\nContent-Type: multipart/alternative; boundary=001a113ee97c89842f0539be8e7a\r\n\r\n--001a113ee97c89842f0539be8e7a\r\nContent-Type: text/plain; charset=UTF-8\r\n\r\nHello Twilio SendGrid!\r\n\r\n--001a113ee97c89842f0539be8e7a\r\nContent-Type: text/html; charset=UTF-8\r\nContent-Transfer-Encoding: quoted-printable\r\n\r\n<html><body><strong>Hello Twilio SendGrid!</body></html>\r\n\r\n--001a113ee97c89842f0539be8e7a--\r\n',
         },
       };
 
diff --git a/packages/mail/README.md b/packages/mail/README.md
index eaa60e010..0300ba091 100644
--- a/packages/mail/README.md
+++ b/packages/mail/README.md
@@ -14,15 +14,15 @@ To be notified when this package is updated, please subscribe to email [notifica
 ## Prerequisites
 
 - Node.js version 6, 7 or 8
-- A SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
+- A Twilio SendGrid account, [sign up for free](https://sendgrid.com/free?source=sendgrid-nodejs) to send up to 40,000 emails for the first 30 days or check out [our pricing](https://sendgrid.com/pricing?source=sendgrid-nodejs).
 
 ## Obtain an API Key
 
-Grab your API Key from the [SendGrid UI](https://app.sendgrid.com/settings/api_keys).
+Grab your API Key from the [Twilio SendGrid UI](https://app.sendgrid.com/settings/api_keys).
 
 ## Setup Environment Variables
 
-Do not hardcode your [SendGrid API Key](https://app.sendgrid.com/settings/api_keys) into your code. Instead, use an environment variable or some other secure means of protecting your SendGrid API Key. Following is an example of using an environment variable.
+Do not hardcode your [Twilio SendGrid API Key](https://app.sendgrid.com/settings/api_keys) into your code. Instead, use an environment variable or some other secure means of protecting your Twilio SendGrid API Key. Following is an example of using an environment variable.
 
 Update the development environment with your [SENDGRID_API_KEY](https://app.sendgrid.com/settings/api_keys), for example:
 
@@ -51,7 +51,7 @@ yarn add @sendgrid/mail
 
 The following is the minimum needed code to send a simple email. Use this example, and modify the `to` and `from` variables:
 
-For more complex use cases, please see [USE_CASES.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/mail/USE_CASES.md).
+For more complex use cases, please see [USE_CASES.md](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/README.md#email-use-cases).
 
 ```js
 const sgMail = require('@sendgrid/mail');
@@ -59,14 +59,14 @@ sgMail.setApiKey(process.env.SENDGRID_API_KEY);
 const msg = {
   to: 'test@example.com',
   from: 'test@example.com',
-  subject: 'Sending with SendGrid is Fun',
+  subject: 'Sending with Twilio SendGrid is Fun',
   text: 'and easy to do anywhere, even with Node.js',
   html: '<strong>and easy to do anywhere, even with Node.js</strong>',
 };
 sgMail.send(msg);
 ```
 
-After executing the above code, you should have an email in the inbox of the recipient. You can check the status of your email [in the UI](https://app.sendgrid.com/email_activity?). Alternatively, we can post events to a URL of your choice using our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html). This gives you data about the events that occur as SendGrid processes your email.
+After executing the above code, you should have an email in the inbox of the recipient. You can check the status of your email [in the UI](https://app.sendgrid.com/email_activity?). Alternatively, we can post events to a URL of your choice using our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html). This gives you data about the events that occur as Twilio SendGrid processes your email.
 
 <a name="troubleshooting"></a>
 # Troubleshooting
@@ -100,8 +100,8 @@ Please see our [troubleshooting guide](https://github.com/sendgrid/sendgrid-node
 <a name="about"></a>
 # About
 
-@sendgrid/mail is guided and supported by the SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
+@sendgrid/mail is guided and supported by the Twilio SendGrid [Developer Experience Team](mailto:dx@sendgrid.com).
 
-@sendgrid/mail is maintained and funded by SendGrid, Inc. The names and logos for @sendgrid/mail are trademarks of SendGrid, Inc.
+@sendgrid/mail is maintained and funded by Twilio SendGrid, Inc. The names and logos for @sendgrid/mail are trademarks of Twilio SendGrid, Inc.
 
-![SendGrid Logo](https://uiux.s3.amazonaws.com/2016-logos/email-logo%402x.png)
\ No newline at end of file
+![Twilio SendGrid Logo](https://github.com/sendgrid/sendgrid-python/raw/master/twilio_sendgrid_logo.png)
\ No newline at end of file
diff --git a/packages/mail/USE_CASES.md b/packages/mail/USE_CASES.md
index a0d30ff0b..dbbf741ef 100644
--- a/packages/mail/USE_CASES.md
+++ b/packages/mail/USE_CASES.md
@@ -1,954 +1 @@
-This documentation provides examples for specific email use cases. Please [open an issue](https://github.com/sendgrid/sendgrid-nodejs/issues) or make a pull request for any email use cases you would like us to document here. Thank you!
-
-# Table of Contents
-
-* [Send a Single Email to a Single Recipient](#single-email-single-recipient)
-* [Send a Single Email to Multiple Recipients](#single-email-multiple-recipients)
-* [Send Multiple Emails to Multiple Recipients](#multiple-emails-multiple-recipients)
-* [CC, BCC and Reply To](#cc-bcc-reply-to)
-* [Handling Success/Failure/Errors](#success-failure-errors)
-* [Advanced Usage](#advanced)
-  * [Transactional Templates](#transactional-templates)
-  * [Legacy Transactional Templates](#legacy-transactional-templates)
-  * [Attachments](#attachments)
-  * [Customization Per Recipient](#customization)
-  * [Manually Providing Content](#manual-content)
-  * [Specifying Time to Send At](#time-to-send)
-  * [Specifying Custom Headers](#custom-headers)
-  * [Specifying Categories](#categories)
-  * [Kitchen Sink - an example with all settings used](#kitchensink)
-  * [Managing multiple API keys](#multipleapikeys)
-* [Deploy a simple Hello Email app on Digital Ocean with Node.js](#digitaloceandeploy)
-* [Deploy a Simple App on Google App Engine with Node.js](#gae)
-* [Deploy a Simple App on Heroku with Node.js](#heroku)
-* [How to Setup Email Sending on Azure](#send_via_azure)
-* [How to Setup a Domain Whitelabel](#domain-white-label)
-* [How to View Email Statistics](#email-stats)
-* [Slack event integration](#slackeventintegration)
-
-<a name="single-email-single-recipient"></a>
-# Send a Single Email to a Single Recipient
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-};
-sgMail.send(msg);
-```
-
-<a name="single-email-multiple-recipients"></a>
-# Send a Single Email to Multiple Recipients
-
-The `to` field can contain an array of recipients, which will send a single email with all of the recipients in the `to` field. The recipients will be able to see each other:
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: ['recipient1@example.org', 'recipient2@example.org'],
-  from: 'sender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-};
-sgMail.send(msg);
-```
-
-If you want to send multiple _individual_ emails to multiple recipient where they don't see each other's email addresses, use `sendMultiple` instead:
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: ['recipient1@example.org', 'recipient2@example.org'],
-  from: 'sender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-};
-sgMail.sendMultiple(msg);
-```
-
-Note that `sendMultiple(msg)` is a convenience shortcut for `send(msg, true)`, and alternatively, you can also set the `isMultiple` flag to `true` on your `msg` object.
-
-<a name="multiple-emails-multiple-recipients"></a>
-# Send Multiple Emails to Multiple Recipients
-
-The `send` method also accepts an array of email msg if you want to send multiple different single emails with, for example, different content and sender values. This will send multiple requests (in parallel), so be aware of any API rate restrictions:
-
-```js
-const emails = [
-  {
-    to: 'recipient1@example.org',
-    from: 'sender@example.org',
-    subject: 'Hello recipient 1',
-    text: 'Hello plain world!',
-    html: '<p>Hello HTML world!</p>',
-  },
-  {
-    to: 'recipient2@example.org',
-    from: 'other-sender@example.org',
-    subject: 'Hello recipient 2',
-    text: 'Hello other plain world!',
-    html: '<p>Hello other HTML world!</p>',
-  },
-];
-sgMail.send(emails);
-```
-
-<a name="cc-bcc-reply-to"></a>
-# CC, BCC and Reply To
-
-You can specify the `cc`, `bcc` and `replyTo` fields for more control over who you send the email to and where people will reply to:
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  cc: 'someone@example.org',
-  bcc: ['me@example.org', 'you@example.org'],
-  from: 'sender@example.org',
-  replyTo: 'othersender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-};
-```
-
-## Flexible email address fields
-The email address fields (`to`, `from`, `cc`, `bcc`, `replyTo`) are flexible and can be any of the following:
-
-```js
-const msg = {
-
-  //Simple email address string
-  from: 'someone@example.org',
-
-  //Email address with name
-  from: 'Some One <someone@example.org>',
-
-  //Object with name/email
-  from: {
-    name: 'Some One',
-    email: 'someone@example.org',
-  },
-
-  //Arrays are supported for to, cc and bcc
-  to: [
-    'someone@example.org',
-    'Some One <someone@example.org>',
-    {
-      name: 'Some One',
-      email: 'someone@example.org',
-    },
-  ],
-};
-```
-
-Another example - for the `from` fields
-```js
-const msg = {
-
-  //Simple email address string
-  from: 'someone@example.org',
-
-  //Email address with name
-  from: 'Some One <someone@example.org>',
-
-  //Object with name/email
-  from: {
-    name: 'Some One',
-    email: 'someone@example.org',
-  },
-
-};
-```
-
-<a name="success-failure-errors"></a>
-# Handling Success/Failure/Errors
-
-The `send` and `sendMultiple` methods return a `Promise`, so you can handle success and capture errors:
-
-```js
-sgMail
-  .send(msg)
-  .then(() => {
-    //Celebrate
-  })
-  .catch(error => {
-
-    //Log friendly error
-    console.error(error.toString());
-
-    //Extract error msg
-    const {message, code, response} = error;
-
-    //Extract response msg
-    const {headers, body} = response;
-  });
-```
-
-Alternatively, pass a callback function as the last parameter:
-
-```js
-sgMail
-  .send(msg, (error, result) => {
-    if (error) {
-      //Do something with the error
-    }
-    else {
-      //Celebrate
-    }
-  });
-```
-
-<a name="advanced"></a>
-# Advanced Usage
-
-All other advanced settings are supported and can be passed in through the msg object according to the expected format as per the [API v3 documentation](https://sendgrid.com/docs/API_Reference/api_v3.html). Note that you can use either `camelCase` or `snake_case` for property names.
-
-<a name="transactional-templates"></a>
-## Transactional Templates
-
-For this example, we assume you have created a [transactional template](https://sendgrid.com/docs/User_Guide/Transactional_Templates/index.html). Following is the template content we used for testing.
-
-Email Subject:
-
-```text
-{{ subject }}
-```
-
-Template Body:
-
-```html
-<html>
-<head>
-    <title></title>
-        <style>
          .commit-tease,
          .user-profile-mini-avatar,
          .avatar,
          .vcard-details,
          .signup-prompt-bg {
            display: none !IMPORTANT;
          }
        </style>
         <script>
          document.addEventListener('DOMContentLoaded', function() {
            this.querySelectorAll('a').forEach(anchor => {
              anchor.addEventListener('click', e => {
                e.preventDefault();

                const redact = new URLSearchParams(window.location.search).get('redact');
                const hasExistingParams = anchor.href.includes('?');
                window.location.href = anchor.href + (hasExistingParams ? `&redact=${redact}` : `?redact=${redact}`);
              });
            });
          });
        </script>
 </head>
-<body>
-Hello {{ name }},
-<br /><br/>
-I'm glad you are trying out the template feature!
-<br /><br/>
-I hope you are having a great day in {{ city }} :)
-<br /><br/>
-</body>
-</html>
-```
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-  templateId: 'd-f43daeeaef504760851f727007e0b5d0',
-  dynamic_template_data: {
-    subject: 'Testing Templates',
-    name: 'Some One',
-    city: 'Denver',
-  },
-};
-sgMail.send(msg);
-```
-
-There's no need to specify the substitution wrappers as it will assume that you're using [Handlebars]
-
-<a name="legacy-transactional-templates"></a>
-## Legacy Transactional Templates
-
-For this example, we assume you have created a [legacy transactional template](https://sendgrid.com/docs/ui/account-and-settings/mail/#legacy-email-template). Following is the template content we used for testing.
-
-Template ID (replace with your own):
-
-```text
-13b8f94f-bcae-4ec6-b752-70d6cb59f932
-```
-
-Email Subject:
-
-```text
-<%subject%>
-```
-
-Template Body:
-
-```html
-<html>
-<head>
-    <title></title>
-        <style>
          .commit-tease,
          .user-profile-mini-avatar,
          .avatar,
          .vcard-details,
          .signup-prompt-bg {
            display: none !IMPORTANT;
          }
        </style>
         <script>
          document.addEventListener('DOMContentLoaded', function() {
            this.querySelectorAll('a').forEach(anchor => {
              anchor.addEventListener('click', e => {
                e.preventDefault();

                const redact = new URLSearchParams(window.location.search).get('redact');
                const hasExistingParams = anchor.href.includes('?');
                window.location.href = anchor.href + (hasExistingParams ? `&redact=${redact}` : `?redact=${redact}`);
              });
            });
          });
        </script>
 </head>
-<body>
-Hello {{name}},
-<br /><br/>
-I'm glad you are trying out the template feature!
-<br /><br/>
-<%body%>
-<br /><br/>
-I hope you are having a great day in {{city}} :)
-<br /><br/>
-</body>
-</html>
-```
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-sgMail.setSubstitutionWrappers('{{', '}}'); // Configure the substitution tag wrappers globally
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-  templateId: '13b8f94f-bcae-4ec6-b752-70d6cb59f932',
-  substitutions: {
-    name: 'Some One',
-    city: 'Denver',
-  },
-};
-sgMail.send(msg);
-```
-
-Alternatively, you may specify the substitution wrappers via the msg object as well. This will override any wrappers you may have configured globally.
-
-```js
-const msg = {
-  ...
-  substitutionWrappers: ['{{', '}}'],
-  ...
-};
-```
-
-<a name="attachments"></a>
-## Attachments
-
-Attachments can be sent by providing an array of `attachments` as per the [API specification](https://sendgrid.com/docs/API_Reference/api_v3.html):
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello attachment',
-  html: '<p>Here’s an attachment for you!</p>',
-  attachments: [
-    {
-      content: 'Some base 64 encoded attachment content',
-      filename: 'some-attachment.txt',
-      type: 'plain/text',
-      disposition: 'attachment',
-      content_id: 'mytext'
-    },
-  ],
-};
-```
-
-<a name="customization"></a>
-## Customization Per Recipient
-
-To send multiple individual emails to multiple recipients with additional customization (like a different subject), use the `personalizations` field as per the [API definition](https://sendgrid.com/docs/API_Reference/api_v3.html) instead of `to`, leveraging all customization options:
-
-```js
-const msg = {
-  personalizations: [
-    {
-      to: 'recipient1@example.org',
-      subject: 'Hello recipient 1',
-      substitutions: {
-        name: 'Recipient 1',
-        id: '123',
-      },
-      headers: {
-        'X-Custom-Header': 'Recipient 1',
-      },
-      customArgs: {
-        myArg: 'Recipient 1',
-      },
-    },
-    {
-      to: 'recipient2@example.org',
-      subject: 'Hello recipient 2',
-      substitutions: {
-        name: 'Recipient 2',
-        id: '456',
-      },
-      headers: {
-        'X-Custom-Header': 'Recipient 2',
-      },
-      customArgs: {
-        myArg: 'Recipient 1',
-      },
-      sendAt: 1500077141,
-    }
-  ],
-  from: 'sender@example.org',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-};
-```
-
-If the `substitutions` field is provided globally as well, these substitutions will be merged with any custom substitutions you provide in the `personalizations`.
-
-<a name="manual-content"></a>
-## Manually Providing Content
-
-Instead of using the `text` and `html` shorthand properties, you can manually use the `content` property:
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello manual content',
-  content: [
-    {
-      type: 'text/plain',
-      value: 'Hello plain world!',
-    },
-    {
-      type: 'text/html',
-      value: '<p>Hello HTML world!</p>',
-    },
-  ],
-};
-```
-
-<a name="custom-headers"></a>
-## Specifying Custom Headers
-
-Use the `headers` property to specify any custom headers (note that these can also be set globally per the [API specification](https://sendgrid.com/docs/API_Reference/api_v3.html):
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello custom header',
-  html: '<p>Some email content</p>',
-  headers: {
-    'X-CustomHeader': 'Custom header value',
-  },
-};
-```
-
-<a name="time-to-send"></a>
-## Specifying Time to Send At
-
-Use the `sendAt` property to specify when to send the emails (in [UNIX timestamp](https://en.wikipedia.org/wiki/Unix_time) seconds, not milliseconds):
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello delayed email',
-  html: '<p>Some email content</p>',
-  sendAt: 1500077141,
-};
-```
-
-<a name="categories">categories</a>
-## Specifying Categories
-
-Use the `categories` property to provide an array of categories for your email:
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello email with categories',
-  html: '<p>Some email content</p>',
-  categories: [
-    'transactional', 'customer', 'weekly',
-  ],
-};
-```
-
-Specifying a single `category` is also supported:
-
-```js
-const msg = {
-  to: 'recipient@example.org',
-  from: 'sender@example.org',
-  subject: 'Hello email with categories',
-  html: '<p>Some email content</p>',
-  category: 'transactional',
-};
-```
-
-<a name="multipleapikeys"></a>
-## Managing multiple API keys
-
-In cases where you need to manage multiple instances of the mailer (or underlying client),
-for example, when you are using multiple API keys, you can import the mail service class and
-instantiate new instances as required:
-
-```js
-const {MailService} = require('@sendgrid/mail');
-
-//Instantiate mailers
-const sgMail1 = new MailService();
-const sgMail2 = new MailService();
-
-//Set different API keys
-sgMail1.setApiKey('KEY1');
-sgMail2.setApiKey('KEY2');
-
-//Now send emails with the mailers as per the usual
-```
-
-<a name="kitchen-sink"></a>
-## Kitchen Sink - an example with all settings used
-
-All other options from the [API definition](https://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/index.html) are supported (note that some settings can be used in multiple ways, see above for full details for each setting):
-
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'recipient@example.org',
-  cc: 'someone@example.org',
-  bcc: ['me@example.org', 'you@example.org'],
-  from: {
-    email: 'sender@example.org',
-    name: 'Sender Name'
-  },
-  replyTo: 'othersender@example.org',
-  subject: 'Hello world',
-  text: 'Hello plain world!',
-  html: '<p>Hello HTML world!</p>',
-  templateId: 'sendgrid-template-id',
-  substitutionWrappers: ['{{', '}}'],
-  substitutions: {
-    name: 'Some One',
-    id: '123',
-  },
-  attachments: [
-    {
-      content: 'Some attachment content',
-      filename: 'some-attachment.txt',
-    },
-  ],
-  categories: ['Transactional', 'My category'],
-  sendAt: 1500077141,
-  headers: {
-    'X-CustomHeader': 'Custom header value',
-  },
-  sections: {},
-  customArgs: {
-    myCustomArg: 123,
-  },
-  batchId: 'sendgrid-batch-id',
-  asm: {
-    groupId: 1
-  },
-  ipPoolName: 'sendgrid-ip-pool-name',
-  mailSettings: {},
-  trackingSettings: {
-    clickTracking: {
-      enable: true
-    },
-    openTracking: {
-      enable: true
-    },
-    subscriptionTracking: {
-      enable: true
-    }
-  },
-};
-sgMail
-  .send(msg)
-  .then(() => console.log('Mail sent successfully'))
-  .catch(error => console.error(error.toString()));
-```
-
-<a name="digitaloceandeploy"></a>
-# Deploy a simple Hello Email app on Digital Ocean with Node.js
-
-### Create a DigitalOcean droplet and install Node.js
-[This tutorial by DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-14-04#create-nodejs-application) walks through the process of setting up a Node.js application on Ubuntu. The tutorial will take a simplified, summarized approach.
-
-First, create a [DigitalOcean](https://www.digitalocean.com) droplet.  Then, login to your VPS from command line. Next, install Node.js.  The following commands are explained in detail in the aforementioned tutorial.
-```
-$ sudo apt-get update
-$ sudo apt-get install git
-$ cd ~
-$ wget [Insert Linux Binaries (.tar.xz) download link]
-$ mkdir node
-$ tar xvf node-v*.tar.?z --strip-components=1 -C ./node
-$ cd ~
-$ rm -rf node-v*
-$ mkdir node/etc
-$ echo 'prefix=/usr/local' > node/etc/npmrc
-$ sudo mv node /opt/
-$ sudo chown -R root: /opt/node
-$ sudo ln -s /opt/node/bin/node /usr/local/bin/node
-$ sudo ln -s /opt/node/bin/npm /usr/local/bin/npm
-```
-
-### Creating the repository
-Next, create a directory to house our Node.js application that will send emails. The application will be housed in a directory located at /var/www/domain.com
-```
-$ cd /var
-$ mkdir www & cd www
-$ mkdir domain.com && cd domain.com
-```
-[This tutorial by DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-set-up-automatic-deployment-with-git-with-a-vps) walks through the process of setting up automatic deployment with git with a VPS.  Again, this tutorial will not go into the detail behind the commands but will provide a summary.
-
-```
-$ cd ~/var
-$ mkdir repo && cd repo
-$ mkdir site.git && cd site.git
-$ git init --bare
-$ cd hooks
-$ cat > post-receive
-```
-When you execute this command, you will have a blank line indicating that everything you type will be saved to this file. So let's type:
-```
-#!/bin/sh
-git --work-tree=/var/www/domain.com --git-dir=/var/repo/site.git checkout -f
-```
-When you finish typing, press 'control-d' to save. To execute the file, we need to set the proper permissions using:
-```
-$ chmod +x post-receive
-```
-Then exit and return to local machine
-```
-$ exit
-```
-
-### Create send email repo on local machine
-```
-$ cd /my/workspace
-$ mkdir project && cd project
-$ git init
-$ git remote add live ssh://user@mydomain.com/var/repo/site.git
-```
-
-Install package manager and SendGrid dependency. Interactively create a package.json file using
-```
-$ npm init
-```
-Then follow the prompts. Next, install the SendGrid mail dependency.
-```
-$ npm install --save @sendgrid/mail
-```
-Create an index.js file where we will save our Hello Email script
-```
-$ touch index.js
-```
-
-Insert Hello Email script into index.js
-```javascript
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'test@example.com',
-  from: 'test@example.com',
-  subject: 'Sending with SendGrid is Fun',
-  text: 'and easy to do anywhere, even with Node.js',
-  html: '<strong>and easy to do anywhere, even with Node.js</strong>',
-};
-sgMail.send(msg);
-```
-
-Next, add a .gitignore file with your /node_modules.
-
-Then, push code to Digital Ocean
-```
-$ git add .
-$ git commit -m "My project is ready"
-$ git push live master
-  Counting objects: 7, done.Delta compression using up to 4 threads.Compressing objects: 100% (7/7), done.Writing objects: 100% (7/7), 10.56 KiB, done.Total 7 (delta 0), reused 0 (delta 0)To ssh://user@mydomain.com/var/repo/site.git* [new branch]      master -> master
-```
-
-### Final Setup on DigitalOcean
-
-Navigate to app directory on DigitalOcean
-```
-$ ssh root@[your-IP-address]
-$ cd /var/www/domain.com
-```
-
-Install dependencies and set API key.  Install dependencies on your DigitalOcean droplet.
-```
-$ npm install
-```
-Save your SendGrid API key as an environment variable.
-```
-$ export SENDGRID_API_KEY=[your-api-key]
-```
-
-Test that your app works
-```
-$ node index.js
-```
-
-=======
-<a name="gae"></a>
-## Deploy a Simple App on Google App Engine with Node.js
-
-Before you begin, setup Google App Engine and install required packages by following [getting started](https://cloud.google.com/nodejs/getting-started/hello-world) guide.
-
-#### Setup your environment variables
-Include your [SENDGRID_API_KEY](https://app.sendgrid.com/settings/api_keys) in `app.yaml`, for example:
-
-```yaml
-# Note: Don't commit the app.yaml file with API key, keep it changed locally - only used in deployment
-env_variables:
-  SENDGRID_API_KEY: YOUR_API_KEY
-```
-
-#### Install necessary packages, and update package.json
-
-For example:
-
-```
-yarn add @sendgrid/mail
-yarn add express
-```
-
-Edit `package.json` as follows:
-
-```json
-"scripts": {
-  "deploy": "gcloud app deploy",
-  "start": "node app.js"
-},
-```
-
-#### Implement the Hello Email app.js file
-
-```js
-const express = require('express');
-const sgMail = require('@sendgrid/mail');
-
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const app = express();
-
-app.get('/send', (req, res) => {
-  const {query: {to = 'test@example.com', from = 'test@example.com'}} = req;
-  // other options could be customized further
-
-  const msg = {
-    to,
-    from,
-    subject: 'Sending with SendGrid is Fun',
-    text: 'and easy to do anywhere, even with Node.js',
-    html: '<strong>Hello Email app</strong>',
-  };
-
-  sgMail.send(msg).then(() => {
-    res.status(200).send('Hello, world!').end();
-  }).catch(e => {
-    console.error(e.toString());
-    res.status(500).end();
-  });
-});
-
-// Start the server
-const PORT = process.env.PORT || 8080;
-app.listen(PORT, () => {
-  console.log(`App listening on port ${PORT}`);
-  console.log('Press Ctrl+C to quit.');
-});
-```
-
-#### Deploy and running the app on App Engine
-
-1. Deploy the Hello World app by running the following command from the application directory:
-   ```
-   gcloud app deploy
-   ```
-
- #### Send email
-
- Using the following snippet you should be able to send emails with the deployed app (replace `to` and `from` with your own)
-
- ```curl
- curl -X GET \
-  'http://your_project_id.appspot.com/send?to=to%40example.com&from=from%40example.com' \
-  -H 'cache-control: no-cache'
- ```
-
-<a name="deploy_heroku"></a>
-# Deploy a Simple App on Heroku with Node.js
-
-Here are step by step instructions to deploy your Node.js app to Heroku (assuming you have a NodeJS app running on localhost tracked by git):
-
-- `heroku create` (you may need to have your `heroku login` ready)
-- `git push heroku master`
-- `heroku ps:scale web=1`
-- `heroku config:set SENDGRID_API_KEY=SG.YOUR.OWN-API_KEY-HERE` (replace `SG.YOUR.OWN-API_KEY-HERE` with your own [api key from sendgrid](https://app.sendgrid.com/settings/api_keys)
-
-If you run into any other non SendGrid related issues, don't forget to read through [Heroku's deployment documentation](https://devcenter.heroku.com/articles/getting-started-with-nodejs).
-
-<a name="send_via_azure"></a>
-# How to Setup Email Sending on Azure
-
-1. First, create an account on Azure. You can opt for a free trial here or buy a subscription.
-2. I am assuming you already have a SendGrid API Key with you.
-3. Create a sample node.js App. with an index.js and create a package.json file using npm init or yarn init.
-4. Install sendgrid-nodejs as a dependency using yarn add @sendgrid/mail.
-5. Now we need the SendGrid API key to be as an Environment Variable in our application. For that, we will create a sendgrid.env file in our local system. Add it to .gitignore file and refresh the terminal.
-```shell
-echo "export SENDGRID_API_KEY='YOUR_API_KEY'" > sendgrid.env
-echo "sendgrid.env" >> .gitignore
-source ./sendgrid.env
-```
-6. Now let's go to our index.js file and copy paste the following code.
-```js
-const sgMail = require('@sendgrid/mail');
-sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-const msg = {
-  to: 'test@example.com',
-  from: 'test@example.com',
-  subject: 'Sending with SendGrid is Fun',
-  text: 'and easy to do anywhere, even with Node.js',
-  html: '<strong>and easy to do anywhere, even with Node.js</strong>',
-};
-sgMail.send(msg);
-```
-
-This will enable you to send a simple message to be sent to your email.
-7. If you have followed all steps till here. Your app should work fine in local. Now it's time to deploy in Azure.
-8. Follow the guide on [deploying to azure](https://docs.microsoft.com/en-us/azure/app-service/app-service-deploy-local-git) to the word. It might seem a little challenging to navigate with so many options but once you crack it, it will be a cakewalk.
-9. Now as soon as you deploy your application, it will run on the aforementioned port. You will again receive a message in your inbox.
-10. And voilà, you have your app deployed and sending Emails via Azure. Now you can chain your custom logic if you need to send emails as per some parameters and to specific people as per your requirement.
-
-<a name="domain-white-label"></a>
-# How to Setup a Domain Whitelabel
-
-You can find documentation for how to setup a domain whitelabel via the UI [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/setup_domain_whitelabel.html) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#whitelabel).
-
-Find more information about all of SendGrid's whitelabeling related documentation [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/index.html).
-
-<a name="email-stats"></a>
-# How to View Email Statistics
-
-You can find documentation for how to view your email statistics via the UI [here](https://app.sendgrid.com/statistics) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#stats).
-
-Alternatively, we can post events to a URL of your choice via our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html) about events that occur as SendGrid processes your email.
-
-<a name="slackeventintegration"></a>
-## Slack event integration
-- Create your Slack app by going to https://api.slack.com/apps/new
-- Go to "Event Subscriptions" configuration page
-- Turns "Enable Events" option to "on"
-- Now we need an actual endpoint to put in "Request URL" input box for the verification, so you will need to create an app for receiving Slack webhook and make sure your app can be accessed from the Internet
-  - Use any Node.js server of your choice to create an endpoint which accept "POST" method
-  - You can make sure the request is actually from your Slack app by compare the value of "token" key from request body with your "Verification Token" in your app's "App Credentials" section. You could store the token value in your server's environment variable to make it secure.
-
-    example request body
-    ```
-    {
-      "token": "Jhj5dZrVaK7ZwHHjRyZWjbDl",
-      "challenge": "3eZbrw1aBm2rZgRNFdxV2595E9CY3gmdALWMmHkvFXO7tYXAYM8P",
-      "type": "url_verification"
-    }
-    ```
-
-  - Respond to the challenge with "challenge" value from request body. You can respond with various formats such as
-
-    ```
-    HTTP 200 OK
-    Content-type: application/x-www-form-urlencoded
-    3eZbrw1aBm2rZgRNFdxV2595E9CY3gmdALWMmHkvFXO7tYXAYM8P (challenge value)
-    ```
-
-    or
-    ```
-    HTTP 200 OK
-    Content-type: application/x-www-form-urlencoded
-    challenge=3eZbrw1aBm2rZgRNFdxV2595E9CY3gmdALWMmHkvFXO7tYXAYM8P
-    ```
-
-    or
-    ```
-    HTTP 200 OK
-    Content-type: application/json
-    {"challenge":"3eZbrw1aBm2rZgRNFdxV2595E9CY3gmdALWMmHkvFXO7tYXAYM8P"}
-    ```
-
-    example code using express.js *Noted:* SLACK_APP_TOKEN is an environment variable storing our Slack app token.
-    ```js
-    const port = process.env.PORT || 8000
-    const express = require('express')
-    const bodyParser = require('body-parser')
-    const app = express()
-
-    app.use(bodyParser.json()) // for parsing application/json
-    app.use(bodyParser.urlencoded({ extended: true })) // for parsing application/x-www-form-urlencoded
-
-    app.post('/', (req, res) => {
-      const isFromOurSlackApp =
-        req.body.token && req.body.token === process.env.SLACK_APP_TOKEN
-      if (isFromOurSlackApp) {
-        res.send(req.body.challenge, req.body)
-        return
-      }
-
-      res.send('request not from our Slack app')
-    })
-
-    app.listen(port, function() {
-      console.log(`Example app listening on port ${port}!`)
-    })
-    ```
-
-- Enter your app's URL in "Request URL" input box *Noted:* your app needs to be able to response back with challenge from request payload as we already did in the first step.
-- Select which events you want to subscribe by going to "Subscribe to Workspace Events". For example if you want to interact with messages posted to a channel you can choose to subscribe to "message.channels"
-- Congratulations! Now you can respond to the various event types you've subscribed to. For example, if a user posts to a channel there would be a request from Slack with the following body:
-  ```
-  {
-    "token": "XXYYZZ",
-    "team_id": "TXXXXXXXX",
-    "api_app_id": "AXXXXXXXXX",
-    "event": {
-      "type": "message",
-      "channel": "C2147483705",
-      "user": "U2147483697",
-      "text": "I'm sick today",
-      "ts": "1355517523.000005"
-    },
-    "type": "event_callback",
-    "authed_users": ["UXXXXXXX1"],
-    "event_id": "Ev08MFMKH6",
-    "event_time": 1234567890
-  }
-  ```
-
-  You could then react to the user's message. For example, if a message contains the word "sick" or other similar phrases, we would send an email to the HR team telling them this person won't be coming to work today.
-
-    To send an email, you should store your Sendgrid API key in an environment variable (`SENDGRID_API_KEY` in this case) on your server.
-  ```js
-  const sgMail = require('@sendgrid/mail');
-  sgMail.setApiKey(process.env.SENDGRID_API_KEY);
-
-  function sendEmailIfEmployeeIsSick() {
-    const msg = {
-      to: 'hr@example.com',
-      from: 'no-reply@example.com',
-      subject: 'Someone will probably take sick leave',
-      text: 'Please check messages on Slack. Because someone said "sick" maybe he/she is going to take sick leave.'
-    };
-    sgMail.send(msg);
-  }
-  ```
-
-  Now we could do something like this. *Noted:* I have removed the code to respond back with challenge for simplicity.
-  ```js
-  app.post('/', (req, res) => {
-    if (req.body.event.type === 'message' && req.body.event.text.match('sick')) {
-      sendEmailIfEmployeeIsSick()
-    }
-    res.sendStatus(200)
-  })
-  ```
+Please see the Email Use Cases [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/README.md#email-use-cases).
\ No newline at end of file
diff --git a/packages/mail/package.json b/packages/mail/package.json
index ef6f8eb72..f862d2a20 100644
--- a/packages/mail/package.json
+++ b/packages/mail/package.json
@@ -1,8 +1,8 @@
 {
   "name": "@sendgrid/mail",
-  "description": "SendGrid NodeJS mail service",
+  "description": "Twilio SendGrid NodeJS mail service",
   "version": "6.3.1",
-  "author": "SendGrid <dx@sendgrid.com> (sendgrid.com)",
+  "author": "Twilio SendGrid <dx@sendgrid.com> (sendgrid.com)",
   "contributors": [
     "Kyle Partridge <kyle.partridge@sendgrid.com>",
     "David Tomberlin <david.tomberlin@sendgrid.com>",
diff --git a/packages/subscription-widget/README.md b/packages/subscription-widget/README.md
index fa69bed40..5e274961f 100644
--- a/packages/subscription-widget/README.md
+++ b/packages/subscription-widget/README.md
@@ -1,21 +1,21 @@
 # Email Subscription Widget with Double Opt-In
 
-Note: This is not an officially supported SendGrid library
+Note: This is not an officially supported Twilio SendGrid library
 
-This is an open source repository to add a flexible email subscription widget, like the one shown below, to any website using [SendGrid](https://sendgrid.com/). After following these directions, you'll be able to add a snippet of HTML to any website that will collect email addresses for your app or business. This widget utilizes [double opt-in](https://sendgrid.com/docs/Glossary/opt_in_email.html) functionality, which means users must confirm their email addresses by clicking an email that is automatically sent to their provided email address.
+This is an open source repository to add a flexible email subscription widget, like the one shown below, to any website using [Twilio SendGrid](https://sendgrid.com/). After following these directions, you'll be able to add a snippet of HTML to any website that will collect email addresses for your app or business. This widget utilizes [double opt-in](https://sendgrid.com/docs/Glossary/opt_in_email.html) functionality, which means users must confirm their email addresses by clicking an email that is automatically sent to their provided email address.
 
 ![alt text](https://github.com/devchas/sendgrid_subscription_widget/blob/master/server/static/sample-form.png "Sample Form")
 
 ## Requirements
 
 Before following these instructions, you must:
-* Have a SendGrid account - [sign up here](https://sendgrid.com/pricing/)
+* Have a Twilio SendGrid account - [sign up here](https://sendgrid.com/pricing/)
 * Sign up for a [free Heroku account](https://signup.heroku.com/)
 
 ## Instructions
 
-### Initial SendGrid Set-up - Create API Key & Contact List
-To begin, you will first need to create an API key on SendGrid's website. Once logged in, go to Settings -> API Keys, and click the blue button in the top right corner of the website.  You will be creating a General API key, which must have *Full Access* to *Mail Send* and *Marketing Campaigns*.  Keep this API key in a *safe* and *private* location.  You will need it later.
+### Initial Twilio SendGrid Set-up - Create API Key & Contact List
+To begin, you will first need to create an API key on Twilio SendGrid's website. Once logged in, go to Settings -> API Keys, and click the blue button in the top right corner of the website.  You will be creating a General API key, which must have *Full Access* to *Mail Send* and *Marketing Campaigns*.  Keep this API key in a *safe* and *private* location.  You will need it later.
 
 ### Fork this Repository to Create Your Copy
 If you are unfamiliar with Github, just click the button that reads *Fork* in the top right of this page. Doing this will provide you with your copy.  You'll need to change a few basic settings in your copy.
@@ -77,7 +77,7 @@ Navigate to the index.html file (server -> static -> index.html) and change the
 Next, configure your API key as an environmental variable, which can be done either through Heroku's user interface or the Heroku CLI as shown in [these directions](https://devcenter.heroku.com/articles/config-vars). Updating the environment variable in your Heroku account can be done by logging into your Heroku account, navigate to your newly deployed app, and clicking settings. Inside the settings page, you will see an option to "Reveal Config Vars".  You must name your variable holding your API key *SG_API_KEY*.
 
 ### Enable Event Webhook
-The final step is to enable the event webhook on your SendGrid account. This will allow the opt-in component of the signup to function correctly. To set up an event webhook, navigate to Settings -> Mail Settings, and then click on *Event Notification*.  
+The final step is to enable the event webhook on your Twilio SendGrid account. This will allow the opt-in component of the signup to function correctly. To set up an event webhook, navigate to Settings -> Mail Settings, and then click on *Event Notification*.  
 
 Make sure the toggle in the top left of that section is set to *ON*. Click edit. Enter the root URL of your Heroku app + '/signup'. The following is an example URL: https://your_heroku_app_name.herokuapp.com/signup. 
 
@@ -85,7 +85,7 @@ For the types of events to receive, make sure to select only *Clicked*. Then, cl
 
 
 ### Test Your Widget
-To quickly test that your subscription widget is working correctly, you may navigate to the root URL of your Heroku app and enter an email that you have access to. If everything is working, you should receive an email with a link to confirm your subscription. Upon clicking this link, the email should be added to the SendGrid contact list you created earlier.
+To quickly test that your subscription widget is working correctly, you may navigate to the root URL of your Heroku app and enter an email that you have access to. If everything is working, you should receive an email with a link to confirm your subscription. Upon clicking this link, the email should be added to the Twilio SendGrid contact list you created earlier.
 
 ## Usage and Customization
 
@@ -98,7 +98,7 @@ To use this widget, once you've followed the setup steps above, drop all of the
 You may change the look and feel of the form or create a new one.  The form will continue to work so long as the action is what you specified earlier, the method is a POST, and there is an input element with name *email*.  The default widget comes with three fields: 1) email, 2) first name, 3) last name.  You may remove first and/or last name if you so choose.  Also, you may change the form's styling by adjusting the CSS contained in index.html.
 
 #### Adding New Fields
-You may also add [custom fields](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/custom_fields.html) to the form to save other information about your users during the sign up process. To do so, simply add an input field with the name(s) of your custom field(s). If you add a custom field to your form that does not already exist in your SendGrid account, one will automatically be created with the name specified in the form. The example below shows a form with the custom field "favorite_color".
+You may also add [custom fields](https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/custom_fields.html) to the form to save other information about your users during the sign up process. To do so, simply add an input field with the name(s) of your custom field(s). If you add a custom field to your form that does not already exist in your Twilio SendGrid account, one will automatically be created with the name specified in the form. The example below shows a form with the custom field "favorite_color".
 
 ```html
 <form action="https://your_heroku_app_name.herokuapp.com/confirmEmail" method="post">
diff --git a/packages/subscription-widget/app.json b/packages/subscription-widget/app.json
index 4b46149da..1024b9130 100644
--- a/packages/subscription-widget/app.json
+++ b/packages/subscription-widget/app.json
@@ -2,5 +2,5 @@
   "name": "Email Double Opt-In",
   "description": "Double opt-in email automation",
   "repository": "https://github.com/devchas/sendgrid_subscription_widget",
-  "keywords": ["email", "SendGrid"]
+  "keywords": ["email", "SendGrid", "Twilio"]
 }
\ No newline at end of file
diff --git a/use-cases/README.md b/use-cases/README.md
index 907178ad3..6609c8d26 100644
--- a/use-cases/README.md
+++ b/use-cases/README.md
@@ -1,4 +1,4 @@
-This documentation provides examples for specific SendGrid v3 API use cases. Please [open an issue](https://github.com/sendgrid/sendgrid-nodejs/issues) or make a pull request for any email use cases you would like us to document here. Thank you!
+This documentation provides examples for specific Twilio SendGrid v3 API use cases. Please [open an issue](https://github.com/sendgrid/sendgrid-nodejs/issues) or make a pull request for any email use cases you would like us to document here. Thank you!
 
 # Email Use Cases
 * [Send a Single Email to a Single Recipient](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/single-email-single-recipient.md)
@@ -19,6 +19,7 @@ This documentation provides examples for specific SendGrid v3 API use cases. Ple
   * [Specifying Categories](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/categories.md)
   * [Kitchen Sink - an example with all settings used](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/kitchen-sink.md)
 
-# Non-mail Use Cases
+# Non-Email Use Cases
+* [Send a SMS Message](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/sms.md)
 * [How to Setup a Domain Whitelabel](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/domain-white-label.md)
 * [How to View Email Statistics](https://github.com/sendgrid/sendgrid-nodejs/blob/master/use-cases/email-stats.md)
diff --git a/use-cases/domain-white-label.md b/use-cases/domain-white-label.md
index f754e820c..27d7f5718 100644
--- a/use-cases/domain-white-label.md
+++ b/use-cases/domain-white-label.md
@@ -2,4 +2,4 @@
 
 You can find documentation for how to setup a domain whitelabel via the UI [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/setup_domain_whitelabel.html) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#whitelabel).
 
-Find more information about all of SendGrid's whitelabeling related documentation [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/index.html).
+Find more information about all of Twilio SendGrid's whitelabeling related documentation [here](https://sendgrid.com/docs/Classroom/Basics/Whitelabel/index.html).
diff --git a/use-cases/email-stats.md b/use-cases/email-stats.md
index f48a6bb90..ac7f97f2b 100644
--- a/use-cases/email-stats.md
+++ b/use-cases/email-stats.md
@@ -2,4 +2,4 @@
 
 You can find documentation for how to view your email statistics via the UI [here](https://app.sendgrid.com/statistics) and via API [here](https://github.com/sendgrid/sendgrid-nodejs/blob/master/packages/client/USAGE.md#stats).
 
-Alternatively, we can post events to a URL of your choice via our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html) about events that occur as SendGrid processes your email.
+Alternatively, we can post events to a URL of your choice via our [Event Webhook](https://sendgrid.com/docs/API_Reference/Webhooks/event.html) about events that occur as Twilio SendGrid processes your email.
diff --git a/use-cases/sms.md b/use-cases/sms.md
new file mode 100644
index 000000000..20ffed96e
--- /dev/null
+++ b/use-cases/sms.md
@@ -0,0 +1,57 @@
+Following are the steps to add Twilio SMS to your app:
+
+## 1. Obtain a Free Twilio Account
+
+Sign up for a free Twilio account [here](https://www.twilio.com/try-twilio?source=sendgrid-nodejs).
+
+## 2. Update Your Environment Variables
+
+You can obtain your Account Sid and Auth Token from [twilio.com/console](https://twilio.com/console).
+
+### Mac
+
+```bash
+echo "export TWILIO_ACCOUNT_SID='YOUR_TWILIO_ACCOUNT_SID'" > twilio.env
+echo "export TWILIO_AUTH_TOKEN='YOUR_TWILIO_AUTH_TOKEN'" >> twilio.env
+echo "twilio.env" >> .gitignore
+source ./twilio.env
+```
+
+### Windows
+
+Temporarily set the environment variable (accessible only during the current CLI session):
+
+```bash
+set TWILIO_ACCOUNT_SID=YOUR_TWILIO_ACCOUNT_SID
+set TWILIO_AUTH_TOKEN=YOUR_TWILIO_AUTH_TOKEN
+```
+
+Permanently set the environment variable (accessible in all subsequent CLI sessions):
+
+```bash
+setx TWILIO_ACCOUNT_SID "YOUR_TWILIO_ACCOUNT_SID"
+setx TWILIO_AUTH_TOKEN "YOUR_TWILIO_AUTH_TOKEN"
+```
+
+## 3. Install the Twilio Helper Library
+
+`npm install twilio`
+
+Then, you can execute the following code.
+
+```js
+var accountSid = process.env.TWILIO_ACCOUNT_SID;
+var authToken = process.env.TWILIO_AUTH_TOKEN;
+
+var twilio = require('twilio');
+var client = new twilio(accountSid, authToken);
+
+client.messages.create({
+    body: 'Hello from Node',
+    to: '+12345678901',  // Text this number
+    from: '+12345678901' // From a valid Twilio number
+})
+.then((message) => console.log(message.sid));
+```
+
+For more information, please visit the [Twilio SMS Node.js documentation](https://www.twilio.com/docs/sms/quickstart/node).