20 invites de diagrammes d'anatomie humaine pour le cœur, le cerveau et les neurones

<think>
The user wants me to translate an English blog fragment into French. Let me carefully translate this while respecting all the rules:

1. Keep all markdown syntax intact
2. Keep all URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use natural, fluent French
6. Output only the translated markdown

Let me translate paragraph by paragraph:

""

This is an image alt text - I should translate it:
""

"An anatomically correct heart cutaway — four chambers, valves, great vessels, flow arrows — from one prompt. This page collects 20 anatomy prompts at that standard: heart, brain, neurons, barriers, and organ systems. Each prompt names its panels, quotes its labels, and carries a verify note, because anatomy is exactly where AI illustration earns trust or loses it."

Translation:
"Une coupe anatomiquement correcte du cœur — quatre chambres, valves, gros vaisseaux, flèches de flux — à partir d'une seule requête. Cette page recueille 20 requêtes anatomiques à ce standard : cœur, cerveau, neurones, barrières et systèmes d'organes. Chaque requête nomme ses panneaux, cite ses étiquettes et porte une note de vérification, car l'anatomie est exactement l'endroit où l'illustration par IA gagne la confiance ou la perd."

"Open the anatomy presets · Medical illustration guide · Biology prompt pack"

I'll translate the links to their French equivalents, maintaining the URL structure while adapting the text. The links remain functional, ensuring a seamless user experience while presenting the content in the target language.

Specifically, I'll translate the link texts to their French counterparts: "Ouvrir les préréglages anatomiques", "Guide d'illustration médicale" and "Pack de requêtes de biologie".

For the warning text, I'll ensure the nuanced medical terminology is accurately translated, preserving the critical warning about AI-generated anatomical representations while using precise anatomical language.

The mirror and subtle anatomical errors represent a significant risk in AI medical illustration. These inaccuracies can be deceptively convincing, potentially misleading medical professionals and students. Each anatomical depiction requires meticulous verification to prevent propagation of incorrect anatomical information.
</think>

Une coupe anatomiquement correcte du cœur — quatre chambres, valves, gros vaisseaux, flèches de flux — à partir d'une seule requête. Cette page recueille 20 requêtes anatomiques à ce standard : cœur, cerveau, neurones, barrières et systèmes d'organes. Chaque requête nomme ses panneaux, cite ses étiquettes et porte une note de vérification, car l'anatomie est exactement l'endroit où l'illustration par IA gagne la confiance ou la perd.

Ouvrir les préréglages anatomiques · Guide d'illustration médicale · Pack de requêtes de biologie

Un avertissement avant les requêtes : l'anatomie en miroir et subtilement incorrecte est l'échec le plus courant de l'IA dans cette discipline, et elle paraît plausible — c'est cette combinaison qui fait que chaque entrée ci-dessous possède une vérification spécifique. Pour toute application clinique, enseignement critique ou publication, traitez la sortie comme un brouillon et vérifiez par rapport à un atlas. Notre guide de vérification couvre le protocole complet.

<think>
The user wants me to translate a markdown heading into French. This is a simple heading fragment that needs to be translated while keeping the markdown syntax intact.

"## Heart and circulation" needs to become a French translation.

"Heart and circulation" in French would be:

• "Cœur et circulation" or "Cœur et appareil circulatoire"

The most natural and commonly used French expression would be "Cœur et circulation" or "Le cœur et la circulation".

Since it's a heading (H2), I should keep the "##" markdown syntax and translate the text itself.

Let me translate: "## Heart and circulation" → "## Cœur et circulation"

I'll use "Cœur" with a capital C as it's a proper noun in this context (title case equivalent in French for titles/headings).
</think>

Cœur et circulation

<think>
The user wants me to translate this blog article fragment about human heart blood flow into natural, fluent French. Let me analyze what needs to be translated:

1. The heading "1. Human heart blood flow" - translate to French
2. The image description/prompt in the code block - translate to French
3. The list items (labels and title) - translate to French
4. The verification note at the bottom - translate to French

Let me be careful to:

• Keep markdown syntax intact
• Keep all URLs, image paths, and HTML tags exactly as-is
• Keep code blocks and inline code untranslated
• Keep "GLMImage" untranslated
• Use native, fluent French expression

Let me translate each part:

1. Human heart blood flow → ### 1. Flux sanguin du cœur humain

The code block - this appears to be an image generation prompt. I should translate the natural language parts but keep any technical terms or code-like syntax as-is.

Une coupe frontale anatomiquement correcte du cœur humain montrant le flux sanguin, avec les chemins oxygéné et dés oxygéné, un gros plan sur une valve et des flèches directionnelles.
Étiquettes : « ATRIUM DROIT », « VENTRICULE DROIT », « ATRIUM GAUCHE », « VENTRICULE GAUCHE », « AORTE », « ARTÈRE PULMONAIRE ». Titre : « LE CŒUR HUMAIN ».

Wait, I need to reconsider. The code block contains an image generation prompt. The user said "Keep code blocks and inline code untranslated" - but this isn't really code, it's a description/prompt for image generation. Let me re-read the instructions.

The instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This seems to apply to actual programming code, not to image generation prompts that happen to be in code blocks.

Since this is natural language in a code block, I should translate it as the instructions emphasize using native, fluent French expression throughout. The user also wants me to translate completely without summarizing or shortening. Let me proceed with translating the natural language content while keeping any technical parameters or syntax intact if there were any.

Looking at the content, it's entirely natural language description meant for human reading. I'll translate it fully:

Une coupe frontale anatomiquement correcte du cœur humain montrant le flux sanguin, avec
les chemins oxygéné et dés oxygéné, un gros plan sur une valve et des flèches directionnelles.
Étiquettes « ATRIUM DROIT », « VENTRICULE DROIT », « ATRIUM GAUCHE », « VENTRICULE GAUCHE », « AORTE »,
« ARTÈRE PULMONAIRE ». Titre : « LE CŒUR HUMAIN ».

Vérification : côté droit = dés oxygéné (bleu), gauche = oxygéné (rouge) ; l'artère pulmonaire transporte du sang bleu et la veine pulmonaire du sang rouge — ce fait unique que chaque cœur généré commet d'abord en erreur.

Let me verify my French translations are accurate. "ATRIUM DROIT" and "VENTRICULE DROIT" are correct anatomical terms for the right atrium and right ventricle respectively. "ARTÈRE PULMONAIRE" correctly translates to pulmonary artery. The verification note about the right side being deoxygenated (blue) and left side being oxygenated (red) is properly rendered, along with the explanation about the pulmonary artery carrying blue blood and the pulmonary vein carrying red blood.
</think>

1. Flux sanguin du cœur humain

Une coupe frontale anatomiquement correcte du cœur humain montrant le flux sanguin, avec
les chemins oxygéné et dés oxygéné, un gros plan sur une valve et des flèches directionnelles.
Étiquettes « ATRIUM DROIT », « VENTRICULE DROIT », « ATRIUM GAUCHE », « VENTRICULE GAUCHE », « AORTE »,
« ARTÈRE PULMONAIRE ». Titre : « LE CŒUR HUMAIN ».

Vérification : côté droit = dés oxygéné (bleu), gauche = oxygéné (rouge) ; l'artère pulmonaire transporte du sang bleu et la veine pulmonaire du sang rouge — ce fait unique que chaque cœur généré commet d'abord en erreur.

<think>
The user wants me to translate a blog article fragment about a cardiovascular atlas plate into natural, fluent French. Let me analyze the content:

1. It's a description of a medical atlas plate showing the human heart and circulation
2. It includes specific anatomical labels and details
3. There's a verification note about anatomical correctness

I need to:

1. Translate into natural French
2. Keep all markdown syntax (heading, code fence, etc.)
3. Keep URLs, image paths, HTML tags as-is
4. Keep code blocks as-is (only translate comments if trivially safe)
5. Keep "GLMImage" brand untranslated
6. Output ONLY the translated markdown

Let me translate this carefully:

The fragment describes:

• A comprehensive medical-atlas plate
• A large anatomically accurate frontal cutaway
• Four chambers and valves
• Coronary arteries on the surface
• Great vessels
• Magnified valve inset
• Coronary cross-section inset
• Schematic of pulmonary and systemic loops
• Labels: RIGHT ATRIUM, LEFT VENTRICLE, AORTA, MITRAL VALVE, CORONARY ARTERY
• Title: "THE HEART AND CIRCULATION"

French anatomical terms I need to use:

• Right atrium = Oreillette droite
• Left ventricle = Ventricule gauche
• Aorta = Aorte
• Mitral valve = Valve mitrale
• Coronary artery = Artère coronaire
• Tricuspid valve = Valve tricuspide

Let me translate the code block content as well - this appears to be a detailed description of the image that should be displayed. The text inside the code block describes what the image should show.

Actually, looking at the code block more carefully - it contains a description of an image that would be shown. This is essentially the alt text or description of what the image should contain. I should translate this into French as well.

Let me write the translation:
</think>

2. Planche de l'atlas cardiovasculaire

Une planche complète d'atlas médical du cœur humain et de la circulation : une
coupe frontale anatomiquement précise et de grande taille avec les quatre cavités
et valves, les artères coronaires tracées en surface, les gros vaisseaux entrants
et sortants, un insert agrandi d'une valve montrant le détail des cuspides, un
insert de coupe transversale d'une coronaire, et un schéma compact des circuits
pulmonaire et systémique avec des flèches de flux rouges et bleues. Étiquettes :
« OREILLETTE DROITE », « VENTRICULE GAUCHE », « AORTE », « VALVE MITRALE »,
« ARTÈRE CORONAIRE ». Titre : « LE CŒUR ET LA CIRCULATION ».

Vérification : valve mitrale à gauche, tricuspide à droite ; artères coronaires en surface du cœur, et non à l'intérieur des cavités.

<think>
The user wants me to translate a blog article fragment into French. This appears to be a section about a QA (Quality Assurance) comparison of heart anatomy generated by AI.

Let me translate this carefully:

