danvics/ytdl-sub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(start): Various rST/Sphinx markup issues

Browse source
This commit is contained in:
Ross Patterson 2025-08-19 00:25:05 -07:00
parent dd87526987
commit cccdcf931a
No known key found for this signature in database
GPG key ID: 2EFF7CCE6828E359
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/source/guides/getting_started/index.rst
View file

@ -89,11 +89,11 @@ ancestor keys above that subscription describe the shared presets of that subscr
and all the other descendant subscriptions under them.
Genres are also more often shared between subscriptions than not. To accommodate that
reality, the ancestor keys of subscriptions may also use the special ``=`` prefix to
reality, the ancestor keys of subscriptions may also use the special ``= ...`` prefix to
specify genres that also apply to all descendant subscriptions.
Finally, ancestor keys may use the `` | `` special character to combine multiple presets
and/or genres for the descendant subscriptions beneath.
Finally, ancestor keys may use the ``... | ...`` special character to combine multiple
presets and/or genres for the descendant subscriptions beneath.
The configuration file extends pre-defined presets
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -109,7 +109,7 @@ Some of these descriptions are not technically complete. For example, a subscrip
use no preset at all and will just run ``yt-dlp`` without any customization or post
processing. The subscriptions file has special support for :ref:`overriding the presets
of all subscriptions in the file <config_reference/subscription_yaml:file preset>`. The
configuration file supports :ref"`a few special options
configuration file supports :ref:`a few special options
<config_reference/config_yaml:configuration>` that are not about defining presets. See
:doc:`the reference documentation <../../config_reference/index>` for technically
complete details, but for almost all of the use cases served by ``ytdl-sub``, the above