Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/tutorial/additional_features.rst`:
- Line 68: Replace the typo "hany" with the correct word "many" in the benchmark
description sentence ("When a job derived from the rule is executed, Snakemake
will measure the wall clock time, memory usage (in MiB), and several other hany
metrics...") so the sentence reads "...and several other many metrics..."
(actually better: "...and several other metrics...") — update the sentence in
docs/tutorial/additional_features.rst to remove the misspelling.
- Around line 215-218: The example mixes wildcard names "sample" and "dataset",
causing confusion; update the text so it consistently uses one name (preferably
"sample") throughout: change occurrences of `dataset="A.1"` and `dataset="A"` to
`sample="A.1"` and `sample="A"`, and keep the constraint example as
`{sample,[A-Z]+}.{group}` while referring to the output file
`{sample}.{group}.txt` and target `A.1.normal.txt` to ensure the wildcard name
is consistent.
- Around line 3-4: The section adornments (underlines) are too short for their
headings — e.g., the "Additional Features: Benchmarking, Modularization" heading
— causing reStructuredText "Title underline too short" warnings; update each
offending underline so its length matches or exceeds the length of the
corresponding heading text (extend the underline characters '-' or '=' to at
least the same number of characters as the heading) for the three sections
flagged so the document parses correctly.

In `@docs/tutorial/advanced.rst`:
- Around line 3-4: The top-level heading "Advanced: Configuration, Input
Functions, Logging" has an underline that's too short; update the underline
under that heading so it matches the heading length (repeat '-' to equal the
title's 49 characters) so the reStructuredText title underline is the same
length as the heading text.

In `@docs/tutorial/basics.rst`:
- Around line 96-103: The opening sentence "In Snakemake workflows are
defined..." is ungrammatical; update the first sentence to a concise,
grammatically correct form such as "In Snakemake, workflows are defined by
specifying rules in a ``Snakefile``." Also tighten surrounding wording for
clarity while preserving the mentions of rule names and directives (``rule``,
``Snakefile``, ``input``, ``output``, ``shell``) and ensure punctuation (commas
and backticks) is correct.

In `@docs/tutorial/tutorial.rst`:
- Around line 3-5: The title adornments for "Tutorial: A Basic Workflow" are too
short and cause an rst build warning; update both the overline and underline
surrounding the heading (the two lines of equals signs currently of length 21)
to match the heading length of 26 characters so both line 3 and line 5 use 26
equals signs each.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/conf.py`:
- Around line 317-321: The function oldheading_role uses mutable default args
options={} and content=[] which can leak state; change the signature to use
options=None and content=None, then inside oldheading_role set options = {} if
options is None and content = [] if content is None before calling anchor_role,
preserving the same call to anchor_role(name, rawtext, anchor_id, lineno,
inliner, options=options, content=content).

In `@docs/tutorial/basics.rst`:
- Around line 142-145: Replace the incorrect wording instances in the tutorial:
change the phrase "re-runs" to "re-run" where it appears in the sentence
"Snakemake will **only** re-runs jobs..." (search for the token "re-runs"), and
fix the typo "thefollowing" to "the following" (search for the token
"thefollowing") so the text reads correctly in both places.

---

Outside diff comments:
In `@docs/tutorial/tutorial.rst`:
- Around line 9-20: The referenced inline targets (Snakemake_, GNU Make`_,
Python_, Conda_, Singularity_) are missing and causing the Sphinx build to fail;
add explicit hyperlink targets for each reference (e.g., add reST target
definitions for Snakemake_, GNU Make_, Python_, Conda_, and Singularity_)
pointing to the correct external URLs and place them in this document (typically
at the end or top of tutorial.rst) so the references resolve during the docs
build; ensure the target names exactly match the reference tokens (including the
trailing underscore) used in the text.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/tutorial/basics.rst`:
- Around line 481-482: Remove the comma following the quoted file path in the
sentence containing "the execution plan for creating the file
``plots/quals.svg``" so the phrase reads smoothly; edit the sentence that
currently reads "the execution plan for creating the file ``plots/quals.svg`,
will be shown." to remove the comma after ``plots/quals.svg`` and ensure spacing
and punctuation remain correct.