From e03da0b5bc2b77559e451a8d45581c6e833321bf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Mon, 6 Mar 2023 15:19:23 -0500
Subject: [PATCH] rephrase

---
 howto/upgrades/bookworm.md | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/howto/upgrades/bookworm.md b/howto/upgrades/bookworm.md
index 0b162d80..93c02c34 100644
--- a/howto/upgrades/bookworm.md
+++ b/howto/upgrades/bookworm.md
@@ -1,11 +1,12 @@
 Debian 12 [bookworm](https://wiki.debian.org/DebianBookworm) [entered freeze in January 19th 2023](https://lists.debian.org/debian-devel-announce/2023/01/msg00004.html). TPA
-is in the process of studying the upgrade immediately after the
-bullseye upgrade is completed. We have a hard deadline of [one year
-after the stable release](https://www.debian.org/security/faq#lifespan), which gives us a few years to complete
-this process. Typically, however, we try to upgrade during the freeze
-to report (and contribute to) issues we find during the upgrade, as
-those are easier to fix during the freeze than after. In that sense,
-the deadline is more like the third quarter of 2023.
+is in the process of studying the procedure and hopes to start
+immediately after the bullseye upgrade is completed. We have a hard
+deadline of [one year after the stable release](https://www.debian.org/security/faq#lifespan), which gives us a
+few years to complete this process. Typically, however, we try to
+upgrade during the freeze to report (and contribute to) issues we find
+during the upgrade, as those are easier to fix during the freeze than
+after. In that sense, the deadline is more like the third quarter of
+2023.
 
 It is an aggressive timeline, which will like be missed. It is tracked
 in the GitLab issue tracker under the [% Debian 12 bookworm
-- 
GitLab