From 524fbca542f6419847a41d77cf62d7869372bf7f Mon Sep 17 00:00:00 2001 From: Nathan Woltman Date: Mon, 22 Apr 2019 12:59:52 -0400 Subject: [PATCH] fix: fix grammatical error (#145) --- content/next/index.md | 2 +- content/v1.0.0-beta.1/index.md | 2 +- content/v1.0.0-beta.2/index.md | 2 +- content/v1.0.0-beta.3/index.md | 2 +- content/v1.0.0-beta.4/index.md | 2 +- content/v1.0.0-beta/index.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/next/index.md b/content/next/index.md index 4a2985b..8c926cc 100644 --- a/content/next/index.md +++ b/content/next/index.md @@ -150,7 +150,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About diff --git a/content/v1.0.0-beta.1/index.md b/content/v1.0.0-beta.1/index.md index 792844b..cea4026 100644 --- a/content/v1.0.0-beta.1/index.md +++ b/content/v1.0.0-beta.1/index.md @@ -130,7 +130,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About diff --git a/content/v1.0.0-beta.2/index.md b/content/v1.0.0-beta.2/index.md index a099d26..a72a444 100644 --- a/content/v1.0.0-beta.2/index.md +++ b/content/v1.0.0-beta.2/index.md @@ -155,7 +155,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About diff --git a/content/v1.0.0-beta.3/index.md b/content/v1.0.0-beta.3/index.md index 7012f7b..5da2804 100644 --- a/content/v1.0.0-beta.3/index.md +++ b/content/v1.0.0-beta.3/index.md @@ -139,7 +139,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About diff --git a/content/v1.0.0-beta.4/index.md b/content/v1.0.0-beta.4/index.md index 0d99aef..d9b397b 100644 --- a/content/v1.0.0-beta.4/index.md +++ b/content/v1.0.0-beta.4/index.md @@ -151,7 +151,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About diff --git a/content/v1.0.0-beta/index.md b/content/v1.0.0-beta/index.md index 906c03b..b71ad4f 100644 --- a/content/v1.0.0-beta/index.md +++ b/content/v1.0.0-beta/index.md @@ -130,7 +130,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d ### Do all my contributors need to use the conventional commit specification? -No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. +No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge. ## About