From 3134d982c34fc1b3eaf004b2af0095ab9168787c Mon Sep 17 00:00:00 2001 From: arraybolt3 Date: Mon, 27 Feb 2023 16:55:39 +0000 Subject: [PATCH] Update 'Bugs' --- Bugs.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Bugs.md b/Bugs.md index 5251f52..6da3d84 100644 --- a/Bugs.md +++ b/Bugs.md @@ -85,11 +85,11 @@ The more complete you can make your bug report, the more likely it is to be fixe 1. The report is filed against an appropriate package. See below. 1. The report has a clear title. 1. The report description includes the following pieces: - -- Steps to reproduce (this is the most important thing; if it's not reproducible, it's nearly impossible to fix). - -- Expected results. - -- Actual results. - -- Affected versions. - -- Optionally, any other notes concerning conditions required to reproduce the bug, testing information, log files, etc. + - Steps to reproduce (this is the most important thing; if it's not reproducible, it's nearly impossible to fix). + - Expected results. + - Actual results. + - Affected versions. + - Optionally, any other notes concerning conditions required to reproduce the bug, testing information, log files, etc. 1. The report includes appropriate tags, but especially "lubuntu." #### General guidelines