Rettskriving

[kristianwn]

Summary by CodeRabbit

• Documentation
  • Updated the displayed page title on the Authorization > Guides > System Vendor (Norwegian) page; other front matter remains unchanged.
  • No changes to page content, links, or navigation behavior.
  • Impact is limited to the visible title in the documentation; functionality is unaffected.
  • This update ensures consistent labeling across the documentation navigation and page header.

[coderabbitai]

Walkthrough

Updated the front matter title string in a Norwegian Bokmål documentation page. No other metadata or content changed. No logic, control flow, or code affected.

Changes

Cohort / File(s)	Summary of Changes
Docs (nb-NO) — front matter title content/authorization/guides/system-vendor/_index.nb.md	Changed front matter title from "Sluttbrukersystemleverndør" to "Sluttbrukersystemlevarndør". No other metadata or content changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A title turns a subtle leaf,
nb-NO whispers, light and brief.
No code awakes, no routes deploy—
just letters shuffled, quiet joy.
Docs align, we nod: “Godt!”
Little change, well-placed dot.
Ship it softly—takk og flott.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The pull request title “Rettskriving” is too generic to convey the specific change and does not indicate which file or term was updated. A reviewer scanning the history would not know that this PR corrects the front matter title in the system-vendor guide. It fails to summarize the primary change of fixing the spelling from “Sluttbrukersystemleverndør” to “Sluttbrukersystemlevarndør.”	Please update the title to clearly describe the main change, for example “Fix spelling of front matter title in system-vendor guide by correcting ‘Sluttbrukersystemleverndør’ to ‘Sluttbrukersystemlevarndør’.” This avoids ambiguity and helps reviewers immediately understand the scope of the update. Adding this specificity will improve traceability in the commit history.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kristianwn-patch-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b864ec1 and 0ebd726.

📒 Files selected for processing (1)

• content/authorization/guides/system-vendor/_index.nb.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

**/*.nb.md

⚙️ CodeRabbit configuration file

Check for Norwegian Bokmål (nb-NO) grammar and spelling with extra care. Pay special attention to specialized terminology and Norwegian-specific words.

Files:

• content/authorization/guides/system-vendor/_index.nb.md

content/**/*

⚙️ CodeRabbit configuration file

Check for links, markdown formatting, headings, grammar, and spelling in multiple languages (en-US, nb-NO, nn-NO).

Files:

• content/authorization/guides/system-vendor/_index.nb.md

🧠 Learnings (1)

📓 Common learnings

Learnt from: mSunberg
PR: Altinn/altinn-studio-docs#0
File: :0-0
Timestamp: 2025-04-04T08:22:36.805Z
Learning: When reviewing Norwegian content (files with .nb.md or .nn.md extensions), carefully check for spelling and grammar issues, particularly watching for changes to specialized terminology like "Digitaliseringsrundskrivet" and Norwegian-specific words.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (javascript-typescript)