Fix markdown lint errors in new wiki pages

Remove trailing punctuation from headers (MD026) and add blank lines
before lists (MD032) to pass CI markdownlint checks.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: nbhansen

docs/Onboarding/accounts_and_access.md

@@ -7,6 +7,7 @@ This page describes how to get access to GIRAF services and accounts.
 All relevant passwords are stored in [KeePass](https://keepass.info/). Contact Ulrik Nyman ([ulrik@cs.aau.dk](mailto:ulrik@cs.aau.dk)) to get the `.kbdx` file.
 
 **Best practices:**
+
 - Store the file on Google Drive so all team members can access it
 - The SM group should manage the password file
 - Re-upload after any changes
@@ -16,6 +17,7 @@ All relevant passwords are stored in [KeePass](https://keepass.info/). Contact U
 The [GIRAF GitHub organization](https://github.com/aau-giraf) contains all repositories.
 
 **To get access:**
+
 1. Contact an existing owner to be added
 2. Or use the shared account (requires 2FA code from Ulrik):
    - Username: `giraf@lists.aau.dk`

docs/Onboarding/index.md

@@ -2,7 +2,7 @@
 
 Welcome to the GIRAF project! This section will help you get set up in your first week.
 
-## What is GIRAF?
+## About GIRAF
 
 GIRAF is an umbrella term for digital tools developed for autistic children with little or no verbal communication. The applications have been developed by students at Aalborg University since 2011, in close cooperation with:
 
@@ -26,7 +26,7 @@ GIRAF is an umbrella term for digital tools developed for autistic children with
 | Know what my role involves | [Process → Roles](../Process/roles.md) |
 | See how previous teams worked | [Archive](../Archive/index.md) |
 
-## Questions?
+## Need Help
 
 - **Discord** — Day-to-day questions ([Invite Link](https://discord.gg/dNCkbsezKb))
 - **Your supervisor** — Project-level guidance

docs/Process/code_workflow.md

@@ -68,6 +68,7 @@ When your work is complete, create a pull request.
 ### Before Creating a PR
 
 Ensure your code:
+
 - Addresses only one issue (one PR per user story)
 - Is fully tested (removing any functionality should break a test)
 - Is reachable in the application
@@ -113,6 +114,7 @@ Ensure your code:
 ## 5. Merging
 
 Once approved:
+
 1. Ensure CI checks pass
 2. Merge the PR (squash or regular merge per repo conventions)
 3. Delete the feature branch

docs/Process/sprint_events.md

@@ -35,6 +35,7 @@ Time estimation uses Planning Poker with Fibonacci cards: 1, 2, 3, 5, 8, 13, 21,
 **Include in estimates:** Testing, code review, documentation, usability test design.
 
 **Process:**
+
 1. Everyone reads and discusses the issue
 2. Everyone picks a card secretly, then reveals simultaneously
 3. If estimates differ by more than two steps (e.g., 3 vs 8), discuss and re-estimate
@@ -57,9 +58,10 @@ Time estimation uses Planning Poker with Fibonacci cards: 1, 2, 3, 5, 8, 13, 21,
 
 Teams work on their assigned issues. See [Code Workflow](code_workflow.md) for the issue-to-merge process.
 
-### Need More Work?
+### Need More Work
 
 If your team finishes early:
+
 1. Find an issue in the Sprint Backlog
 2. Ask the SM group for approval (they may redirect you to higher priorities)