Skip to content

Commit c217c41

Browse files
authored
Fix a typo (github#26298)
1 parent d4a3424 commit c217c41

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/repositories/working-with-files/using-files/working-with-non-code-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -341,7 +341,7 @@ $ jupyter nbconvert --to html <em>NOTEBOOK-NAME.ipynb</em>
341341
- [Gallery of Jupyter Notebooks](https://github.com/jupyter/jupyter/wiki/A-gallery-of-interesting-Jupyter-Notebooks)
342342

343343
{% if mermaid %}
344-
## Displaying mermaid files on {% data variables.product.prodname_dotcom %}
344+
## Displaying Mermaid files on {% data variables.product.prodname_dotcom %}
345345

346346
{% data variables.product.product_name %} supports rendering Mermaid files within repositories. Commit the file as you would normally using a `.mermaid` or `.mmd` extension. Then, navigate to the path of the Mermaid file on {% data variables.product.prodname_dotcom %}.
347347

@@ -367,7 +367,7 @@ If the chart displays, but does not appear as you'd expect, you can create a new
367367

368368
#### Known issues
369369

370-
* Sequence diagram charts frequently render with additional padding below the chart, with more padding added as the chart size increases. This is a known issue with the mMermaid library.
370+
* Sequence diagram charts frequently render with additional padding below the chart, with more padding added as the chart size increases. This is a known issue with the Mermaid library.
371371
* Actor nodes with popover menus do not work as expected within sequence diagram charts. This is due to a discrepancy in how JavaScript events are added to a chart when the Mermaid library's API is used to render a chart.
372372
* Not all charts are a11y compliant. This may affect users who rely on a screen reader.
373373

0 commit comments

Comments
 (0)