From 1853311347b59e0c51dea2af1a592f347e4176bc Mon Sep 17 00:00:00 2001 From: Jared Tobin Date: Wed, 28 Aug 2019 13:31:38 -0230 Subject: [PATCH] contributing: text fixup 'clear' is preferred to "clear, obvious" here. --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4a95bf997..cb447264d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -211,11 +211,11 @@ bugs, performance problems, feature requests, and so on. If you encounter any issues when developing on urbit, feel free to submit a report about it here. A good bug report, description of a crash, etc., should ideally be -*reproducible*, with clear, obvious steps as to how another developer can -replicate and examine your problem. That said, this isn't always possible -- -some bugs depend on having created a complicated or unusual state, or can -otherwise simply be difficult to trigger again (say, you encountered it in the -last continuity era). +*reproducible*, with clear steps as to how another developer can replicate and +examine your problem. That said, this isn't always possible -- some bugs +depend on having created a complicated or unusual state, or can otherwise +simply be difficult to trigger again (say, you encountered it in the last +continuity era). Your issue should thus at a minimum be *informative*. The best advice here is probably "don't write bad issues," where "bad" is a matter of judgment and