← all cases

format/frontmatter

Front matter: the title is text, the date is data, and the target's slug is its own.

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,9 +1,9 @@
 ---
-title: Membership fees
+title: Membership and fees
 slug: fees
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Membership fees
+# Membership and fees
 
 Membership costs 200 SEK per year.

Runs

hunks

✓ Run 1 · 1 edit · 2 turns · 4,503 in / 521 out tokens · $0.0119 · 4.9 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✓ has "updated: 2026-09-01"
  • ✓ lacks "2026-01-10"
  • ✓ has /^title: Medlemskap (och|&) avgifter$/m
  • ✓ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

@@ -1,9 +1,9 @@
 ---
-title: Medlemsavgifter
+title: Medlemskap och avgifter
 slug: avgifter
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Medlemsavgifter
+# Medlemskap och avgifter
 
 Medlemskapet kostar 200 kr per år.

The translator's notes

**Change:** English retitled the page from "Membership fees" to "Membership and fees" (both the front matter title and the H1) and bumped `updated` to 2026-09-01. The likely reason is that the page is meant to cover membership more broadly, not only the fee amounts. The body is unchanged.

**Places in the Swedish file:**
- `title: Medlemsavgifter` needs an edit so it matches the new scope: "Medlemskap och avgifter".
- `# Medlemsavgifter` needs the same edit.
- `updated: 2026-01-10` needs an edit to 2026-09-01, since the page is being revised.
- `slug: avgifter` stays as it is, because the English slug didn't change.
- The body "Medlemskapet kostar 200 kr per år." stays as it is, because it is unchanged and already correct.I updated the Swedish file to follow the English retitling. The title and the H1 now read "Medlemskap och avgifter", and `updated` is 2026-09-01. I left the slug `avgifter` and the body text as they were, since neither changed in English.

Tool calls

  1. edit_file: {"old_string":"title: Medlemsavgifter\nslug: avgifter\nupdated: 2026-01-10\n---\n\n# Medlemsavgifter","new_string":"title: Medlemskap och avgifter\nslug: avgift
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). 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:
---
title: Membership fees
slug: fees
updated: 2026-01-10
---

# Membership fees

Membership costs 200 SEK per year.


## Changes made to en since then:
@@ -1,9 +1,9 @@
 ---
-title: Membership fees
+title: Membership and fees
 slug: fees
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Membership fees
+# Membership and fees
 
 Membership costs 200 SEK per year.

## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Update the sv file.
✓ Run 2 · 1 edit · 2 turns · 4,490 in / 505 out tokens · $0.0117 · 5.0 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✓ has "updated: 2026-09-01"
  • ✓ lacks "2026-01-10"
  • ✓ has /^title: Medlemskap (och|&) avgifter$/m
  • ✓ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

@@ -1,9 +1,9 @@
 ---
-title: Medlemsavgifter
+title: Medlemskap och avgifter
 slug: avgifter
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Medlemsavgifter
+# Medlemskap och avgifter
 
 Medlemskapet kostar 200 kr per år.

The translator's notes

**Change:** English renamed the title and heading from "Membership fees" to "Membership and fees". It also bumped `updated` to 2026-09-01. The likely reason is that the page is meant to cover membership in general as well as the fees.

**Places in the Swedish file:**
- `title: Medlemsavgifter` needs an edit so it matches the new scope, e.g. "Medlemskap och avgifter".
- `updated: 2026-01-10` needs an edit to the new date.
- `# Medlemsavgifter` needs an edit to match the title.
- `slug: avgifter` stays as it is. English left its slug unchanged, and the Swedish slug is its own convention.
- The body, "Medlemskapet kostar 200 kr per år.", stays as it is. The fact is unchanged.I updated the Swedish file to match the English change. The title and the heading now read "Medlemskap och avgifter", and `updated` is now 2026-09-01. I left the slug `avgifter` and the body text as they were, because neither changed in English.

Tool calls

  1. edit_file: {"old_string":"title: Medlemsavgifter\nslug: avgifter\nupdated: 2026-01-10\n---\n\n# Medlemsavgifter","new_string":"title: Medlemskap och avgifter\nslug: avgift
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). 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:
---
title: Membership fees
slug: fees
updated: 2026-01-10
---

# Membership fees

Membership costs 200 SEK per year.


## Changes made to en since then:
@@ -1,9 +1,9 @@
 ---
-title: Membership fees
+title: Membership and fees
 slug: fees
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Membership fees
+# Membership and fees
 
 Membership costs 200 SEK per year.

## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Update the sv file.
✓ Run 3 · 1 edit · 2 turns · 4,459 in / 473 out tokens · $0.0068 · 4.6 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✓ has "updated: 2026-09-01"
  • ✓ lacks "2026-01-10"
  • ✓ has /^title: Medlemskap (och|&) avgifter$/m
  • ✓ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

@@ -1,9 +1,9 @@
 ---
-title: Medlemsavgifter
+title: Medlemskap och avgifter
 slug: avgifter
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Medlemsavgifter
+# Medlemskap och avgifter
 
 Medlemskapet kostar 200 kr per år.

The translator's notes

**Change:** English renamed the title and heading from "Membership fees" to "Membership and fees". It also bumped `updated` to 2026-09-01. The likely reason is that the page now covers membership in general as well as fees.

**Places in the Swedish file:**
- `title: Medlemsavgifter` needs an edit, so that it matches the new scope.
- `updated: 2026-01-10` needs an edit, to the new date.
- `# Medlemsavgifter` needs an edit, to match the title.
- The slug `avgifter` stays as it is, because English kept its slug too.
- The body text is unchanged in English, so it stays.

The Swedish title becomes "Medlemskap och avgifter".I changed the Swedish title and the heading to "Medlemskap och avgifter", matching English's new "Membership and fees". I also set `updated` to 2026-09-01. I left the slug and the body text as they were, because English didn't change either.

Tool calls

  1. edit_file: {"old_string":"title: Medlemsavgifter\nslug: avgifter\nupdated: 2026-01-10\n---\n\n# Medlemsavgifter","new_string":"title: Medlemskap och avgifter\nslug: avgift
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions. The languages are equal peers; none is the original. Since Swedish was last brought up to date, someone changed English (en). 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:
---
title: Membership fees
slug: fees
updated: 2026-01-10
---

# Membership fees

Membership costs 200 SEK per year.


## Changes made to en since then:
@@ -1,9 +1,9 @@
 ---
-title: Membership fees
+title: Membership and fees
 slug: fees
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
-# Membership fees
+# Membership and fees
 
 Membership costs 200 SEK per year.

## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Update the sv file.

nodiff

✗ Run 1 · 1 edit · 2 turns · 4,166 in / 435 out tokens · $0.0105 · 6.1 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✓ has "updated: 2026-09-01"
  • ✓ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

@@ -1,7 +1,7 @@
 ---
 title: Medlemsavgifter
 slug: avgifter
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
 # Medlemsavgifter

The translator's notes

Comparing the two pages:

- Title: the English "Membership and fees" and the Swedish "Medlemsavgifter" are close enough. The Swedish title is a natural rendering, so I'm leaving it.
- Slug: "fees" and "avgifter" differ, but the Swedish slug is a translated path that follows its own convention. I'm keeping it.
- Body: "Membership costs 200 SEK per year" matches "Medlemskapet kostar 200 kr per år". The content is the same.
- `updated`: English says 2026-09-01 and Swedish says 2026-01-10. This is a date field. The body doesn't differ, but the Swedish page is being brought up to date with the English one, so I'll set the date to 2026-09-01.I changed one thing in the Swedish page: the `updated` date, from 2026-01-10 to 2026-09-01, to match the English page. The title, slug and body already say the same as the English, so I left them alone. The 200 kr per year fee matches, and the Swedish slug follows its own convention.

Tool calls

  1. edit_file: {"old_string":"updated: 2026-01-10","new_string":"updated: 2026-09-01"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them 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:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


Bring the sv file up to date with the pages above.
✗ Run 2 · 1 edit · 2 turns · 4,139 in / 400 out tokens · $0.0057 · 6.5 s

Checks

  • ✓ keeps "slug: avgifter"
  • ✓ has "updated: 2026-09-01"
  • ✓ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

@@ -1,7 +1,7 @@
 ---
 title: Medlemsavgifter
 slug: avgifter
-updated: 2026-01-10
+updated: 2026-09-01
 ---
 
 # Medlemsavgifter

The translator's notes

Comparing the pages:

- Title: the English "Membership and fees" and the Swedish "Medlemsavgifter" cover the same topic in different wording. This is a difference on purpose, so I'm leaving it.
- Slug: "fees" in English and "avgifter" in Swedish. The slug is translated by convention, so it stays.
- Body: "Membership costs 200 SEK per year" matches "Medlemskapet kostar 200 kr per år". The two say the same thing.
- `updated`: English has 2026-09-01 and Swedish has 2026-01-10. The content is identical, so the only thing to change is the date, which I'm bringing in line with English.The only change was the `updated` date in the Swedish front matter, which I set from 2026-01-10 to 2026-09-01 to match English. The body text already says the same thing in both languages (200 SEK per year). The title and slug are translated differently on purpose, so I left them.

Tool calls

  1. edit_file: {"old_string":"updated: 2026-01-10","new_string":"updated: 2026-09-01"}
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them 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:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


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

Checks

  • ✓ keeps "slug: avgifter"
  • ✗ has "updated: 2026-09-01"
  • ✗ lacks "2026-01-10"
  • ✗ has /^title: Medlemskap (och|&) avgifter$/m
  • ✗ has /^# Medlemskap (och|&) avgifter$/m
  • ✓ 2× /^---$/gm

Swedish, before → after

Left unchanged.

The translator's notes

Comparing the two pages:

- Title: "Membership and fees" (en) and "Medlemsavgifter" (sv). Swedish covers fees, and the wording differs a little. I read this as a difference in wording and leave it.
- Slug: "fees" (en) and "avgifter" (sv). The slug is translated on purpose, so it stays.
- Body: "Membership costs 200 SEK per year" (en) and "Medlemskapet kostar 200 kr per år" (sv). The two say the same thing, so no edit.
- `updated`: 2026-09-01 (en) and 2026-01-10 (sv). The en date is later, but the content is the same. Changing the date without changing any content would be arbitrary, so I leave it.

The Swedish page already says what the English page says, so I made no edits.
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them 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:
---
title: Membership and fees
slug: fees
updated: 2026-09-01
---

# Membership and fees

Membership costs 200 SEK per year.


## Current sv content (this is what you'll edit):
---
title: Medlemsavgifter
slug: avgifter
updated: 2026-01-10
---

# Medlemsavgifter

Medlemskapet kostar 200 kr per år.


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