Jason Grout hace 5 años
padre
commit
2243965011
Se han modificado 2 ficheros con 2 adiciones y 4 borrados
  1. 1 3
      .github/ISSUE_TEMPLATE/bug_report.md
  2. 1 1
      docs/source/getting_started/issue.rst

+ 1 - 3
.github/ISSUE_TEMPLATE/bug_report.md

@@ -14,7 +14,6 @@ https://jupyterlab.readthedocs.io/en/latest/getting_started/issue.html
 
 <!--Describe the bug clearly and concisely. Include screenshots if possible-->
 
-
 ## Reproduce
 
 <!--Describe step-by-step instructions to reproduce the behavior-->
@@ -27,13 +26,12 @@ https://jupyterlab.readthedocs.io/en/latest/getting_started/issue.html
 <!--Describe how you diagnosed the issue. See the guidelines at
  https://jupyterlab.readthedocs.io/en/latest/getting_started/issue.html -->
 
-
 ## Expected behavior
 
 <!--Describe what you expected to happen-->
 
-
 ## Context
+
 <!--Complete the following for context, and add any other relevant context-->
 
 - Operating System and version:

+ 1 - 1
docs/source/getting_started/issue.rst

@@ -29,7 +29,7 @@ If you find a problem in JupyterLab, please follow the steps below to diagnose a
    If you are using pipenv: (someone please update this area with instructions for creating a new environment in pipenv)
 
    - I cannot reproduce this issue in a clean environment: The problem is probably not in JupyterLab itself. Go to step 2.
-   - I can reproducethis issue in a clean environment: Go to step 3.
+   - I can reproduce this issue in a clean environment: Go to step 3.
 2. Perhaps the issue is in one of the JupyterLab extensions you had installed. Install any JupyterLab extensions you had one at a time, checking for the issue after each one.
 
    - I can reproduce the issue after installing a particular extension: That extension may be causing the problem. File an issue with that extension's issue tracker. Be sure to mention what you have done here to narrow the problem down.