Update _index.nb.md

[ramvi]

Småfeil

Summary by CodeRabbit

• Documentation
  • Improved readability with typographical and formatting corrections in the Module 2 course page.
  • Fixed duplicated words and adjusted spacing around punctuation and conjunctions.
  • Rewrapped sentences and refined bullet numbering/line breaks for clarity.
  • No changes to instructional sequence, examples, data model descriptions, or training flow.

[coderabbitai]

Walkthrough

Minor editorial corrections in a single Norwegian Bokmål documentation file: fixed a duplicated word, adjusted spacing and punctuation around terms and code spans, rewrapped sentences for readability, and tweaked bullet numbering/line breaks. No changes to functionality, models, or instructional sequence.

Changes

Cohort / File(s)	Summary of Changes
Docs (nb-NO) formatting fixes content/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md	Corrected duplicate word, adjusted spacing and punctuation, reflowed sentences, and normalized bullet/line breaks. No content or flow changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks (1 passed, 1 warning, 1 inconclusive)

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description consists of a single word “Småfeil,” which does not adhere to the repository’s PR description template requiring detailed context, summary of changes, motivation, and validation instructions. It lacks any explanation of what was edited or why those edits were necessary, preventing reviewers from assessing the impact or verifying the fixes. Without structured information, it is unclear how to test or validate the changes.	Extend the description to include a summary of the specific edits made, the motivation behind these changes, and any steps for testing or validation. Follow the repository’s PR template by adding section headings such as “Summary of Changes,” “Motivation,” and “Testing Instructions.” Providing this structured information will enable reviewers to understand and verify the updates effectively.
Title Check	❓ Inconclusive	The current title “Update _index.nb.md” merely names the file and does not convey what was changed, making it too generic to inform reviewers about the primary edits such as typo corrections and formatting adjustments. It fails to highlight the substantive nature of the update and does not aid in quickly understanding the PR’s intent. A more descriptive title would help teammates scanning PRs to immediately grasp the main changes.	Revise the title to a concise summary of the main edits, for example “Fix typographical and formatting errors in Modul2 index page.” Ensuring the title reflects the type of corrections performed will improve clarity and context for reviewers.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A tidy tap on words that roam,
A space set right, a comma home,
Bullets march in ordered line,
Sentences breathe, now crisp, now fine—
No code disturbed, just docs that shine.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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: 0

🧹 Nitpick comments (2)

content/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md (2)

38-39: Fjern komma før «og»

Kommaet før «og» er unødvendig når to infinitivskonstruksjoner deler subjektet.

- for å tydelig vise hva de representerer, og legge til egne felter.
+ for å tydelig vise hva de representerer og legge til egne felter.

---

48-48: Fjern komma før «og» i punktliste

Samme kommaregel gjelder her.

-4. Velg feltet `property2`, og endre navnet på feltet til `etternavn`.
+4. Velg feltet `property2` og endre navnet på feltet til `etternavn`.

📜 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 e4ca183 and c8ea476.

📒 Files selected for processing (1)

• content/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md (3 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/altinn-studio/getting-started/app-dev-course/modul2/_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/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md

🧠 Learnings (2)

📓 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.

📚 Learning: 2025-04-04T08:22:36.805Z

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.

Applied to files:

• content/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md

🔇 Additional comments (1)

content/altinn-studio/getting-started/app-dev-course/modul2/_index.nb.md (1)

66-66: LGTM – konsekvent terminologi og formatering

Setningen er klar, og bruken av backticks og fet skrift er konsistent med resten av dokumentet.