formatting

Change-Id: I69092dc6c2121bb780aed1b145ccd3eaabb0ff5d

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 6c8c8052b59dd315846fee5c21ce8a6c7795f167..f7e4fad364de563874c0e1cab632acb64d70b5e0 100644 (file)
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -13,14 +13,11 @@ If you are new to SQLAlchemy bug reports, please review our many examples
 of [well written bug reports](https://github.com/sqlalchemy/sqlalchemy/issues?q=is%3Aissue+label%3A%22great+mcve%22).   Each of these reports include the following features:
 
 1. a **succinct description of the problem** - typically a line or two at most
-2. **code to reproduce the problem**, otherwise known as
-   a [Minimal, Complete, and Verifiable](http://stackoverflow.com/help/mcve)
-   example.
+2. **succinct, dependency-free code which reproduces the problem**, otherwise known as a [Minimal, Complete, and Verifiable](http://stackoverflow.com/help/mcve) example.
 3. **complete stack traces for all errors**
 4. Other things as applicable:   **SQL log output**, **database backend and DBAPI driver**,
    **operating system**, **comparative performance timings** for performance issues.
 
-
 **Describe the bug**
 <!-- A clear and concise description of what the bug is. -->