← all cases

format/mdx-props

MDX: a text prop and an image path change; the target's localized href and the ids stay.

hunks ✓✓✓ · nodiff ✗✗✗ · target Swedish · languages English, Swedish

What changed

This is what the diff version was told. The nodiff baseline got the current page of each language instead.

English changed

@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Row with us" />
+<Hero id="top" image="/img/eights.jpg" title="Row with us" />
 
-<Card id="plans" title="See our plans" href="/pricing">
+<Card id="plans" title="See plans and prices" href="/pricing">
   Pick the membership that suits you.
 </Card>

Runs

hunks

✓ Run 1 · 2 edits · 2 turns · 4,775 in / 519 out tokens · $0.0124 · 5.1 s

Checks

  • ✓ has "image=\"/img/eights.jpg\""
  • ✓ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✓ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />
+<Hero id="top" image="/img/eights.jpg" title="Ro med oss" />
 
-<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
+<Card id="plans" title="Se medlemskap och priser" href="/sv/priser">
   Välj det medlemskap som passar dig.
 </Card>

The translator's notes

Changes in en:
1. The Hero image changed from /img/boats.jpg to /img/eights.jpg. The Swedish Hero has `image="/img/boats.jpg"`. The image is a path, not text, and nothing suggests Swedish uses a different image on purpose, so it needs the same edit.
2. The Card title changed from "See our plans" to "See plans and prices". The Swedish title is "Se våra medlemskap". The new English title adds prices, so Swedish should say something like "Se medlemskap och priser". The href `/sv/priser` follows the Swedish convention and stays as it is.I made two edits in the Swedish file to match the English changes.

- **Hero image:** I changed it from `/img/boats.jpg` to `/img/eights.jpg`, the same as in English.
- **Card title:** I changed "Se våra medlemskap" to "Se medlemskap och priser", so it now mentions prices like the new English title.

I left the `/sv/priser` link alone because it already follows the Swedish path convention.

Tool calls

  1. edit_file: {"old_string":"/img/boats.jpg","new_string":"/img/eights.jpg"}
  2. edit_file: {"old_string":"Se våra medlemskap","new_string":"Se medlemskap och priser"}
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. Since Swedish was last brought up to date, someone changed the English page. For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## en content at time of last sync:
<Hero id="top" image="/img/boats.jpg" title="Row with us" />

<Card id="plans" title="See our plans" href="/pricing">
  Pick the membership that suits you.
</Card>


## Changes made to en since then:
@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Row with us" />
+<Hero id="top" image="/img/eights.jpg" title="Row with us" />
 
-<Card id="plans" title="See our plans" href="/pricing">
+<Card id="plans" title="See plans and prices" href="/pricing">
   Pick the membership that suits you.
 </Card>

## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Update the sv file.
✓ Run 2 · 2 edits · 2 turns · 4,783 in / 533 out tokens · $0.0126 · 4.9 s

Checks

  • ✓ has "image=\"/img/eights.jpg\""
  • ✓ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✓ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />
+<Hero id="top" image="/img/eights.jpg" title="Ro med oss" />
 
-<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
+<Card id="plans" title="Se medlemskap och priser" href="/sv/priser">
   Välj det medlemskap som passar dig.
 </Card>

The translator's notes

Changes in en:
1. The Hero image changed from /img/boats.jpg to /img/eights.jpg. This is a markup attribute, and the image is shared, so Swedish should use the new image too. The Swedish Hero has `image="/img/boats.jpg"`, which needs an edit.
2. The Card title changed from "See our plans" to "See plans and prices". It was probably changed to mention prices. The Swedish Card title is "Se våra medlemskap", which needs an edit. A fitting new title is "Se medlemskap och priser". The href `/sv/priser` stays as it is because it follows the Swedish path convention.I made two edits in the Swedish file to match the English changes:

- **Hero image:** I changed it from `/img/boats.jpg` to `/img/eights.jpg`, since the image is shared between languages.
- **Card title:** I changed it from "Se våra medlemskap" to "Se medlemskap och priser", matching the English "See plans and prices".

I left the `/sv/priser` link as it was, because it already follows the Swedish path convention.

Tool calls

  1. edit_file: {"old_string":"/img/boats.jpg","new_string":"/img/eights.jpg"}
  2. edit_file: {"old_string":"Se våra medlemskap","new_string":"Se medlemskap och priser"}
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. Since Swedish was last brought up to date, someone changed the English page. For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## en content at time of last sync:
<Hero id="top" image="/img/boats.jpg" title="Row with us" />

<Card id="plans" title="See our plans" href="/pricing">
  Pick the membership that suits you.
</Card>


## Changes made to en since then:
@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Row with us" />
+<Hero id="top" image="/img/eights.jpg" title="Row with us" />
 
-<Card id="plans" title="See our plans" href="/pricing">
+<Card id="plans" title="See plans and prices" href="/pricing">
   Pick the membership that suits you.
 </Card>

## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Update the sv file.
✓ Run 3 · 2 edits · 2 turns · 4,790 in / 535 out tokens · $0.0079 · 5.3 s

Checks

  • ✓ has "image=\"/img/eights.jpg\""
  • ✓ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✓ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />
+<Hero id="top" image="/img/eights.jpg" title="Ro med oss" />
 
-<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
+<Card id="plans" title="Se medlemskap och priser" href="/sv/priser">
   Välj det medlemskap som passar dig.
 </Card>

The translator's notes

Changes in en:
1. The Hero image changed from /img/boats.jpg to /img/eights.jpg. This is a markup attribute, and the image is not language-specific, so Swedish should use the new image too. The Swedish Hero reads `image="/img/boats.jpg"`, so it needs an edit.
2. The Card title changed from "See our plans" to "See plans and prices". Swedish has "Se våra medlemskap", which is a localized wording. The new English title adds prices, so Swedish should mention them as well: "Se medlemskap och priser". The Swedish href `/sv/priser` follows the Swedish path convention and stays as it is.I made two edits to the Swedish file to match the English changes.

- **Hero image:** I changed it to `/img/eights.jpg`, since the image isn't language-specific.
- **Card title:** I changed "Se våra medlemskap" to "Se medlemskap och priser", so it now mentions prices like the English "See plans and prices".

I left the Card link `/sv/priser` as it was, since it follows the Swedish path convention.

Tool calls

  1. edit_file: {"old_string":"/img/boats.jpg","new_string":"/img/eights.jpg"}
  2. edit_file: {"old_string":"Se våra medlemskap","new_string":"Se medlemskap och priser"}
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. Since Swedish was last brought up to date, someone changed the English page. For each language that changed, you have the content from when Swedish was last synced and a diff showing what changed since then.

Your job is not to translate the diff. It is to understand each change (what it says, and why it was likely made: a new fact, a correction, a rewording, a removal, a reordering) and then ask: if the person who made it had been editing the Swedish version instead, what would they have changed there? Make those changes.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Keep all of that, except where a change is about it. It follows that:
- One change may need several edits in Swedish: everywhere Swedish says what changed, also where the other language never said it, so that Swedish does not contradict itself.
- A change may need no edit at all: when Swedish does not have the content it is about, or already says what the change says.
- A change to order or structure applies only where Swedish follows that order or structure.
- Something that only looks like the changed content, but is about something else, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: for each change, what it says and why it was likely made; then every place in the Swedish file that it concerns, quoted, with whether that place needs an edit and why. Places the other language never mentions count too.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## en content at time of last sync:
<Hero id="top" image="/img/boats.jpg" title="Row with us" />

<Card id="plans" title="See our plans" href="/pricing">
  Pick the membership that suits you.
</Card>


## Changes made to en since then:
@@ -1,5 +1,5 @@
-<Hero id="top" image="/img/boats.jpg" title="Row with us" />
+<Hero id="top" image="/img/eights.jpg" title="Row with us" />
 
-<Card id="plans" title="See our plans" href="/pricing">
+<Card id="plans" title="See plans and prices" href="/pricing">
   Pick the membership that suits you.
 </Card>

## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Update the sv file.

nodiff

✗ Run 1 · 0 edits · 1 turn · 1,916 in / 286 out tokens · $0.0076 · 3.0 s

