diff --git a/docs/explanation/kernel.md b/docs/explanation/kernel.md
index df69f11..c713b0c 100644
--- a/docs/explanation/kernel.md
+++ b/docs/explanation/kernel.md
@@ -54,12 +54,12 @@ Debian scans licenses and patches out everything
 that violates the claim to stay 100% free. Since Garden Linux shares this
 approach, we benefit from Debian patches.
 
-Additionally, Debian provides a good kernel configuration,
+Debian also provides a good kernel configuration,
 which is used by Garden Linux as a base for configuration.
 We extend this kernel configuration to our specific requirements during the
 kernel integration process.
 
-Furthermore, Debian kernel [patches](https://salsa.debian.org/kernel-team/linux/-/tree/master/debian/patches) are applied in most cases.
+Debian kernel [patches](https://salsa.debian.org/kernel-team/linux/-/tree/master/debian/patches) are applied in most cases.
 
 ## Further reading
 
diff --git a/docs/how-to/kernel-builds.md b/docs/how-to/kernel-builds.md
index 7344471..db82dfa 100644
--- a/docs/how-to/kernel-builds.md
+++ b/docs/how-to/kernel-builds.md
@@ -103,7 +103,7 @@ A scheduled workflow scans a list of configured branches [see](https://github.co
 The automation creates a PR if a new patch level is available.
 
 :::warning
-Note that build failures in this PR will not be visible in the way you are used to it.
+Build failures in this PR will not be visible in the way you are used to it.
 This is due to limitations on GitHub.
 Always check the PR-related workflow manually before merge as it might well be that an upgrade of the kernel breaks the build.
 [See this issue for more information if you are interested](https://github.com/gardenlinux/package-linux/issues/47).