Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarified how you can change the sender name #645

Merged
merged 1 commit into from
Oct 22, 2018

Conversation

Sundin
Copy link
Contributor

@Sundin Sundin commented Dec 20, 2017

Clarified how you can change the sender name, which was not entirely obvious. Also added it to the "kitchen sink" example and fixed the link to that section in the table of contents.

Fixes

Checklist

  • [ x ] I have made a material change to the repo (functionality, testing, spelling, grammar)
  • [ x ] I have read the [Contribution Guide] and my PR follows them.
  • [ x ] I updated my branch with the master branch.
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ x ] I have added necessary documentation about the functionality in the appropriate .md file
  • [ ] I have added in line documentation to the code I modified

Short description of what this PR does:

Some minor documentation updates.

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.

@thinkingserious thinkingserious added the status: code review request requesting a community code review or review from Twilio label Dec 20, 2017
@SendGridDX
Copy link
Collaborator

SendGridDX commented Dec 20, 2017

CLA assistant check
All committers have signed the CLA.

@thinkingserious
Copy link
Contributor

Thank you @Sundin!

We have added this to our backlog for review.

With Best Regards,

Elmer

clee
clee previously requested changes Feb 13, 2018
Copy link

@clee clee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, @Sundin! Unfortunately it looks like one of the changes you made broke a link in the USE_CASES.md document. Can you please fix the broken link and resubmit your PR? (It also looks like you may need to rebase against the latest master branch.)

@@ -15,7 +15,7 @@ This documentation provides examples for specific email use cases. Please [open
* [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)
* [Kitchen Sink - an example with all settings used](#kitchen-sink---an-example-with-all-settings-used)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change breaks the link to the Kitchen Sink example.

@clee clee added status: code review complete and removed status: code review request requesting a community code review or review from Twilio labels Feb 13, 2018
Clarified how you can change the sender name, which was not entirely obvious. Also added it to the "kitchen sink" example and fixed the link to that section in the table of contents.
@Sundin
Copy link
Contributor Author

Sundin commented Feb 14, 2018

Yep, it seems someone else fixed/changed that link during the two months since I created this PR. But my branch is now rebased with the latest changes and the link is working again!

@thinkingserious thinkingserious added difficulty: easy fix is easy in difficulty type: docs update documentation change not affecting the code status: ready for deploy code ready to be released in next deploy labels Mar 6, 2018
@benstokoe
Copy link

This was very helpful! :-)

@thinkingserious thinkingserious merged commit 6df133d into sendgrid:master Oct 22, 2018
@thinkingserious
Copy link
Contributor

Hello @Sundin,

Thanks again for the PR!

We want to show our appreciation by sending you some swag. Could you please fill out this form so we can send it to you? Thanks!

Team SendGrid DX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: easy fix is easy in difficulty status: ready for deploy code ready to be released in next deploy type: docs update documentation change not affecting the code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants