Parcial transmi

Generate concise but comprehensive study notes for the quiz titled "T1".
Respond entirely in Spanish — every word, including all headings, labels, callouts, and section markers. Do not use English terms like "Pitfall", "TL;DR", "Key Takeaway", etc. when writing in another language.
Based on the quiz topic and title, create study notes that help someone learn and retain the content.
If the user has attached additional source material (uploaded documents, PDFs, slides, lecture notes, textbook chapters, images), treat THAT as the primary authority for facts, depth, terminology, and examples. Use the quiz title to determine the overall topic and scope — but pull definitions, explanations, and detail from the attached material whenever it is available. If the attached material conflicts with your own knowledge, prefer the attached material and briefly note the discrepancy.
If NO additional material is attached, rely on your own subject-matter knowledge to generate comprehensive study notes on this topic — provide accurate definitions, context, examples, and depth that a textbook on this topic would include.

FORMATTING — use Markdown. The renderer supports:

Headings, lists, bold/italic emphasis, blockquotes (>), links
LaTeX math via KaTeX: inline $...$ and display $$...$$. Use this for any formulas, equations, variables, or scientific/mathematical notation.
Tables — use them for comparisons, attribute/value pairs, taxonomies, and side-by-side concepts. STRICT table rules: each row MUST be a single line that both starts and ends with |. NEVER put blank lines, multiple paragraphs, or HTML tags like <br> inside a cell — the renderer treats them as literal text. Keep cells concise (one short phrase or sentence). If a cell needs lists or longer prose, move that content out of the table into its own section.
Fenced code blocks with language tags (e.g. python, sql) — ONLY when the subject genuinely involves programming, query languages, or markup. Do not wrap prose, procedures, math, or step-by-step explanations in code blocks; use lists or worked examples instead.
Mermaid diagrams in ```mermaid fences for processes, timelines, relationships, cycles, decision trees, hierarchies, and comparison flowcharts. STRICT mermaid rules: use ONLY these arrow types — --> (solid), <mark class="md-hl">> (thick), -.-> (dotted); never invent any other connector. Do NOT use x or o arrowheads or partial connectors like --x, --o, -.x, </mark>x, -.-, or combinations like =.=>, =.>, -.=>. To put a label ON an edge, attach it with pipes right after the arrow, e.g. A -->|label| B or A -.->|label| B (NOT A -.x |label| B). Keep node labels short and plain — avoid parentheses, quotes, or special characters inside [...]/(...)/{...}; if you need punctuation in a label, wrap it like ["label with (stuff)"]. Prefer simple graph TD or flowchart TD diagrams; do not use experimental syntax.

KROG STUDY ELEMENTS — this renderer ALSO supports the special syntax below. The tag and directive NAMES are fixed syntax: keep them exactly as written here in English (e.g.

question text (markdown/LaTeX ok)

Cloze deletions: hide the single most important term(s) in a sentence with double braces, e.g. "The {{mitochondria}} produces {{ATP}}." Do not blank out every other word.
Flashcards for term/definition recall:

Spoilers to let the reader self-test before revealing: hidden answer
Steps for procedures: wrap an ordered list in

…

Auto-numbered boxes for formal STEM content — give each a short title after the tag name (it labels the box AND its entry in the reader's Index, see below):

…

Tabs to show one idea several ways (e.g. intuition vs formal):

…

Compare/contrast two or more concepts side by side (markdown inside each column):

Mitosis

…

Meiosis

…

Timeline for chronologies, processes, or histories — one "marker :: text" entry per line: with lines like "1905 :: Special relativity" then "1915 :: General relativity" inside.
Function plots for math/physics — one expression per line, using x as the variable (sin, cos, tan, exp, log, sqrt, abs and ^ are supported); optional domain/range/title attributes:

Molecule structures from SMILES — ONLY for chemistry topics:

REFERENCEABLE ELEMENTS: the reader gets an auto-generated, clickable Index that collects every definition/theorem/lemma/corollary/example/proof box, every table, and every figure (plot/molecule/mermaid), and jumps to it on click. Treat these as the material's reusable anchors — title the boxes clearly, and when the prose refers back to one, name it the same way (e.g. "by Theorem 2" / "see the Definition of continuity") so the reference matches its Index entry.
Highlighter for the few most exam-critical phrases: ==text== (yellow) or =={colour}:text== (e.g. =={red}:never do this==). Use very sparingly — bold is usually enough.
Inline helpers: Ctrl for keyboard keys; word to mark a glossary term; text for coloured emphasis (use sparingly).
Click-to-hear words for pronunciation — wrap text the reader can tap to hear spoken aloud: . The lang attribute is a language code (e.g. en, es, fr, de, ja) and is optional (it inherits the surrounding @lang). Ideal for language learning, vocabulary, and any term whose pronunciation matters; skip it for ordinary prose.
Section directives — each applies to everything BELOW it until changed (reset with "default"): @numbering (auto-number headings 1, 1.1, …), @accent (e.g. @accent emerald to tint a unit's headings/links), @columns 2, @font STIX. Keep these minimal and purposeful.
CLOSE EVERY TAG: each opening tag MUST have its matching closing tag on its own —

…

, /, /, , etc. Never leave a box, callout, or element open. A box ends at its </…> tag, so do not start a new heading or section while a box is still open — close it first.
Do not output empty elements, and do not wrap an entire section in a single callout or box.

PEDAGOGICAL ELEMENTS — weave these in where they help learning:

Worked examples: step-by-step solutions for quantitative or procedural topics.
Key terms: bold definitions on first mention, or a short glossary per section.
Things students typically get wrong or confuse: use a

callout to flag common errors and misconceptions.

Mnemonics: acronyms or memory aids for list-heavy or sequence-based material.
Real-world examples and applications: concrete grounding for abstract ideas.
Self-check questions: deeper "test yourself" prompts at the end of sections that go beyond the source questions — render these as inline elements so the reader can answer them in place.
One-line summary at the end of each major section.
Cross-topic connections: explicitly note how concepts relate ("this builds on…", "contrast with…", "see also…").
Use bold to naturally emphasize the most important points within the prose — no labels or markers needed.

Do not include a table of contents — one will be generated automatically.
SECTIONS (chapters) — unless the material is short (one focused topic), you MUST split it into several chapters. Separate every pair of consecutive chapters with a delimiter: a line containing ONLY six hyphens and nothing else — ------ — at the very START of the line, with no indentation, heading, or other text. This delimiter is what drives the chapter navigation, so material that covers multiple major topics but contains NO ------ line is wrong and must be fixed. Two chapters are separated exactly like this (note the ------ alone on its own line, flush left):

Cell structure

Prose of the first chapter…