Skip to content

Commit

Permalink
docs(process): tiny typos (ionic-team#18855)
Browse files Browse the repository at this point in the history
  • Loading branch information
rtpHarry authored and manucorporat committed Jul 22, 2019
1 parent fb18f3b commit cf27063
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/PROCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ If the issue is a support question, the submitter should be redirected to our [f

### Incomplete Template

If the issue template has not been filled out completely, the issue should be closed and locked. The submitter should be informed top re-submit the issue making sure they fill the form out completely. Use the `ionitron: missing template` label to accomplish this.
If the issue template has not been filled out completely, the issue should be closed and locked. The submitter should be informed to re-submit the issue making sure they fill the form out completely. Use the `ionitron: missing template` label to accomplish this.

### Issues with Open Questions

Expand All @@ -77,7 +77,7 @@ NOTE: be sure to perform those actions in the order stated. If you add the comme

If there is a response to the question, the bot will remove the `needs: reply` and apply the `triage` label. The issue will then go through the triage handling again.

if there is no response within 30 days, the issue will be closed and locked.
If there is no response within 30 days, the issue will be closed and locked.

## Workflow

Expand Down Expand Up @@ -248,4 +248,4 @@ Hotfixes bypass `master` and should only be used for urgent fixes that can't wai

1. Rewrite the commit message to `merge release-[VERSION]` with the proper release branch. For example, if this release is for `4.5.0`, the message would be `merge release-4.5.0`.

1. Submit a pull request from the release branch into `master`. Merge this pull request using the same commit format in the last step, to ensure any changes made on the release branch get added to future releases.
1. Submit a pull request from the release branch into `master`. Merge this pull request using the same commit format in the last step, to ensure any changes made on the release branch get added to future releases.

0 comments on commit cf27063

Please sign in to comment.