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

Update showcase info for miyamadojinja.com #22620

Conversation

mnishiguchi
Copy link
Contributor

@mnishiguchi mnishiguchi commented Mar 28, 2020

Description

This is a minor improvement for Miyamadojinja's showcase info, including a typo.

TL;DR: Japanses (wrong) -> Japanese (correct)

Related PR: #20856

@mnishiguchi mnishiguchi requested a review from a team as a code owner March 28, 2020 03:39
@mnishiguchi mnishiguchi force-pushed the mnishiguchi/update-miyamadojinja-showcase branch from 08ccae2 to 4dfd4a2 Compare March 28, 2020 03:43
@mnishiguchi mnishiguchi force-pushed the mnishiguchi/update-miyamadojinja-showcase branch from 4dfd4a2 to 07f5e29 Compare March 28, 2020 03:44
@mnishiguchi
Copy link
Contributor Author

There are four typo warnings but they are correct Japanese words.

@laurieontech
Copy link
Contributor

laurieontech commented Mar 30, 2020

Thanks for the PR! Since you're including a github link it'd be great if that README file including full instructions for running the site. For example: git clone, cd , npm install.

@mnishiguchi
Copy link
Contributor Author

@laurieontech You are absolutely right. I updated the site repo's README with instructions for installation. https://github.com/mnishiguchi/miyamadojinja/blob/master/README.md

@laurieontech
Copy link
Contributor

Thanks for the PR!

@laurieontech laurieontech merged commit babc491 into gatsbyjs:master Mar 30, 2020
@mnishiguchi mnishiguchi deleted the mnishiguchi/update-miyamadojinja-showcase branch March 30, 2020 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants