← all cases

format/frontmatter

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

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

What changed

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 · 2 edits · 2 turns · 4,657 in / 580 out tokens · $0.0129 · 5.4 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:** The English title and H1 changed from "Membership fees" to "Membership and fees", and the `updated` date changed to 2026-09-01. The likely reason is that the page is meant to cover membership in general as well as the fees. The body text is unchanged.

**Places in the Swedish file:**
- `title: Medlemsavgifter` needs an edit to match the broadened title, "Medlemskap och avgifter".
- `# Medlemsavgifter` needs the same edit.
- `updated: 2026-01-10` needs an edit to the new date.
- `slug: avgifter` stays as it is. The English slug did not change, and the Swedish slug follows its own convention.
- The body, "Medlemskapet kostar 200 kr per år.", stays as it is. It already says the same thing as the English body.I changed the Swedish title and heading to "Medlemskap och avgifter" to match the new English "Membership and fees". I also updated the `updated` date to 2026-09-01. The slug and body text stay as they were. The slug is unchanged in English, and the body already matches.

Tool calls

  1. edit_file: {"old_string":"title: Medlemsavgifter\nslug: avgifter\nupdated: 2026-01-10","new_string":"title: Medlemskap och avgifter\nslug: avgifter\nupdated: 2026-09-01"}
  2. edit_file: {"old_string":"# Medlemsavgifter","new_string":"# Medlemskap och avgifter"}
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,450 in / 465 out tokens · $0.0112 · 4.4 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

The English change renamed the title and heading from "Membership fees" to "Membership and fees". It also bumped the `updated` date to 2026-09-01. The body text is unchanged.

Places in the Swedish file that this touches:
- `title: Medlemsavgifter` needs an edit so it matches the new English title: "Medlemskap och avgifter".
- `# Medlemsavgifter` needs the same edit.
- `updated: 2026-01-10` needs an edit to 2026-09-01.
- The body, "Medlemskapet kostar 200 kr per år.", is unchanged and stays.
- The slug `avgifter` is a Swedish convention of its own and stays.I updated the Swedish file to match the English change. The title and heading now read "Medlemskap och avgifter", and the `updated` date 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 3 · 1 edit · 2 turns · 4,473 in / 488 out tokens · $0.0070 · 4.7 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" and bumped `updated` to 2026-09-01. The likely reason is a broader scope for the page, with the date marking the edit.

**Places in Swedish:**
- `title: Medlemsavgifter` needs an edit to "Medlemskap och avgifter", to match the new scope.
- `# Medlemsavgifter` needs the same edit.
- `updated: 2026-01-10` needs an edit to 2026-09-01.
- `slug: avgifter` stays, since the English slug is unchanged and Swedish has its own slug.
- The body sentence "Medlemskapet kostar 200 kr per år." stays, since the body is unchanged.I updated the Swedish file to match the English change. The title and heading now read "Medlemskap och avgifter", and `updated` is 2026-09-01. I left the slug `avgifter` and the body sentence 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.