Checks

  • ✗ has "image=\"/img/eights.jpg\""
  • ✗ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✗ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages, I found no difference that needs an edit in Swedish:

- **Hero:** The image is `/img/eights.jpg` in English and `/img/boats.jpg` in Swedish. This looks like a deliberate local choice, and the image path is markup, so I'm leaving it. The title "Row with us" and "Ro med oss" say the same thing.
- **Card title:** "See plans and prices" and "Se våra medlemskap" differ in wording. The Swedish version says the same thing in its own words, so it stays.
- **Card link:** `/pricing` in English and `/sv/priser` in Swedish. This follows the Swedish convention of a language prefix and a translated path, so it stays.
- **Card text:** "Pick the membership that suits you." and "Välj det medlemskap som passar dig." say the same thing.

I made no edits.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
<Hero id="top" image="/img/eights.jpg" title="Row with us" />

<Card id="plans" title="See plans and prices" href="/pricing">
  Pick the membership that suits you.
</Card>


## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Bring the sv file up to date with the pages above.
✗ Run 2 · 0 edits · 1 turn · 1,916 in / 251 out tokens · $0.0029 · 2.8 s

Checks

  • ✗ has "image=\"/img/eights.jpg\""
  • ✗ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✗ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages, I found no place where Swedish says something different from English:

- **Hero:** The image is `/img/eights.jpg` in English and `/img/boats.jpg` in Swedish. This looks like a deliberate local choice, and I can't tell it's wrong, so I'm keeping it. The title "Ro med oss" matches "Row with us".
- **Card title:** "Se våra medlemskap" against "See plans and prices". This is a natural Swedish rendering, so I'm keeping it.
- **Card link:** `/sv/priser` follows the Swedish path convention, so I'm keeping it.
- **Card text:** "Välj det medlemskap som passar dig." matches "Pick the membership that suits you."

I made no edits.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
<Hero id="top" image="/img/eights.jpg" title="Row with us" />

<Card id="plans" title="See plans and prices" href="/pricing">
  Pick the membership that suits you.
</Card>


## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Bring the sv file up to date with the pages above.
✗ Run 3 · 0 edits · 1 turn · 1,916 in / 270 out tokens · $0.0031 · 3.0 s

Checks

  • ✗ has "image=\"/img/eights.jpg\""
  • ✗ lacks "/img/boats.jpg"
  • ✓ keeps "href=\"/sv/priser\""
  • ✓ keeps "<Card id=\"plans\""
  • ✓ keeps "<Hero id=\"top\""
  • ✗ has /<Card id="plans" title="[^"]*pris[^"]*"/i
  • ✓ keeps "title=\"Ro med oss\""

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages, I found no difference that needs an edit in Swedish:

- **Hero:** The English page uses image `/img/eights.jpg` and the Swedish page uses `/img/boats.jpg`. This looks like a deliberate local choice, and image paths are markup. I'm leaving it.
- **Hero title:** "Row with us" and "Ro med oss" say the same thing.
- **Card title:** "See plans and prices" and "Se våra medlemskap" are close enough. Swedish words it its own way.
- **Card link:** `/pricing` and `/sv/priser` follow the Swedish link convention, which uses a language prefix and a translated path.
- **Card body:** "Pick the membership that suits you." and "Välj det medlemskap som passar dig." match.

I made no edits.
The full prompt
System
You are keeping the Swedish (sv) translation of a document up to date. Its source is English (en): Swedish was translated from it, and has since been corrected and localized by hand. The English page may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now.

Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things.

The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that:
- A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself.
- A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose.
- A difference in order or structure is not a reason to reorder Swedish.
- Something that only looks like a difference, but says the same thing, stays as it is.

Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style.

Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word.

Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why.

Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content:
<Hero id="top" image="/img/eights.jpg" title="Row with us" />

<Card id="plans" title="See plans and prices" href="/pricing">
  Pick the membership that suits you.
</Card>


## Current sv content (this is what you'll edit):
<Hero id="top" image="/img/boats.jpg" title="Ro med oss" />

<Card id="plans" title="Se våra medlemskap" href="/sv/priser">
  Välj det medlemskap som passar dig.
</Card>


Bring the sv file up to date with the pages above.