From 512be4c8e1eb637213146157b7a8cae23f0f2fe6 Mon Sep 17 00:00:00 2001 From: Ryan Meredith Date: Thu, 4 Apr 2019 10:15:44 -0400 Subject: [PATCH] Text Improvements --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- .github/ISSUE_TEMPLATE/question.md | 4 +--- CONTRIBUTING.md | 2 +- 3 files changed, 3 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 74ebe9e3ad..385782a424 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -8,7 +8,7 @@ assignees: '' --- **Describe the bug** -A clear and concise description of what the bug is. +A clear and concise description of the bug. **To Reproduce** Steps to reproduce the behavior: diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md index d26942d863..b9fefaa534 100644 --- a/.github/ISSUE_TEMPLATE/question.md +++ b/.github/ISSUE_TEMPLATE/question.md @@ -1,10 +1,8 @@ --- name: Question -about: Ask a question from the developers +about: Ask the developers a question title: '' labels: question assignees: '' --- - - diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4880c092f0..a082f6f8c3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -29,7 +29,7 @@ Patches should be submitted in the form of Pull Requests to the Ghidra [repository] on GitHub. But first, consider the following tips to ensure a smooth process when submitting a patch: -- Ensure that the patch compiles and does not break any build-time tests +- Ensure that the patch compiles and does not break any build-time tests. - Be understanding, patient, and friendly; developers may need time to review your submissions before they can take action or respond. This does not mean your contribution is not valued. If your contribution has not received a