fix markdownlint issues in tpa-rfc-73

**Definition**: In Gitlab we have roles with different permissions. When the user is added to the project or group they need to have a specific role assigned. The role defines which actions they can take in that Gitlab project or group.

Right now we have the following roles:

- guest

- reporter

- developer

will be part of the different epics in the ‘Arti relays’ project. The

milestones will be used for planning specific releases.

**Difference between Epics and Milestones**

#### Difference between Epics and Milestones

Milestones are better suited for planning release timelines and tracking specific features, allowing teams to focus on deadlines and delivery goals.

**What problem we are solving**: Represent and track in Gitlab the iterations we are having in different projects.

**Difference between Epics and Iterations**

#### Difference between Epics and Iterations

While Epics group related issues to track high-level goals over multiple milestones, Iterations focus on a set timeframe (e.g., two-week sprints) for completing specific tasks within a project. Iterations help teams stay on pace by emphasizing regular progress toward smaller, achievable goals, rather than focusing solely on broad outcomes as Epics do.

Using iterations enables GitLab to mirror Agile sprint cycles directly, adding a cadence to project tracking that can improve accountability and deliverable predictability.

**Proposal**: 

#### Proposal

For projects, we will start planning and tracking issues on iterations

if we get all tickets estimated.

- track progress of projects in a more efficient way

### Community contributor to Tor

Volunteers want to:

There will be no change on how they use Gitlab.

#### Sysadmins at the Tor project (TPA)

Sysadmins will start managing non-free software after we migrate to Gitlab Ultimate.