From c5e85956b1a19d39d0b2f877ae010d034e7b6bbd Mon Sep 17 00:00:00 2001
From: jschall <mr.challinger@gmail.com>
Date: Sun, 12 Oct 2014 00:11:30 -0700
Subject: [PATCH] Update CONTRIBUTING.md

---
 CONTRIBUTING.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 037c1a7e3..5c772583f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,8 +12,9 @@ If you are reading this page, you are possibly interested in contributing to our
 
 * Make sure your bug is not a support issue. Support issues should go to [the APM forums](http://ardupilot.com/forum/). Support issues with logs attached should generally go to the "Log files, Tuning, and Analysis of Log files" section. If you're not sure you have a bug, you should seek support first.
 * Search for your bug, make sure it is not already reported. If it is already reported, make a comment on that issue.
-* Write a clear summary. Be specific about what component of the software you are writing about, and follow the convention: "Copter: blah blah blah"
-* Write a clear description, with **particularly clear steps** to reproduce the problem. Include logs that display the bug. 
+* Only report one bug per issue report.
+* Write a clear and concise summary. Be specific about what component of the software you are writing about, and follow the convention: "Copter: blah blah blah"
+* Write a clear and concise description, with **particularly clear steps** to reproduce the problem. Include logs that display the bug. **Try to report only facts in your issue report, keeping your assumptions out of it.** 
 * The majority of issues open now are good or acceptable by these guidelines. Please refer to them for examples.
 
 # Submitting patches
-- 
GitLab