open-source-guides
/
TRaSH-Guides
mirror of https://github.com/TRaSH-/Guides
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore(guide): fix exposed comment due to space after `!` (#1906)

Browse Source
pull/1909/head
TRaSH 3 weeks ago committed by GitHub
parent 769bdf736c
commit f52ca4bdcc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

2
docs/Radarr/Radarr-collection-of-custom-formats.md
Unescape View File

@ -540,7 +540,7 @@ We've made 3 guides related to this.
--8<-- "includes/cf-descriptions/dv.md"
<! -- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md` -->
<!-- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md` -->
??? example "JSON - [Click to show/hide]"

2
docs/Sonarr/sonarr-collection-of-custom-formats.md
Unescape View File

@ -541,7 +541,7 @@ We've made 3 guides related to this.
--8<-- "includes/cf-descriptions/dv.md"
<! -- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md`-->
<!-- the reason why we didn't use here `include-markdown` is because all the headers when using `include-markdown` will be looking in `/includes` and not the current markdown file, in this case the pointer to `#dv-webdl` in `includes/dv.md`-->
??? example "JSON - [Click to show/hide]"

Write Preview
Loading…
Cancel
Save