From 83ef365b721ff33d73e65f49510b2442aa73c8da Mon Sep 17 00:00:00 2001
From: kilavvy <140459108+kilavvy@users.noreply.github.com>
Date: Thu, 12 Jun 2025 15:48:09 +0200
Subject: [PATCH 1/2] Update iterators.rs

---
 utils/src/iterators.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/src/iterators.rs b/utils/src/iterators.rs
index 612e95070..df1d3c9af 100644
--- a/utils/src/iterators.rs
+++ b/utils/src/iterators.rs
@@ -1,6 +1,6 @@
 use std::num::NonZeroUsize;
 
-/// Given an iterator that's clonable, split it into two iterators
+/// Given an iterator that's cloneable, split it into two iterators
 /// at a given maximum number of elements.
 pub fn iterator_split<I>(
     it: I,

From 91b64485ee4b2dbc12139099a6040308c989448e Mon Sep 17 00:00:00 2001
From: kilavvy <140459108+kilavvy@users.noreply.github.com>
Date: Thu, 12 Jun 2025 15:49:03 +0200
Subject: [PATCH 2/2] Update relationship-particles.md

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

diff --git a/docs/src/relationship-particles.md b/docs/src/relationship-particles.md
index ce5675138..6ea539b51 100644
--- a/docs/src/relationship-particles.md
+++ b/docs/src/relationship-particles.md
@@ -211,7 +211,7 @@ Here, we circle back to [composefs](https://github.com/containers/composefs).  O
 think of composefs as effectively a way to manage something like dm-verity, but using
 files.
 
-What bootc builds on top of that is to target a specfic container image rootfs
+What bootc builds on top of that is to target a specific container image rootfs
 that is part of the "physical" root.  Today, this is implemented again using ostree, via the `ostree=` kernel commandline argument.  In the future, it is likely to be a `bootc.image`.
 However, integration with other bootloaders (such as Android Boot) require us to interact
 with externally-specified fixed kernel arguments.