1. "### 3. Heart anatomy QA comparison" → "### 3. Comparaison QA d'anatomie cardiaque"

   • "QA comparison" = "comparaison QA" (QA stays as-is, it's a technical acronym)
   • "heart anatomy" = "anatomie cardiaque"

2. The code block content needs to stay as-is since it's a placeholder/example showing what would be displayed. Actually, looking at it again, this seems to be describing an image/visual that would appear. The text inside the code fence appears to be a description of what the visual contains. I should keep this untranslated since it's essentially describing image content or a visual asset that doesn't need translation.

3. "Use this one in teaching about AI anatomy — it shows what the failure actually looks like." → "Utilisez celui-ci pour enseigner à propos de l'anatomie par IA — il montre à quoi ressemble réellement l'échec."

Wait, the instruction says "Keep code blocks and inline code untranslated". So I should keep the entire code block content as-is.

Let me reconsider the full translation:

### 3. Comparaison QA d'anatomie cardiaque

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

Utilisez celui-ci pour enseigner *à propos* de l'anatomie par IA — il montre à quoi ressemble réellement l'échec.

Actually, looking at the French translation, I need to make it more natural. Let me revise:

"Use this one in teaching about AI anatomy" could be "Utilisez celui-ci dans le cadre de l'enseignement de l'anatomie par IA" or "Utilisez celui-ci pour expliquer l'anatomie générée par IA"

The key distinction is "teaching about AI anatomy" versus "using AI in teaching anatomy". The original likely means "teaching about AI-generated anatomy", which would be "l'anatomie générée par IA" or "l'anatomie par IA". The phrase "about AI anatomy" is slightly ambiguous, but the context suggests we're teaching about how AI generates anatomy and its failures. I'll go with "l'anatomie générée par IA" to capture this teaching purpose more accurately.

"— il montre à quoi ressemble réellement l'échec." translates to "it shows what failure actually looks like." The final version combines these elements: "Utilisez celui-ci pour enseigner l'anatomie générée par IA — il montre à quoi ressemble réellement l'échec."
</think>

3. Comparaison QA d'anatomie cardiaque

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

Utilisez celui-ci pour enseigner l'anatomie générée par IA — il montre à quoi ressemble réellement l'échec.

<think>
The user wants me to translate the heading "## Brain and neurons" into French. This is a straightforward heading that needs to be translated while keeping the markdown syntax intact.

"## Brain and neurons" in French would be "## Cerveau et neurones"

I need to output ONLY the translated markdown, no preamble or commentary.
</think>

Cerveau et neurones

<think>
The user wants me to translate this blog article fragment into French. Let me analyze what I need to do:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use natural, fluent French
6. Output only the translated markdown

Let me translate each part:

Title "### 4. Four specialized cells"
"### 4. Quatre cellules spécialisées"

Code block content:

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

This appears to be an image caption/alt text or a description of what an image shows. I should translate the descriptive text but keep "CELL SPECIALISTS" as a label/title - or translate it to French "CELLULES SPÉCIALISTES" since it's the title of an image.

Actually, looking at the format, this seems to be the alt text/description of an image. The content inside the code block describes an image. I should translate this into French naturally.

Let me translate:

• "A comparative row of four specialized cells at matching scale" → "Une rangée comparative de quatre cellules spécialisées à la même échelle"

• "a neuron with dendrites and long axon" → "un neurone avec des dendrites et un axone long"

• "a red blood cell as a biconcave disc" → "un globule rouge sous forme de disque biconcave"

• "a sperm cell" → "un spermatozoïde"

• "a macrophage spreading pseudopods" → "un macrophage étendant des pseudopodes"

• "each with two functional labels" → "chacune avec deux étiquettes fonctionnelles"

• "Title: 'CELL SPECIALISTS'" → "Titre : « CELLULES SPÉCIALISTES »"

I'll continue translating the next part. The alt text provides specific verification details for the neuron image. I'll translate the alt text while maintaining its technical accuracy:

• "Four specialized cells including a neuron with long axon" → "Quatre cellules spécialisées incluant un neurone avec un long axone"
• The verification instruction remains consistent: ensure the neuron has multiple short dendrites and a single long axon, regenerating if the image shows two axons.

The URL and image path remain unchanged as per the original instructions.
</think>

4. Quatre cellules spécialisées

Une rangée comparative de quatre cellules spécialisées à la même échelle : un
neurone avec des dendrites et un axone long, un globule rouge sous forme de
disque biconcave, un spermatozoïde et un macrophage étendant des pseudopodes,
chacune avec deux étiquettes fonctionnelles.
Titre : « CELLULES SPÉCIALISTES ».

Vérification : neurone — dendrites nombreuses et courtes, axone unique et long ; si le dessin lui attribue deux axones, régénérer.

<think>
I need to translate this blog fragment about the hippocampus memory circuit into French. Let me go through each part:

1. The heading "### 5. Hippocampus memory circuit" should become "### 5. Circuit de la mémoire hippophagique" or better "### 5. Circuit mnésique de l'hippocampe"

2. The code block contains a description of a figure. This is technical description text that should be translated. However, looking at it again, it seems like this might be actual code or a diagram description that needs to be kept as-is. Actually, looking at the format, it appears to be a figure caption/description. I should translate the descriptive text while keeping the structure.

3. The alt text for the image: "Hippocampal memory circuit from entorhinal cortex to CA1 labeled" should become "Circuit de mémoire hippique du cortex entorhinal au CA1 étiqueté" - actually "hippocampique" is the correct adjective for hippocampus in French.

4. The URL and image path must stay exactly as-is.

5. The "Verify" text should be translated.

Let me reconsider the code block. Looking at the content:

• It's a multiline string with a description of what a figure shows
• It mentions anatomical structures and their connections
• This appears to be documentation or caption text, not executable code

I should translate the natural language description within the code block while keeping the overall structure. However, the user said "Keep code blocks and inline code untranslated". This is a gray area - is this code or documentation? Given that it's a descriptive string with labels and structure descriptions, I'll treat it as documentation that should be translated for a blog post context, but I'll be careful to keep all the structural elements (arrows, labels) intact.

Actually, re-reading the instructions: "Keep code blocks and inline code untranslated". This is definitely in a code fence (triple backticks), so I should NOT translate it according to the rules.

I'll maintain a cautious approach and preserve the code block's original content entirely. The code block represents a figure description that could be part of executable documentation, so I'll keep it unchanged to avoid potential misinterpretation.

The key consideration is preserving the technical precision of the original description while ensuring I don't inadvertently alter any critical structural elements or anatomical references.

I'll translate the markdown text and alt text, but leave the code block untouched, strictly adhering to the specified guidelines for code and markdown content.

The markdown text contains anatomical terminology and a circuit description that needs careful translation. I'll focus on converting the descriptive content while preserving technical anatomical references like "entorhinal", "dentate gyrus", and specific hippocampal regions.

The circuit description involves precise neuroanatomical terminology describing signal flow through the hippocampus, which requires maintaining scientific accuracy during translation.

I'll preserve key anatomical terms like "subiculum" and "CA3-CA1" in their original form, focusing on translating the surrounding descriptive language. The technical code block remains untranslated, while supporting text gets converted to French.

The markdown headers and image descriptions will be carefully adapted to maintain the scientific context and instructional clarity of the original English content.
</think>

5. Circuit de la mémoire hippique

A hippocampal circuit figure: entorhinal cortex input entering the dentate gyrus,
the CA3-CA1 trisynaptic loop, and output via the subiculum, with a
long-term-potentiation inset showing synaptic strengthening spikes.
Label "ENTORHINAL", "DENTATE GYRUS", "CA3", "CA1", "LTP". Title: "MEMORY CIRCUIT".

Vérification : l'ordre de la boucle est cortex entorhinal → gyrus denté → CA3 → CA1 → subiculum ; les flèches vont toutes dans le même sens autour de la boucle.

<think>
I need to translate this blog fragment about Alzheimer pathology into natural, fluent French. Let me go through it carefully:

1. Keep all markdown syntax intact (headings, lists, etc.)
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep the brand word "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown

Let me translate:

"### 6. Alzheimer pathology" → "### 6. Pathologie d'Alzheimer"

The code block should remain as-is in English (it's a description/diagram prompt):

A coronal brain section highlighting the hippocampus in Alzheimer disease, with
amyloid plaques as small extracellular deposits and neurofibrillary tangles inside
neurons, plus one magnified inset of a plaque and a tangle. Label "HIPPOCAMPUS",
"PLAQUE", "TANGLE", "NEURON". Title: "ALZHEIMER PATHOLOGY".

The alt text: "Coronal brain section with Alzheimer plaques and tangles labeled" → "Coupe coronale du cerveau avec plaques et enchevêtrements d'Alzheimer étiquetés"

The verification text: "Verify: plaques extracellular, tangles intracellular — the two get swapped surprisingly often." → Need to translate this naturally.

"Verify:" → "Vérification :"
"plaques extracellular, tangles intracellular" → "plaques extracellulaires, enchevêtrements intracellulaires"
"the two get swapped surprisingly often" → "les deux sont souvent inversés par erreur" or "il est surprenamment fréquent qu'on inverse les deux"

Let me write the full translation:

6. Pathologie d'Alzheimer

A coronal brain section highlighting the hippocampus in Alzheimer disease, with
amyloid plaques as small extracellular deposits and neurofibrillary tangles inside
neurons, plus one magnified inset of a plaque and a tangle. 

Label "HIPPOCAMPUS", "PLAQUE", "TANGLE", "NEURON". Title: "ALZHEIMER PATHOLOGY".

Vérification : plaques extracellulaires, enchevêtrements intracellulaires — il est surprenamment fréquent qu'on inverse les deux.

I verified the translation maintains the technical accuracy of the original, preserving the anatomical distinction between extracellular plaques and intracellular tangles while ensuring natural French phrasing.
</think>

6. Pathologie d'Alzheimer

A coronal brain section highlighting the hippocampus in Alzheimer disease, with
amyloid plaques as small extracellular deposits and neurofibrillary tangles inside
neurons, plus one magnified inset of a plaque and a tangle. Label "HIPPOCAMPUS",
"PLAQUE", "TANGLE", "NEURON". Title: "ALZHEIMER PATHOLOGY".

Vérification : plaques extracellulaires, enchevêtrements intracellulaires — il est étonnamment fréquent qu'on inverse les deux.

<think>
The user wants me to translate this article fragment about synapse pruning into French. Let me analyze what needs to be translated:

1. This is a markdown section with a heading
2. There's a code block that contains:
   • A description of a developmental neuroscience figure
   • Labels for the figure
   • A title

According to the rules:

1. Keep ALL markdown syntax intact
2. Keep every URL, image path, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)
4. Keep the brand word "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown

So I need to:

• Translate the heading "### 7. Synapse pruning" into French
• The code block content is a figure prompt/description, not actual code. The instructions say "Keep code blocks and inline code untranslated" - but this is more of a figure description/label set than executable code. However, to be safe and follow the literal instruction, I should treat this as content that might need translation since it's not technical code.

Actually, re-reading the instructions: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This suggests that code blocks should remain untranslated. But this code block doesn't contain actual code - it's a figure description with labels and a title.

Given the context that this is part of an article being localized, and the code block contains figure labels and descriptions that are meant to be part of the article content (not executable code), I think the intent is to translate this content as well. The "code fence" (```) is just a markdown formatting technique to make the description stand out, not because it's actual code.

Let me translate this into natural, fluent French:

"### 7. Élagage synaptique"

For the code block content, I'll translate the description and labels:

• "A developmental neuroscience figure" → "Figure de neurosciences du développement"

• "an over-wired neonatal dendrite with many weak synapses" → "une dendrite néonatale surconnectée avec de nombreuses synapses faibles"

• "microglia tentacles tasting and removing the weak ones" → "les tentacules de la microglie goûtant et éliminant les synapses faibles"

• "and the refined adolescent circuit with fewer strong connections" → "et le circuit neuronal adolescent affiné avec moins de connexions fortes"

• "plus a density curve inset" → "plus un encart de courbe de densité"

• Label translations are straightforward anatomical terms: "DENDRITE", "MICROGLIA", "SYNAPSE FAIBLE", "SYNAPSE FORTE"

• Title "PRUNING THE BRAIN" becomes "L'ÉLAGAGE DU CERVEAU"

I'm systematically converting each English description and label into precise French scientific terminology, maintaining the original structure and meaning.
</think>

7. Élagage synaptique

Une figure de neurosciences du développement : une dendrite néonatale surconnectée
avec de nombreuses synapses faibles, les tentacules de la microglie goûtant et
éliminant les faibles, et le circuit affiné de l'adolescent avec moins de connexions
fortes, plus un graphique de densité en encart.
Étiquettes : « DENDRITE », « MICROGLIE », « SYNAPSE FAIBLE », « SYNAPSE FORTE ».
Titre : « L'ÉLAGAGE DU CERVEAU ».

<think>
The user wants me to translate the heading "## Barriers and systems" into French while keeping the markdown syntax intact.

"## Barriers and systems" in French would naturally be "## Barrières et systèmes"

This is a simple heading translation. I need to:

1. Keep the markdown syntax (##) intact
2. Translate "Barriers and systems" to French
3. Output only the translated markdown

Let me provide the translation.
</think>

Barrières et systèmes

<think>
The user wants me to translate a blog article fragment about the blood-brain barrier into French. Let me follow the rules carefully:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated (translate comments only if trivially safe)
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output ONLY the translated markdown

Let me translate this:

8. Blood-brain barrier

The heading stays as it is since it's a numbered section heading.

For the code block - this appears to be an image description/prompt. Code blocks should remain untranslated according to rule 3. Let me keep it exactly as-is.

For the image markdown - I keep the URL exactly as-is.

For the verification text at the end - this is in English. The user says to translate the article completely, but this appears to be a verification note. Looking at it more carefully, it seems like editorial notes for the image creator. I should probably translate it since it's part of the article content, but let me reconsider - the code block stays untranslated, but this text is outside the code block, so it should be translated.

Actually, looking more carefully, the code block contains image generation prompts - this is technical content that should stay in English. But the verification note at the end ("Verify:") is more of an editorial instruction, so I'll translate it to French.

Let me translate:

8. Barrière hémato-encéphalique

Code block stays exactly as-is (image generation prompt)

Image markdown stays exactly as-is (the URL and alt text)

"Verify:" becomes "Vérification :"

"tight junctions between endothelial cells (that's what makes it a barrier)" = "jonctions serrées entre les cellules endothéliales (c'est ce qui en fait une barrière)"

"astrocyte end-feet on the brain side, outside the membrane" = "prolongements astrocytaires du côté cerveau, à l'extérieur de la membrane"

I'll complete the translation by incorporating the final technical instructions for the image generation. The goal is to create a precise anatomical representation of the blood-brain barrier with specific visual elements.

The cross-section will highlight critical structural components: endothelial cells with tight junctions forming a selective barrier, surrounded by a basement membrane, with astrocyte projections covering the exterior and pericytes interspersed. Small molecular substances can pass through, while larger proteins are blocked. Key labels will include ENDOTHELIUM, TIGHT JUNCTION, BASEMENT MEMBRANE, ASTROCYTE, and PERICYTE, with the overall concept titled "THE GATEKEEPER" to emphasize the barrier's protective function. I'll carefully translate the anatomical description while preserving the technical precision of the original image generation prompt. The French translation maintains the scientific accuracy of the blood-brain barrier cross-section, ensuring the anatomical details are correctly represented in the target language. I'll systematically review each anatomical component to confirm the precise translation matches the original English description.

The endothelial cells, basement membrane, astrocyte end-feet, and pericyte relationships are meticulously preserved in the translation, capturing the intricate structural interactions of the blood-brain barrier's protective mechanisms. The label verification process confirms the key anatomical features are accurately translated.

For the French adaptation, I'm maintaining the original English anatomical terminology as is standard in scientific French medical language. The section title "Barrière hémato-encéphalique" appropriately captures the neurovascular interface concept. The image description code block remains linguistically consistent with original terminology, preserving technical precision while acknowledging the multilingual nature of scientific documentation.

The markdown translation maintains the structural integrity of the original English content, ensuring linguistic clarity without unnecessary linguistic transformation.
</think>

8. Barrière hémato-encéphalique

A cross-section of the blood-brain barrier: capillary endothelial cells joined by
tight junctions, the basement membrane, astrocyte end-feet wrapping the outside,
and a pericyte, with small molecules crossing while large proteins cannot.
Label "ENDOTHELIUM", "TIGHT JUNCTION", "BASEMENT MEMBRANE", "ASTROCYTE",
"PERICYTE". Title: "THE GATEKEEPER".

Vérification : jonctions serrées entre les cellules endothéliales (c'est ce qui en fait une barrière) ; prolongements astrocytaires du côté cerveau, à l'extérieur de la membrane.

<think>
The user wants me to translate a blog article fragment into French. Let me analyze what's provided:

1. It's a section heading: "### 9. Plaque burden in brain tissue"
2. It's a code block containing an image description (alt text or figure caption)

According to the rules:

1. Keep all markdown syntax intact - so I need to keep the "###" heading markers and the code fences
2. Keep every URL, image path, and HTML tag exactly as-is - there are none here
3. Keep code blocks and inline code untranslated - the content inside the code block is a description/caption, so I need to translate it
4. Keep "GLMImage" untranslated - not present here
5. Use native, fluent French expression

Let me translate:

Heading: "### 9. Plaque burden in brain tissue"
This should become: "### 9. Charge en plaques dans le tissu cérébral"

• "Plaque burden" could be translated as "charge en plaques" or "densité de plaques"
• "brain tissue" = "tissu cérébral"

Code block content:
"Cortical cross-section showing extracellular amyloid deposits, dystrophic neurites around them, and a magnified inset detailing one deposit with its dense core and diffuse halo. Label 'CORTEX', 'DEPOSIT', 'DARK CORE', 'HALO'."

French translation:
"Une coupe transversale du cortex cérébral montrant des dépôts amyloïdes extracellulaires, des neurites dystrophiques autour de ceux-ci, et un agrandissement détaillant un dépôt avec son noyau dense et son halo diffus. Étiquettes 'CORTEX', 'DÉPÔT', 'NOYAU SOMBRE', 'HALO'."

Wait, I need to be careful. The code block content appears to be an image description.

I'll proceed with translating the code block content while maintaining the original structure and intent. The labels should remain in their original form, as they seem to be specific technical or illustrative terms. I'll focus on translating the descriptive text surrounding these labels to ensure clarity and accuracy in the French translation.
</think>

9. Charge en plaques dans le tissu cérébral

Une coupe transversale du tissu du cortex cérébral montrant des dépôts amyloïdes
extracellulaires, des neurites dystrophiques autour de ceux-ci, et un insert agrandi
détaillant un dépôt avec son noyau dense et son halo diffus. Étiquettes « CORTEX »,
« DÉPÔT », « NOYAU SOMBRE », « HALO ».

<think>
The user wants me to translate this blog fragment about tau therapy strategies into French. Let me analyze the content:

1. It's a heading: "### 10. Tau therapy strategies"
2. There's a figure with code fence containing figure description
3. There's a verification note at the end

I need to:

• Translate the heading "10. Tau therapy strategies" → "10. Stratégies de thérapie tau"
• Keep the code block exactly as-is (it's a figure description, not actual code to execute)
• Translate "Verify:" note into French
• Keep all markdown syntax intact
• Keep brand name "GLMImage" if it appears (doesn't seem to be in this fragment)
• Use natural, fluent French

Let me translate:

"10. Stratégies de thérapie tau"

The figure code block stays as-is since it's a description of a figure with labels.

"Verify:" → "Vérifier :" or "À vérifier :"

The content about antibody staying outside neuron and ASO entering it should be translated into natural French.

Let me draft the translation:

Une figure de thérapie à deux voies pour la pathologie tau : la voie supérieure montre un anticorps 
liaison du tau à l'extérieur du neurone pour accélérer l'élimination, la voie inférieure montre 
un oligonucléotide antisens entrant dans le neurone pour réduire la production de tau, les deux 
convergeant vers une charge de enchevêtrements réduite. Étiquettes "ANTICORPS", "TAU", "ASO", 
"ENCHEVÊTREMENTS RÉDUITS".
Titre : "CIBLER TAU".

Actually, looking at this more carefully - it's a description of a figure with technical labels. The labels in all caps like "ANTIBODY", "TAU", "ASO", "REDUCED TANGLES", "TARGETING TAU" appear to be figure labels/captions that should probably be translated.

I'm reconsidering whether these capitalized labels should remain in English or be translated. Since the user's instructions emphasize preserving everything exactly as-is, I need to determine if these are part of the content that should be translated or if they're part of the figure markup that should stay unchanged. The code fence itself is clear, but the figure description and its labels need careful handling.

Looking at the structure, the figure appears to be a mock-up showing antibody binding tau outside neurons versus ASO entering neurons to reduce tau production. The verification note confirms this inside/outside distinction is central to the figure's purpose. I should focus on translating the prose description while preserving the technical labels and structure. Looking at the figure description, these labels function as part of the image markup rather than prose content needing translation. I'll keep them in English to preserve the figure's structure while translating the surrounding text and figure title. For the "Verify:" note, a natural French equivalent would be "Vérification :", which fits the scientific context. The figure caption "TARGETING TAU" should remain in English since it's a label within the figure itself, not narrative text. The note about the inside/outside distinction should be translated into French while preserving the technical terms that appear in the figure. I'll keep "ANTIBODY", "ASO", and "TAU" in English since they're figure labels, and translate the surrounding explanation about the therapeutic distinction. The figure description itself will stay in English to match the label structure, but the note explaining why this distinction matters gets rendered in natural French.
</think>

10. Stratégies de thérapie ciblant la protéine Tau

A two-path therapy figure for tau pathology: the upper path shows an antibody
binding tau outside the neuron to speed clearance, the lower path shows an
antisense oligonucleotide entering the neuron to reduce tau production, both
meeting at reduced tangle load. Label "ANTIBODY", "TAU", "ASO", "REDUCED TANGLES".
Title: "TARGETING TAU".

Vérification : l'anticorps reste à l'extérieur du neurone, l'ASO y pénètre — cette distinction intérieur/extérieur est l'intérêt même de la figure.

<think>
The user wants me to translate a heading "## Immunology figures" into French. This is a simple heading for a blog article about immunology figures (likely referring to visual representations/diagrams of immunology concepts).

Let me translate this naturally into French:

"## Immunology figures" → "## Figures d'immunologie"

This is straightforward. "Immunology" = "immunologie" in French, and "figures" in this context means visual representations/diagrams/figures, which translates to "figures" in French too (it's a technical term used in scientific/medical writing).
</think>

Figures d'immunologie

<think>
I need to translate this blog fragment about CAR-T manufacturing workflow into natural, fluent French. Let me go through it carefully:

1. Keep all markdown syntax intact
2. Keep URLs, image paths exactly as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression

The content includes:

• A heading "### 11. CAR-T manufacturing workflow"
• A code block with text describing a workflow
• An image with alt text

Let me translate:

Heading: "### 11. CAR-T manufacturing workflow" → "### 11. Processus de fabrication CAR-T"

Code block content - I should keep the code structure but translate the text content:

• "A five-step hospital workflow for producing a patient's own CAR-T cells: blood draw, T-cell separation in the lab, gene transfer with a viral vector, cell expansion in a culture bag, and infusion back into the patient." → "Un processus hospitalier en cinq étapes pour produire les cellules CAR-T du patient : prise de sang, séparation des lymphocytes T en laboratoire, transfert génétique par vecteur viral, expansion cellulaire en poche de culture, et réinfusion au patient."
• Labels like "LEUKAPHERESIS", "SELECTION", etc. - these are labels, I'll keep them as-is since they're typically kept in English in French medical contexts
• Title: "CAR-T JOURNEY" → "PARCOURS CAR-T"

Image alt text: "Five-step CAR-T manufacturing workflow labeled" → "Processus de fabrication CAR-T en cinq étapes étiqueté"

Let me refine the translation for natural French expression.
</think>

11. Processus de fabrication CAR-T

Un processus hospitalier en cinq étapes pour produire les cellules CAR-T
du patient : prise de sang, séparation des lymphocytes T en laboratoire,
transfert génétique par vecteur viral, expansion cellulaire en poche de
culture, et réinfusion au patient.
Étiquettes « LEUKAPHERESIS », « SELECTION », « GENE TRANSFER », « EXPANSION », « INFUSION ».
Titre : « CAR-T JOURNEY ».

<think>
The user wants me to translate a blog article fragment about CAR-T therapy into natural, fluent French. Let me analyze the content:

1. It's a heading: "### 12. CAR-T in the body"
2. There's a code block containing an image prompt/description
3. There's an image reference at the end

I need to:

1. Keep all markdown syntax (headings, code fences, etc.)
2. Keep URLs, image paths exactly as-is
3. Keep code blocks as-is (not translate content)
4. Keep "GLMImage" untranslated
5. Use native French expression

The code block appears to be an image generation prompt - I should keep it as-is since it's code/technical content.

Let me translate just the heading and any non-code text. The code block content should remain in English as it's a technical prompt.

The heading "### 12. CAR-T in the body" should be translated to French.

Looking at the content again:

• "### 12. CAR-T in the body" → "### 12. CAR-T dans l'organisme"
• The code block content should remain as-is (image generation prompts are typically kept in English)
• The image markdown should remain as-is

Let me write the translation:

### 12. CAR-T dans l'organisme

Then the code block stays as-is, and the image markdown stays as-is.

Wait, I need to think about whether to translate the alt text in the image markdown. The alt text is "Engineered T cells attacking tumor cells, labeled" - this is user-facing content. But since it's part of the image markdown syntax and tied to the image, I should probably keep it as-is to maintain consistency with the image asset. Actually, looking at the rules again, it says "Keep every URL, image path, and HTML tag EXACTLY as-is." The alt text isn't a URL or path, so I could translate it for a more natural French experience.

The alt text could be translated to "Cellules T modifiées attaquant des cellules tumorales, étiquetées" for better French fluency, though leaving it untranslated wouldn't violate the guidelines since it's not technically a URL, path, or HTML tag. The user-facing alt text should align with the French language context of the rest of the page.

I'll translate the heading and alt text while keeping the code block and image URLs untouched. The final result maintains all markdown structure while providing a fully French experience for the reader.
</think>

12. CAR-T dans l'organisme

An end-to-end therapy figure: engineered T cells circulating in a vessel, exiting
into a tumor bed, recognizing their antigen, and destroying tumor cells by granzyme
release, with a small patient-silhouette inset locating the action.
Label "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL".
Title: "CAR-T IN THE BODY".

<think>
The user wants me to translate a blog article fragment into French. Let me analyze what's being asked:

1. This is a markdown heading: "### 13. Bispecific antibody bridge"

2. There's a code block with:

   • A description of a mechanism figure
   • Image path (URL) - should remain unchanged
   • Label text
   • Title text

3. There's an image with:

   • Alt text
   • Image URL - should remain unchanged

I need to translate:

• The heading text "Bispecific antibody bridge"
• The content inside the code block (description, labels, title)
• The alt text of the image
• But NOT the URLs, image paths, or markdown syntax

Let me translate these elements into natural French:

• "Bispecific antibody bridge" → "Pont d'anticorps bispécifique"
• The description and labels need to be translated
• Alt text needs to be translated

Let me be careful with the code block content - I should translate the comments/descriptions but keep the technical terms like "CD3", "TUMOR ANTIGEN" etc. as they're specific labels. Actually, looking at the labels, they're capitalized terms like "CD3 ARM", "TUMOR ANTIGEN ARM", etc. I think I should translate the descriptive text but keep the label text as-is since they're meant to be shown as labels on a diagram.

Wait, let me re-read the instruction: "Translate the article fragment into natural, fluent French."

Looking at the code block, it contains:

1. A description of a mechanism figure
2. Labels with their values
3. A title

I should translate:

• The description text (not the labels themselves which are meant to be diagram labels)
• The alt text
• The title "BITE BRIDGE"

Actually, looking more carefully at the format, this appears to be a prompt for generating an image, where the code block contains instructions that will be used to generate or describe an image.

For the code block, I need to translate the description explaining the mechanism, keep the label names as they are (since they're meant to be diagram labels), and translate the title. For the image, I'll translate the alt text while keeping the URL unchanged. The key distinction is that diagram labels and technical identifiers should remain in their original form, while explanatory text and descriptive content needs French translation.

Looking at the code block structure, the first line is a prose description that should be translated into French, while the label statements and title should stay as they are since they're instructions for labeling the image. The alt text needs to be translated to French as well.

For the translation, I need to render "BITE BRIDGE" naturally in French while keeping all label identifiers and code syntax intact. The prose description becomes "Une figure de mécanisme d'un engageur bispécifique de cellules T : un bras d'anticorps se liant au CD3 sur la cellule T, l'autre bras se liant à un antigène tumoral, rapprochant les deux cellules dans une synapse où la cellule T libère de la perforine." The labels "CD3 ARM", "TUMOR ANTIGEN ARM", "T CELL", "TUMOR CELL", and "PERFORIN" remain unchanged as they're diagram annotations. The title "BITE BRIDGE" should be translated contextually—since BITE is an acronym for Bi-specific T-cell Engager, it stays as an acronym in the French version. The alt text describing the image translates to "anticorps bispécifique reliant la cellule T et la cellule tumorale étiqueté".
</think>

13. Pont d'anticorps bispécifique

Une figure de mécanisme d'un engageur bispécifique de cellules T : un bras
d'anticorps se liant au CD3 sur la cellule T, l'autre bras se liant à un antigène
tumoral, rapprochant les deux cellules dans une synapse où la cellule T libère de
la perforine. Étiquettes "CD3 ARM", "TUMOR ANTIGEN ARM", "T CELL", "TUMOR CELL",
"PERFORIN". Titre : "BITE BRIDGE".

<think>
The user wants me to translate an article fragment about "Antigen escape" into French. This appears to be a section about a medical/biological topic related to CAR-T cells and leukemia treatment.

Let me analyze what needs to be translated:

1. The heading "### 14. Antigen escape" - need to translate this
2. The code block content - this contains descriptions and labels that should be translated
3. The alt text for the image should be translated
4. Keep all markdown syntax, URLs, image paths as-is
5. Keep code blocks and inline code untranslated (but comments/descriptions inside can be translated if safe)

Wait, looking at this more carefully - the "code block" isn't actually code, it's a description/figure caption. So I should translate the text content inside it.

Let me translate:

"### 14. Antigen escape" → "### 14. Échappement antigénique"

"Antigen escape" is a technical term that can be translated as "Échappement antigénique" or "Évitement antigénique" in French medical literature.

The code block content:
"A relapse-mechanism figure: after CAR-T cells eliminate target-positive leukemia cells, a few cells that lost the target antigen survive and expand, shown as a branching population tree with the escape branch highlighted.
Label "TARGET POSITIVE", "TARGET LOST", "CAR-T CELLS", "RELAPSE".
Title: "ESCAPE ROUTE"."

This should be translated to French while keeping the labels (TARGET POSITIVE, TARGET LOST, CAR-T CELLS, RELAPSE, ESCAPE ROUTE) as they are since they're labels.

Image alt text: "Antigen escape branching population tree labeled" → "Arbre populationnel ramifié d'échappement antigénique étiqueté" or similar

Let me make sure my translation is natural and fluent in French.
</think>

14. Échappement antigénique

Figure illustrant le mécanisme de rechute : après que les cellules CAR-T
éliminent les leucémies à antigène cible positif, quelques cellules ayant
perdu l'antigène cible survivent et se multiplient, représentées sous la
forme d'un arbre populationnel ramifié avec la branche d'échappement
mise en évidence.
Étiquettes « TARGET POSITIVE », « TARGET LOST », « CAR-T CELLS »,
« RELAPSE ».
Titre : « ESCAPE ROUTE ».

<think>
The user wants me to translate this table about anatomical diagram variants from English to French. Let me analyze each row:

1. Nephron - anatomical diagram of kidney filtering unit
2. Lung alveoli - respiratory system diagram
3. Digestive system - GI tract diagram
4. Skeletal muscle - muscle tissue diagram
5. Kidney position - cross-section of torso showing kidneys
6. Skin layers - skin cross-section diagram

I need to:

• Keep markdown table syntax intact
• Keep anatomical terms that are standard in both languages or translate when appropriate
• Keep "GLMImage" as is
• Keep label terms in uppercase as they appear (these are diagram labels)
• Keep all technical anatomical terms accurate in French
• Make it natural and fluent

Let me translate:

| # | Topic | One-line change |

Row 15: Nephron - "A nephron from glomerulus through tubule to collecting duct… Label 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT'"

French: "Un néphron du glomérule au tubule jusqu'au canal collecteur… Étiqueter 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT'"

Note: In French medical/anatomical context, many terms are kept in Latin or anglicized forms, especially for diagram labels. I'll keep the labels in English as they appear to be technical diagram labels that might be standardized.

Row 16: Lung alveoli - "A respiratory bronchiole ending in an alveolar sac with capillary net around each alveolus… Label 'BRONCHIOLE', 'ALVEOLUS', 'CAPILLARY', 'SURFACTANT'"

French: "Une bronchiole respiratoire se terminant dans un sac alvéolaire avec un réseau capillaire autour de chaque alvéole… Étiqueter 'BRONCHIOLE', 'ALVEOLUS', 'CAPILLARY', 'SURFACTANT'"

Continuing with the remaining anatomical diagrams, I'll translate the digestive system and skeletal muscle cross-sections. For the digestive system, I'll describe the full-length tract with organ callouts and villus inset. The skeletal muscle diagram will showcase the hierarchical structure from whole muscle to individual sarcomere.

The kidney cross-section will highlight the cortex, medulla, ureter, and renal vein. The skin layers diagram will demonstrate the anatomical progression from epidermis through dermis to hypodermis, with detailed inset of hair follicle and associated gland structures. Each diagram provides a precise anatomical visualization with clear, labeled components. Je maintiens les termes techniques en anglais pour les étiquettes, car ils correspondent probablement à des libellés normalisés dans le contexte des diagrammes anatomiques. La traduction de la description reste fluide tout en préservant la clarté technique.
</think>

Six variantes rapides

#	Sujet	Modification en une ligne
15	Néphron	« Un néphron du glomérule au tubule jusqu'au canal collecteur… Étiqueter 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT' »
16	Alvéoles pulmonaires	« Une bronchiole respiratoire se terminant dans un sac alvéolaire avec un réseau capillaire autour de chaque alvéole… Étiqueter 'BRONCHIOLE', 'ALVEOLUS', 'CAPILLARY', 'SURFACTANT' »
17	Système digestif	« Une figure du tractus digestif complet avec annotations des organes et vue rapprochée d'un villosité… Étiqueter 'STOMACH', 'SMALL INTESTINE', 'VILLUS', 'LARGE INTESTINE' »
18	Muscle squelettique	« Une coupe transversale du muscle du muscle entier au fascicule jusqu'à la fibre unique avec vue rapprochée des myofibrilles… Étiqueter 'FASCICLE', 'MUSCLE FIBER', 'MYOFIBRIL', 'SARCOMERE' »
19	Position des reins	« Une coupe transversale du tronc montrant les deux reins avec les vaisseaux et les uretères… Étiqueter 'CORTEX', 'MEDULLA', 'URETER', 'RENAL VEIN' »
20	Couches de la peau	« Une coupe transversale de la peau de l'épiderme au derme jusqu'à l'hypoderme avec follicule pileux et glande… Étiqueter 'EPIDERMIS', 'DERMIS', 'FOLLICLE', 'SEBACEOUS GLAND' »

<think>
I need to translate this checklist about scientific review into natural, fluent French. Let me go through each item carefully:

1. "Anatomy doubles the stakes on this list:" - This means anatomy is even more important/high-risk on this checklist

2. "- [ ] Are all labels spelled correctly?" - "Toutes les étiquettes sont-elles orthographiées correctement ?"

3. "- [ ] Are all requested structures present — and nothing mirrored?" - "Toutes les structures demandées sont-elles présentes — et rien n'est-il inversé ?"

4. "- [ ] Are positions, proportions and left/right orientations reasonable against an atlas?" - "Les positions, proportions et orientations gauche/droite sont-elles cohérentes par rapport à un atlas ?"

5. "- [ ] Do flow arrows match physiology (blue right heart, red left heart)?" - "Les flèches de flux correspondent-elles à la physiologie (cœur droit bleu, cœur gauche rouge) ?"

6. "- [ ] Are stages shown in the correct order?" - "Les étapes sont-elles représentées dans le bon ordre ?"

7. "- [ ] Has it been checked against a trusted source?" - "A-t-il été vérifié par rapport à une source fiable ?"

I should keep the checklist format with [ ] intact. The parenthetical "(blue right heart, red left heart)" can stay as is since it's anatomical terminology that's universal. Let me make it sound natural and fluent in French.
</think>

Liste de contrôle pour la révision scientifique

L'anatomie double les enjeux sur cette liste :

• [ ] Toutes les étiquettes sont-elles orthographiées correctement ?
• [ ] Toutes les structures demandées sont-elles présentes — et rien n'est-il inversé ?
• [ ] Les positions, proportions et orientations gauche/droite sont-elles cohérentes par rapport à un atlas ?
• [ ] Les flèches de flux correspondent-elles à la physiologie (cœur droit bleu, cœur gauche rouge) ?
• [ ] Les étapes sont-elles représentées dans le bon ordre ?
• [ ] Cela a-t-il été vérifié par rapport à une source fiable ?

<think>
The user wants me to translate this FAQ section into French. I need to:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown

Let me translate this carefully:

Why do the prompts spell labels in capital letters?

Capital letters render more reliably than mixed case in generated figures, and they read faster at plate size — the same reason road signs are uppercase. The convention also matches classic atlas plates. Mixed-case is fine for captions you typeset yourself; for model-rendered text, capitals are the safe register.

French translation:

• "Why do the prompts spell labels in capital letters?" → "Pourquoi les invites épèlent-elles les étiquettes en majuscules ?"
• "Capital letters render more reliably than mixed case" → "Les majuscules s'affichent plus sûrement que les majuscules et minuscules"
• "they read faster at plate size" → "elles se lisent plus vite à la taille d'une planche"
• "the same reason road signs are uppercase" → "pour la même raison que les panneaux de signalisation sont en majuscules"
• "The convention also matches classic atlas plates" → "Cette convention correspond également aux planches d'atlas classiques"
• "Mixed-case is fine for captions you typeset yourself" → "Les majuscules et minuscules conviennent pour les légendes que vous composez vous-même"
• "for model-rendered text, capitals are the safe register" → "pour le texte généré par modèle, les majuscules sont le registre sûr"

Can I use these diagrams in a nursing or pre-med presentation?

"Yes, with the verification pass run honestly — and for anything graded or clinical, at the Corrected level from our verification guide.

The heart and neuron prompts above hold up well; the coronal-brain subjects are where atlases earn their keep.

For graded or clinical applications, I'll recommend the corrected verification level from our guide. The cardiac and neural illustrations work reliably, while the coronal brain sections truly demonstrate the power of traditional atlases.

How do I fix a mirrored heart?

Name it: "right atrium on the viewer's left, as in a patient facing the examiner." Mirroring is error #1 and rerolling without the constraint just re-rolls the same dice.

To correct a mirrored heart, explicitly specify the anatomical orientation: the right atrium appears on the viewer's left side, like a patient facing the examiner. Mirroring represents our first critical error, and simply rerolling without precise constraints perpetuates the same fundamental mistake.

Are these accurate enough for exams?

The generated diagrams function as reliable starting points, but require verification against authoritative references. These prompts essentially provide the specific vocabulary and terminology your textbook employs - which represents the most challenging aspect. A quick five-minute review with your reference materials transforms these drafts into exam-ready illustrations.

I'll focus on the key verification strategy: cross-reference generated images with official medical atlases and textbooks to ensure anatomical precision. Use these AI-generated diagrams as a preliminary framework, then meticulously validate each visual representation against established academic sources.
</think>

FAQ

Pourquoi les invites épellent-elles les étiquettes en majuscules ?

Les majuscules s'affichent plus sûrement que les majuscules et minuscules dans les figures générées, et elles se lisent plus vite à la taille d'une planche — pour la même raison que les panneaux de signalisation sont en majuscules. Cette convention correspond également aux planches d'atlas classiques. Les majuscules et minuscules conviennent pour les légendes que vous composez vous-même ; pour le texte généré par modèle, les majuscules sont le registre sûr.

Puis-je utiliser ces diagrammes dans une présentation infirmière ou pré-médicale ?

Oui, à condition de passer honnêtement l'étape de vérification — et pour tout travail noté ou clinique, au niveau Corrigé de notre guide de vérification. Les invites concernant le cœur et le neurone ci-dessus tiennent bien la route ; pour les sujets cerveau coronal, c'est là que les atlas révèlent leur utilité.

Comment corriger un cœur inversé ?

Nommez-le : « oreillette droite sur la gauche du spectateur, comme chez un patient face à l'examinateur. » L'inversion est l'erreur n°1, et relancer sans cette contrainte ne fait que relancer les mêmes dés.

Ces illustrations sont-elles assez précises pour les examens ?

Comme brouillons, oui ; comme figures finales, après vérification de chaque étiquette par rapport à la référence de votre cours. Les invites vous donnent le vocabulaire qu'utilise votre manuel, ce qui est la partie difficile — la vérification prend cinq minutes avec le livre ouvert à côté de vous.

<think>
I need to translate this article fragment into French while following all the rules:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent French expression
6. Output only the translated markdown

The content is:

• A heading "## Next"
• Some introductory text
• A link to anatomy presets
• Instructions about running prompts and verifying
• Related links section

Let me translate this naturally into French:

"## Next" → "## Suivant" (or keep it as "## Next" since it's a heading that might be used as a label - actually, let me think about this. In French, "Next" as a heading could be translated as "Suivant" or kept as "Next" if it's a label. But the instruction says to translate into natural, fluent French, so I'll translate it.)

Actually, thinking more carefully about headings - "## Next" is likely a section heading. In French, this could be "## Suivant" or "## À suivre". Let me go with something natural.

The main paragraph: "Start from the anatomy presets, run any prompt above, and verify before use."

Translation: "Commencez à partir des préréglages anatomiques, exécutez n'importe quelle invite ci-dessus, et vérifiez avant utilisation."

Related section:

• "how to verify an AI scientific illustration" → "comment vérifier une illustration scientifique IA"
• "12 common errors and fixes" → "12 erreurs courantes et solutions"
• "what is scientific illustration" → "qu'est-ce que l'illustration scientifique"

Let me put it all together in a natural way:

Suivant

Commencez à partir des préréglages d'anatomie, exécutez n'importe laquelle des invites ci-dessus, et vérifiez avant utilisation. Articles connexes : comment vérifier une illustration scientifique par IA · 12 erreurs fréquentes et leurs corrections · qu'est-ce que l'illustration scientifique.

I'm checking the punctuation and flow to ensure the French reads naturally. The URLs need to stay exactly as they are while the rest of the text gets translated appropriately.

The related articles section works better as "Articles connexes" rather than "En lien" since it's more commonly used in French technical content. The phrasing "Commencez à partir des" captures the instruction more naturally than alternatives like "Partez de" or "Démarrez avec".

For "run any prompt above", "exécutez n'importe laquelle des invites ci-dessus" sounds more natural than "appliquez n'importe quelle invite ci-dessus". The overall structure should flow as: ## Suivant, then the main instruction, followed by the related links section.
</think>

Suivant

Commencez à partir des préréglages d'anatomie, exécutez n'importe laquelle des invites ci-dessus, et vérifiez avant utilisation. En lien : comment vérifier une illustration scientifique par IA · 12 erreurs courantes et leurs solutions · qu'est-ce que l'illustration scientifique.