From ff569a4de05272464abb18c5649f11b9cf5e87d7 Mon Sep 17 00:00:00 2001
From: Naveen Prashanth <gnpaone@gmail.com>
Date: Thu, 7 May 2026 10:05:29 +0000
Subject: [PATCH] Edit making_a_release.md

---
 docs/making_a_release.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/making_a_release.md b/docs/making_a_release.md
index ec0bd8a..a1419d1 100644
--- a/docs/making_a_release.md
+++ b/docs/making_a_release.md
@@ -5,7 +5,7 @@ The following describes the process of making a new release:
 1. In `data/org.pipewire.Helvum.metainfo.xml.in`,
    add a new `<release>` tag to the releases section with the appropriate version and date.
 
-2. In `meson.build` and `Cargo.toml`, bumb the projects version to the new version.
+2. In `meson.build` and `Cargo.toml`, bump the projects version to the new version.
 
 3. Ensure cargo dependencies are up-to-date by running `cargo outdated` (may require running `cargo install cargo-outdated`) and updating outdated dependencies (including the versions specified in `Cargo.lock`).