Skip to content

Commit 355e5f4

Browse files
authored
Merge pull request #21773 from LasseRosenow/guides-remove-managing-a-release-toc
doc/guides: remove toc from managing a release and fix using timers guide
2 parents 1f6a7b4 + 152736a commit 355e5f4

File tree

2 files changed

+3
-15
lines changed

2 files changed

+3
-15
lines changed

doc/guides/c_tutorials/timers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ also use soon. Using `ztimer_sleep(ZTIMER_SEC, 5);` we simply wait for around
5050
But what if we want to do something else while waiting for the timer to expire?
5151
Let's take a closer look at how we can use timers in RIOT.
5252

53-
### Step 1: Creating a Callback
53+
## Step 2: Creating a Callback
5454

5555
Timers are a way to schedule tasks to be executed at a later time.
5656
In RIOT, you have to tell the timers two things:
@@ -76,7 +76,7 @@ and prints the string to the console. Congrats, you have created a callback func
7676
now all that is left is to create the timer and schedule it.
7777
To do that lets restructure our `main` function to use the timer.
7878
79-
### Step 2: Scheduling the Timer
79+
## Step 3: Scheduling the Timer
8080
8181
Go into your `main` function and include the following code:
8282
@@ -102,7 +102,7 @@ This code tells the timer to fire in 3 seconds.
102102
The first argument specifies which type of clock we want to use,
103103
the second argument is the timer we created, and the third argument is the time in seconds.
104104
105-
### Step 3: Running the Program
105+
## Step 4: Running the Program
106106
107107
Now that we have created the timer and scheduled it, we can run the program.
108108
Compile the program using `make` and flash it to your board using `make flash`.

doc/guides/misc/managing-a-release.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3,18 +3,6 @@ title: Managing a Release
33
description: This page describes the process of managing a release.
44
---
55

6-
## Contents
7-
8-
1. [Checklist](#1-checklist)
9-
2. [Preparation](#2-preparation)
10-
3. [Feature Freeze and Testing](#3-feature-freeze-and-testing)
11-
4. [Drafting Release Notes](#4-drafting-release-notes)
12-
5. [Actual Release](#5-actual-release)
13-
6. [Other Repositories](#6-other-repositories)
14-
7. [Important Fixes after Release](#7-important-fixes-after-release)
15-
8. [Resources](#8-resources)
16-
9. [Forum Post Templates](#9-forum-post-templates)
17-
186
## 1. Checklist
197

208
Steps marked with a :scroll: icon can also be automated with the release manager script.

0 commit comments

Comments
 (0)