Merge pull request #10 from gatsbyjs/textlint-fix

uetchy · web-flow · commit f84c9e14a593 · 2020-01-14T09:26:21.000+09:00
chore: textlint --fix
diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
@@ -9,5 +9,5 @@ jobs:
         uses: tsuyoshicho/action-textlint@v1
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
-          reporter: github-pr-check
+          reporter: github-pr-review
           textlint_flags: "docs/**/*.md"
diff --git a/.textlintrc.js b/.textlintrc.js
@@ -14,11 +14,18 @@ module.exports = {
     // https://github.com/textlint-rule/textlint-rule-prh
     prh: { rulePaths: ["./prh.yml"] },
     "ja-technical-writing/no-exclamation-question-mark": false, // 文末の感嘆符を許可
+    "ja-technical-writing/max-ten": {
+      // 句点の数を緩和
+      max: 5,
+    },
+    "ja-technical-writing/ja-no-weak-phrase": false, // 弱い表現の許容
     "ja-technical-writing/sentence-length": false, // 翻訳完了後に有効化
     "ja-technical-writing/max-comma": false, // 翻訳完了後に有効化
-    "textlint-rule-ja-hiragana-hojodoushi": true,
-    "textlint-rule-ja-hiragana-fukushi": true,
-    "textlint-rule-ja-hiragana-keishikimeishi": true,
+    "ja-technical-writing/ja-no-mixed-period": {
+      allowPeriodMarks: ["："],
+    },
+    "textlint-rule-ja-hiragana-hojodoushi": true, // ひらがなにしたほうが良い補助動詞
+    "textlint-rule-ja-hiragana-fukushi": true, // ひらがなにしたほうが良い副詞
   },
   filters: {
     // https://github.com/textlint/textlint-filter-rule-comments
diff --git a/README.md b/README.md
@@ -19,7 +19,7 @@
 
 ### 作業の重複を防ぐための宣言
 
-未翻訳記事の翻訳を行いたい場合は、他の人との作業の重複を防ぐため、[この Issue](https://github.com/gatsbyjs/gatsby-ja/issues/1) での宣言をお願いします。
+未翻訳記事を翻訳したい場合は、他の人との作業の重複を防ぐため、[この Issue](https://github.com/gatsbyjs/gatsby-ja/issues/1) での宣言をお願いします。
 
 ### 翻訳スタイルガイド
 
@@ -29,12 +29,12 @@
 
 ## 参考リンク
 
-* [翻訳スタイルガイド](/style-guide.md)
-* [Gatsby翻訳ガイド](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/)
-* [Gatsby Discord](https://gatsby.dev/discord)
+- [翻訳スタイルガイド](/style-guide.md)
+- [Gatsby 翻訳ガイド](https://www.gatsbyjs.org/contributing/gatsby-docs-translation-guide/)
+- [Gatsby Discord](https://gatsby.dev/discord)
 
 ## メンテナー
 
-* [**@hirotaka**](https://github.com/hirotaka)
-* [**@Naturalclar**](https://github.com/Naturalclar)
-* [**@uetchy**](https://github.com/uetchy)
+- [**@hirotaka**](https://github.com/hirotaka)
+- [**@Naturalclar**](https://github.com/Naturalclar)
+- [**@uetchy**](https://github.com/uetchy)
diff --git a/docs/contributing/code-of-conduct.md b/docs/contributing/code-of-conduct.md
@@ -26,9 +26,9 @@ title: Gatsby コントリビューター行動規範
 
 ## 私たちの責任
 
-プロジェクトのメンテナーは、許容できる行動の基準を明確にすることに責任があります。また、何かしらの許容できない行動に対応する、適切かつ公平な是正処置をとることが期待されています。
+プロジェクトのメンテナーは、許容できる行動の基準を明確にする責任があります。また、何かしらの許容できない行動に対応する、適切かつ公平な是正処置をとることが期待されています。
 
-プロジェクトのメンテナーは、この行動規範に沿っていない、コメント、コミット、コード、wiki編集、issue、その他の貢献を削除、編集、拒否する権利と義務を有します。また、他の不適切、脅迫的、攻撃的、嫌がらせと考えられる行動を取ったコントリビューターを一時的もしくは恒久的に追放する権利と義務を有します。
+プロジェクトのメンテナーは、この行動規範に沿っていない、コメント、コミット、コード、wiki 編集、issue、その他の貢献を削除、編集、拒否する権利と義務を有します。また、他の不適切、脅迫的、攻撃的、嫌がらせと考えられる行動を取ったコントリビューターを一時的もしくは恒久的に追放する権利と義務を有します。
 
 ## 適用範囲
 
@@ -38,7 +38,7 @@ title: Gatsby コントリビューター行動規範
 
 暴言、嫌がらせ、またはそれ以外の受け入れられない行動は、[conduct@gatsbyjs.com](mailto:conduct@gatsbyjs.com) に連絡して、プロジェクトチームに報告される可能性があります。すべての苦情は、レビュー、調査され、必要かつ適切と判断された対応がとられます。プロジェクトチームは、事象の報告者に関する守秘義務があります。具体的な執行に関する詳細が別途設定されているかもしれません。
 
-この行動規範に誠意を持って従うまたは執行することができないプロジェクトのメンテナーは、プロジェクトをリードしている他のメンバーの判断により、一時的または恒久的な影響を受けることがあります。
+この行動規範に誠意を持って従うことができない、または執行ができないプロジェクトのメンテナーは、プロジェクトをリードしている他のメンバーの判断により、一時的または恒久的な影響を受けることがあります。
 
 もし、再三の注意の後も悪質なコメントやハラスメントが継続する場合は、Gatsby チームはその方を Gatsby の Github のリポジトリから追放し、SNS 等でブロックする権利を留保します。この決定は必ず二人以上のチームメンバーの合意によって行われます。
 
diff --git a/docs/docs/awesome-gatsby-resources.md b/docs/docs/awesome-gatsby-resources.md
@@ -36,7 +36,7 @@ See the [unofficial list of themes](https://gatsbytemplates.io/)
 - [2018-07-18: The Great GatsbyJS w/ Jason Lengstorf on The Changelog #306](https://changelog.com/podcast/306)
 - [2018-04-17: Gatsby.js w/Jason Lengstorf](https://spec.fm/podcasts/toolsday/134337)
 - [2018-02-28: syntax.fm on Static Site Generators (lots of Gatsby love)](https://syntax.fm/show/034/why-static-site-generators-are-awesome)
-- [2017-09-21: Kyle Mathews on JAMSTACK radio on "Static Site Generation with GatsbyJS](https://www.heavybit.com/library/podcasts/jamstack-radio/ep-22-static-site-generation-with-gatsbyjs/)
+- [2017-09-21: Kyle Mathews on JAMSTACK radio on "Static Site Generation with GatsbyJS"](https://www.heavybit.com/library/podcasts/jamstack-radio/ep-22-static-site-generation-with-gatsbyjs/)
 - [2017-07-21: Kyle Mathews on Web of Tomorrow](https://www.orbit.fm/weboftomorrow/39/)
 - [2017-08-17: Kyle Mathews on Software Engineering Daily](https://softwareengineeringdaily.com/2017/08/17/gatsbyjs-with-kyle-mathews/)
 
diff --git a/docs/docs/end-to-end-testing.md b/docs/docs/end-to-end-testing.md
@@ -34,7 +34,7 @@ Last but not least you add additional scripts to your `package.json` to run Cypr
 
 Run `npm run test:e2e` in your command line and see Cypress running for the first time. A folder named `cypress` will be created at the root of your project and a new application window will pop up. [Cypress' getting started guide](https://docs.cypress.io/guides/getting-started/writing-your-first-test.html#) is a good start to learn how to write tests!
 
-_Important note_: If you are running Gatsby with the `--https` flag, whether using your own or automatically generated certificates, you will also need to tell `start-server-and-test` to disable HTTPS certificate checks (otherwise it will wait forever and never actually launch Cypress. You do this by passing in an environmental variable: `START_SERVER_AND_TEST_INSECURE=1`. [start-server-and-test docs](https://github.com/bahmutov/start-server-and-test#disable-https-certificate-checks).
+_Important note_: If you are running Gatsby with the `--https` flag, whether using your own or automatically generated certificates, you will also need to tell `start-server-and-test` to disable HTTPS certificate checks (otherwise it will wait forever and never actually launch Cypress). You do this by passing in an environmental variable: `START_SERVER_AND_TEST_INSECURE=1`. [start-server-and-test docs](https://github.com/bahmutov/start-server-and-test#disable-https-certificate-checks).
 
 This means your `test:e2e` script would look like this:
 
diff --git a/docs/docs/gatsby-core-philosophy.md b/docs/docs/gatsby-core-philosophy.md
@@ -51,7 +51,7 @@ When this incantation is simple and takes seconds, we can easily get lost for ho
 
 Developers, designers, demand-gen marketers, copywriters -- every stakeholder in a website project _can_ feel this -- with proper tooling.
 
-As Bret Victor suggested in _Inventing on Principle_, each creator needs "an immediate connection to what they're making.”
+As Bret Victor suggested in _Inventing on Principle_, each creator needs "an immediate connection to what they're making."
 
 These instant feedback loops are often felt near the beginning of projects. But they can quickly be drowned by project complexity.
 
@@ -91,7 +91,7 @@ For more on this, look at [the features Gatsby bundles together](/features).
 
 ### Progressively disclose complexity
 
-One concept UX designers use to make applications easier to learn and less error-prone is called “progressive disclosure".
+One concept UX designers use to make applications easier to learn and less error-prone is called "progressive disclosure".
 
 If you were designing a user interface, you might move advanced or rarely-used features to a secondary screen, such as "advanced settings".
 
diff --git a/docs/docs/gatsby-image.md b/docs/docs/gatsby-image.md
@@ -176,7 +176,7 @@ In a query, you can specify options for fluid images.
 - `maxWidth` (int, default: 800)
 - `maxHeight`(int)
 - `quality` (int, default: 50)
-- `srcSetBreakpoints` (array of int, default: [])
+- `srcSetBreakpoints` (array of int, default: `[]`)
 - `fit` (string, default: `[sharp.fit.cover][6]`)
 - `background` (string, default: `rgba(0,0,0,1)`)
 
diff --git a/docs/docs/index.md b/docs/docs/index.md
@@ -9,7 +9,7 @@ Gatsby は、React のための高速でモダンな静的サイトジェネレ
 
 ## Gatsby ことはじめ
 
-Gatsby に入門するために、大きくふたつの方法が用意されています。
+Gatsby に入門する方法は、大きく分けてふたつあります。
 
 1. [チュートリアル](/tutorial/): Gatsby をインストールして、新しいプロジェクトを始める方法をステップ・バイ・ステップ方式で学びます。Gatsby や Web 開発に詳しくないような人を念頭に書かれていますが、もちろんあらゆるレベルの開発者にとっても有用なガイドです。
 2. [クイックスタート](/docs/quick-start): Gatsby をインストールして新しいプロジェクトを作成する方法を簡潔にまとめたページです。
diff --git a/docs/docs/lower-bids-more-profit.md b/docs/docs/lower-bids-more-profit.md
@@ -8,7 +8,7 @@ After identifying projects that are a good fit for Gatsby, they will bid _signif
 
 Ben Robertson, of the 80-person Mediacurrent agency, [explains this strategy](https://www.youtube.com/watch?v=QiocnDGnKfs&feature=youtu.be&t=1145) in the context of Mediacurrent's work on the citysprings.com website for the city of Sandy Springs, GA:
 
-> "This was an experimental project for us. We had done decoupled Drupal before, but this was our first project as a team that was using Gatsby and it was a budget that was actually significantly under what we would charge for a full Drupal 8 build. And that was scary!
+> "This was an experimental project for us. We had done decoupled Drupal before, but this was our first project as a team that was using Gatsby and it was a budget that was actually significantly under what we would charge for a full Drupal 8 build. And that was scary!"
 
 Not only was the team able to deliver the project on time and under budget, but the client was so happy they were able to [get additional work immediately](https://www.youtube.com/watch?v=QiocnDGnKfs&feature=youtu.be&t=1531):
 
diff --git a/docs/docs/migrating-from-v0-to-v1.md b/docs/docs/migrating-from-v0-to-v1.md
@@ -324,5 +324,5 @@ change making `this.props.children` a function call so `this.props.children()`.
 The rational for this change is described
 [in this PR comment](https://github.com/gatsbyjs/gatsby/pull/940#issuecomment-300878300).
 
-Nested layouts (similar to the nested _template feature) are \_not_ supported yet
+Nested layouts (similar to the nested _template feature_) are **not** supported yet
 but are on the roadmap for v1.
diff --git a/docs/docs/schema-generation.md b/docs/docs/schema-generation.md
@@ -48,7 +48,7 @@ The majority of schema generation code kicks off in [build-node-types.js](https:
 
 Gatsby infers GraphQL Types from the fields on the sourced and transformed nodes. But before that, we allow plugins to create their own custom fields. For example, `source-filesystem` creates a [publicURL](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-filesystem/src/extend-file-node.js#L11) field that when resolved, will copy the file into the `public/static` directory and return the new path.
 
-To declare custom fields, plugins implement the [setFieldsOnGraphQLNodeType](/docs/node-apis/#setFieldsOnGraphQLNodeType) API and apply the change only to types that they care about (e.g. source-filesystem [only proceeds if type.name = `File`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-filesystem/src/extend-file-node.js#L6). During schema generation, Gatsby will call this API, allowing the plugin to declare these custom fields, [which are returned](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/schema/build-node-types.js#L151) to the main schema process.
+To declare custom fields, plugins implement the [setFieldsOnGraphQLNodeType](/docs/node-apis/#setFieldsOnGraphQLNodeType) API and apply the change only to types that they care about (e.g. source-filesystem [only proceeds if type.name = `File`](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-filesystem/src/extend-file-node.js#L6)). During schema generation, Gatsby will call this API, allowing the plugin to declare these custom fields, [which are returned](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/schema/build-node-types.js#L151) to the main schema process.
 
 ### 2. Create a "GQLType"
 
diff --git a/docs/docs/winning-over-developers.md b/docs/docs/winning-over-developers.md
@@ -65,7 +65,7 @@ You may find that many of your developer friends and colleagues have some questi
 
 Sometimes the most effective way to get a developer's attention is to show them examples of real sites and dev teams using Gatsby. Here are some case studies you might want to share:
 
-- [Delicious Simplicity <3 Gatsby: Building Happily Ever After](/blog/2019-06-08-delicious-simplicity-case-study-part-1/)
+- [Delicious Simplicity ❤️ Gatsby: Building Happily Ever After](/blog/2019-06-08-delicious-simplicity-case-study-part-1/)
 - [Beyond Static: Haptic Media Uses Gatsby to Build a Dynamic Web App](/blog/2019-02-05-hapticmedia-case-study/)
 - [IBM Uses Gatsby to Manage Enterprise-Level Content](/blog/2018-12-17-ibm-case-study/#big-company-big-website)
 
diff --git a/docs/tutorial/index.md b/docs/tutorial/index.md
diff --git a/package.json b/package.json
diff --git a/prh.yml b/prh.yml
diff --git a/yarn.lock b/yarn.lock
