From 2d2f928c74318ee6d2dd2e49d266c26f076d626c Mon Sep 17 00:00:00 2001
From: Henry Pinkard <7969470+henrypinkard@users.noreply.github.com>
Date: Thu, 2 Nov 2023 08:39:50 -0700
Subject: [PATCH] Update bug_report.md

---
 .github/ISSUE_TEMPLATE/bug_report.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 7a54c871..8e9756b7 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -19,10 +19,19 @@ labels: bug
     configuration, it is likely unrelated to pycro-manager
     -->
 
-<!--The best bug reports are those which can be converted into an automated test. This ensures that once fixed, the bug can be avoided in the future. Tests are minimal scripts that reproduce the errant behavior using the Micro-Manager Demo configuration. Examples of tests can be found here: https://github.com/micro-manager/pycro-manager/tree/main/pycromanager/test
+<!--The best bug reports are those which can be converted into an automated test. 
+This ensures that once fixed, the bug can be avoided in the future. Tests are minimal 
+scripts that reproduce the errant behavior using the Micro-Manager Demo configuration.
+Examples of tests can be found here: 
+https://github.com/micro-manager/pycro-manager/tree/main/pycromanager/test
 -->
 
-<!--If you're familiar with the process of making pull requests, the most helpful type of bug report to create is one with a linked pull request with a new test added (which should currently fail due to the bug). More information running the testing framework can be found here: (https://github.com/micro-manager/pycro-manager/blob/main/Contributing.md#testing-the-code). If you're not familiar with this process, it is also okay to simply paste a snippet of code in this report.-->
+<!--If you're familiar with the process of making pull requests, the most helpful type of
+bug report to create is one with a linked pull request with a new test added (which should 
+currently fail due to the bug). More information running the testing framework can be found here:
+(https://github.com/micro-manager/pycro-manager/blob/main/Contributing.md#testing-the-code). 
+If you're not familiar with this process, it is also okay to simply paste a snippet of 
+code in this report.-->
 
 **Code for reproduction**
 ```python